Confusion on setting hostname and DNS

Greetings,
I have S10 on x86. In attempting to get the DHCP client up and running I followed the instructions from the S10 Documentation and ran sys-unconfig. This seemed to work well in that it did handle the setup of DHCP for my lan card. One thing that it didn't seem to set up correctly was my hostname.
When the system reboots the host name comes up 'unknown'. I am able to manually set the hostname but I'd like it to be permanent. I read the pages on requesting a specific host name from the DHCP server but I don' t think this is what I want to do and it doesn't seem to work for me anyway. I suspect that part of the issue is that the DHCP 'server' is nothing more than a switch/router and only provides IP addresses, nothing more.
How do I set the permanent hostname? Is it as obvious as /etc/hostname?
Thanks
TC

Hi,
For a dhcp client, don't create a /etc/hostname file.
It'll be created (empty) for you.
To get the hostname, create a file /etc/nodename
with the hostname you want inside.
# cat /etc/nodename
maxlap
# uname -a
SunOS maxlap 5.10 Generic i86pc i386 i86pc
# ls -l /etc/hostname.elxl0
-rw-r--r-- 1 root root 0 Feb 7 10:03 /etc/hostname.elxl0
Note that I didn't create /etc/hostname.elxl0.
It was created at boot for the interface on that machine.
max

Similar Messages

Need to set hostname and domain name

Hi All,
I need to
1) set my "hostname" (foo), and
2) set my "domain name" (acme.local)
such that my machine identifies itself as "foo.acme.local". Anyone know how to do this? (I found the host name in file sharing, but it will not let me set the domain name.)
Many thanks,
-T

etresoft wrote:
Your domain is the name of your server.
What gave you that idea? My domain name is "acme.local". It is not the name of my server. I have three servers on my network. The one with the DNS, DHCP, and firewall servers on it called "server.acme.local".
I am confused about why you feel the need to have a subdomain.
This is not a subdomain. What gave you the impression I was asking for a subdomain?
What you seek to accomplish is entirely unnecessary and far more involved than just editing a config file.
Pretty easy in Linux and Windows. They just grab the domain name from the DHCP server. Or, you can hand configure them if you wish. Do you know how accomplish same in 10.6.4?
Give your machine a name in System Preferences > Sharing and it will have the name "whatever.local". That is all you need.
I would like to the entire network name displayed correctly. "whatever.local" is incorrect. It should be "machinename.domainname" or "foo.acme.local". In my example, "foo" is the machine name ("whatever" in your example) and "acme.local" is the domain name. (Not the server's name, by the way.)
"System Preferences > Sharing" will not let me add any extra periods. And will not let me change the ".local" either. (In this instance, I want the ".local".)
Here is the reverse rule I had to hand create:
182 PTR foo.acme.local.
(The dot on the end is not a mistake.)
I do not want a stray computer floating around that does not identify itself correctly. "foo.acme.local" is correct. "foo.local" is not.
By the way, this computer gets its IP address from a DHCP server, which does tell this Apple what the domain name is. (It gets ignored.)
/etc/dhcpd.conf
option domain-name "acme.local";
That is the config file for your DHCP server. You would use this if your machine were sharing its internet connection, for example. You don't need to edit this file.
You misunderstand. The DHCP server, not on this Mac, is not being used to share Internet connections. It is being used to assign IP addresses to machines on the local network. It is also being used to assign fixed IP's to network printers based on their MAC addresses. In my network, these are "off Internet" addresses. The firewall, also not on this Mac, it used to share a single Internet connection with all the internal users.
Hmmm. I created the file (dhcpd.conf) by hand. And, yes I do need to edit it all the time. Especially when I have bone headed machines on my network that do not follow or respond to standard networking conventions. This Mac does not accept the domain name given to it by my DHCP server and as such my DHCP server will not automatically update my DNS tables.
Evidence of this can be found in the dhcpd.leases, where I had to hand enter
client-hostname "foo";
into the lease table (did not do me any good).
I am wondering if 10.6.4 is not capable of handling this kind of standard network naming convention. (FreeBSD, which Apple run on top, is capable, so I am confused.)
MacOS X does not run on top of FreeBSD. They are different operating systems. MacOS X has a POSIX layer which most closely resembles BSD, that is all.
Interesting. Thank you for pointing out the difference. I bet POSIX know how, just like FreeBSD, which it resembles.
If I change the name in /etc/hosts, will Apple over ride it? (I am not at the machine or I would just try it.)
You do not "change" the name in /etc/hosts. You are just adding entries into your machine's lookup table. You can add as many aliases to as many IP addresses as you want. This is not the same as changing your machine's name, but it may be sufficient for what you are trying to accomplish - assuming I knew that, which I don't.
Then, where do I make the change?
10.6.4 did not tell the DHCP server what its name was either, so I had to hand add it into my DNS forward and reverse records. AAAAHHHHH!!!!
I strongly advise against editing files you don't understand.
I create my entire DNS configuration by hand, including my forward and reverse tables. Oh yes, I understand it, do I ever understand it. You should not jump to conclusions: it is insulting. I am presuming you meant no insult. Just be more careful next time.
I think that what is happening here is that 10.6.4 is not set up to follow standard network naming conventions. I would posit that the idea is to keep home users out of trouble. Probably a good thing. If 10.6.4 is not capable of using standard naming conventions, (or following standard DHCP conventions), I would just like a confirmation of that so I will stop trying to figure out how to do it. And, stop wasting my time and just hand configure any additional Mac's that enter my network.
Again, a "confirmation that it can not be done", or "how to do it" is what I am looking for.
Thank you for the assistance,
-T

Hostname and file sharing names don't match

I have a very strange problem... I am running OS X 10.7.2 on my Mac Pro. My Computer Name / Hostname doesn't match what is shown for my computer name on the Sharing panel under System Preferences for File Sharing, Screen Sharinging etc.
When I go to System Preferences -> Sharing, my Computer Name is "gascan-mac" which is what I get in the terminal of my system. However when I selected Screen Sharing or File Sharing the details about this service on the left show "vnc://mac-mini/" for the Screen Sharing address and "afp://mac-mini" for File Sharing and "http://mac-mini/" for Web Sharing. What is up?
I have rebooted multiple times and nothing fixes this. If I go to another system and ping using "mac-mini" I get a response from the correct address. So something in the system is set to this name but I can't find where to change it.
Help!
Thanks,
Chris

I don't see your problem.
There is little to no connection between your machine's own hostname and DNS - which is what everyone else will be using to lookup your host via.
In other words, according to the DNS for your network, the IP address in use by your machine has the 'mac-mini[.whatever]' hostname.
The Sharing preferences hostname is pretty much used by Bonjour/Zeroconf so your machine likely also has the name 'gascan-mac.local' but that's not directly connected to your DNS.

Setting hostname,domainname and static IP address

Hi,
I have an issue regarding hostname and domainname on Oracle Linux 5.4.
I followed the steps given on this link for Oracle Linux 5.4 installation.
http://www.oracle-base.com/articles/linux/OracleEnterpriseLinux5Installation.php
As per the snapshots and guidelines given on this link,I should have been asked to configure network interface.
But It didn't show me the screens shown in steps 16,17 and 18 where I could have entered hostname,domainname,IP etc.
And when I checked after installation,it showed me
hostname
localhost.localdomain
and
domainname
(none)
That's because it took DHCP network configuration automatically(Correct me if i am wrong!!).
Although I am going to turn it's currnet DHCP assigneed IP into static IP.
Now,as I am going to have to install Oracle E-Business suite on this platform,I must have hostname,domainname and IP set properly.
Please guide me how I can set these three things(hostname,domainname and IP) permenantly.
Also should I turn its current DHCP IP into static IP before changing hostname and domainname or after it?
Thanks,
Rushi
Edited by: Rushi Shah on May 21, 2011 7:43 PM

login as root
and enter setup >> select eth0 >> enter i/p and dns details and save and exit and then restart network
steps
====
1) setp
2) enter i/p and dns details
3)save & exit
4)service network restart
2)settipng up hostname & ipconfig
steps
1) vi /etc/hosts
add entry
ipaddreddss hostname.domain name hostname
save & exit
ex:
192.168.0.12 apps.oracle.com apps
2) service network restart
3) chk hostname -i (ip address)
hostname -a (hostname)
hostname -d (domain)
crosscheck all the values & if its ok..
Thanks
reddy
http://11iapps.wordpress.com
Edited by: user13551818 on May 21, 2011 8:03 PM
Edited by: user13551818 on May 21, 2011 8:04 PM

I am trying to setup Microsoft office mail and need assistance - I am receiving the error, unable to find server and DNS setting in the Network

I am trying to setup Microsoft office mail and need assistance - I am receiving the error, unable to find server and DNS setting in the Network

Which version of OSX and what email provider are you using.

Setting Locale and Hostname on New Installation Fails

Hello,
Tried doing an Arch install on my Acer Aspire One D255 today, but when I try to set the hostname and locale while chroot'ed into /mnt, I get:
Failed to get D-Bus connection: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
This occurs when running hostnamectl and localectl as per the Beginners' Guide. I had to set the locale manually in /etc/locale.conf, but I don't know what to do about the hostname, and something seems to indicate there's a more serious issue.
Any idea?

ifaigios wrote:I edited Beginner's Guide yesterday replacing the old method of setting the default locale and the hostname, with localectl and hostnamectl. However, as you discovered, it seems that these commands require DBus to be running to work, so they are of no use in the chroot. Thankfully, thestinger reverted my edits as soon as you found out the problem, so the page contains the correct information again. I am sorry for the inconvenience and for any trouble I caused.
No problem, thanks for helping! However, I think you missed a few 'systemctl' commands. There's three here and one here. I don't know how to fix them, so for now I'll just configure them on reboot.

Common Abbreviations Used When Setting Up and Troubleshooting HP Printers

Here is a list of common abbreviations and phrases used while trying to troubleshoot network-connected printers within the forums and other web-based support documents:
Ad Hoc – Latin phrase meaning "for this" and is used when describing a type of connection between the printer and computer by-passing the router. This is not the recommended network connection by HP support (see SNC below).
ADF – Automatic Document Feeder which is the tray on the top of a printer used for multipage scans and faxes.
AES – Advanced Encryption Standard used to describe a password-protected router/internet connection.
AiO – All-in-One
AP/STA – Access Point Station or another word for router.
ASIC – Application Specific Integrated Circuit
AWC – Auto Wireless Connect
BIOS – Built Input/Output System
BSOD – Blue Screen of Death
CGD – Color Graphic Display
CMD – Command
CMYK – Cyan Magenta Yellow Black
CNG (tones) – 1100 Hz tone stands for Calling Tones used on landline fax machines.
CPU – Central Processing Unit
CUE – printer version 10-14 also known as Solution Center.
CVN - Card Verification Number on the back of a credit card.
DHCP – Dynamic Host Configuration Protocol
DIM – Digital Imaging Monitor
DMI – Desktop Management Interface
DNS – Domain Name Server
DPI – Dots Per Inch
DSL – Dedicated Service/Subscriber Line or type of digital internet service bundle.
ECM – Error Correction Mode in advanced fax settings.
EIRP – Equivalent Isotropically Radiated Power
EMI – Electromagnetic Interface
ESP – Extended Service Plan
EWS – Embedded Web Server
FFC - Federal Communications Commission regulates all forms of communication.
FoIP – Fax Over IP
FPU – Floating Point Unit
FTF – First Time Fix
GBU – Global Business Unit
GUI - Graphical User Interface or the images on a computer screen or display.
HDMI – High Definition Multimedia Interface which is a type of plug-in to connect a computer to an HD monitor.
HHO – Home and Home Office is the name of the sales department in HP www.hp.com/shopping
HW - Hardware
ICF – Internet Connection Firewall; Integrated Catalog Facility; Intersystem Communications Function
IE – Internet Explorer
IEEE – Institute of Electrical and Electronics Engineers
EMF - Electromagnetic Frequencies
IIC – Individual Ink Cartridge is a type of ink that consists of only one color.
IP – Internet Protocol which is what a router uses to locate another network connected device.
IPG – Image and Printing Group was one of the names of the printing department in HP.
IPH – Integrated Print Head is a type of ink cartridge that has the printhead in it.
IPIPA – Automatic Private IP Addressing also associated with an IP address beginning with 169.xxx.xxx.xxx
IRIS – Integrated Risk Information System often installed with the OCR software and printer driver.
IRQ – Interrupted Request or one of the original chat rooms and communities when the internet was first created.
ISB - Ink System Business
ISDN – Integrated Services Digital Network
ISF – Ink System Failure
ISM – Instrumentation, Scientific and Medical radio band
IVR – Interactive Voice Response
IW – In Warranty
LCD – Liquid Crystal Display
LIFI – optical (light) version of WIFI introduced in 2012
LOI – Low On Ink
LPD – Line Printer Daemon
MAC – Media Access Control
mDNS – Multicast Domain Name Service
MFP - Multi-Function Printer
NAT – Network Address Translation
NDU – Network Diagnostic Utility
NTF – No Trouble Found
NVM – Non-Volatile Memory
OCR – Optical Character Recognition is often installed with the printer drivers to allow you to scan to editable text.
ODD – Optical Disk Drive
OJ – OfficeJet
OOW – Out Of Warranty
OOBE – Out Of Box Experience
OSD – Onscreen Display
PBX – Public Branch Exchange
PCIE – Peripheral Component Interconnect Express
PEN – ink cartridge and printer head
PHA - Print Head Assembly that holds the ink in it (often removed while setting up a replacement printer)
POTS – Plain ‘Ol Telephone System
PPI – Pixels Per Inch
PQ – Print Quality
PSC - Print Copy Scan and quite often refers to the very first all-in-one printers.
PSG – Personal Systems Group which was one of the names used to describe the computer department in HP.
QRG – Quick Reference Guide
RAID – Redundant Array of Independent Disks which is what is usually cleaned up while defragmenting a hard-drive.
RFI – Radio Frequency Interference
RPC - Remote Procedure Call often associated with the scan services.
SNC - Standard Network Connection also known as Infrastructure which includes the printer, computer and a router. **This is the preferred wireless connection supported by HP.
SNMP – Simple Network Management Protocol
SOHO – Small Office Home Office which is a division of printer support.
SSID – Service Set Identifier
SSRD – Support Sent Recovery Disc
SW - Software
T30 – Typical Fax Line and also describes the type of cord used for fax setup.
TAM – Telephone Answering Machine not to be confused with voicemail.
TCP/IP – Transmission Control Protocol/ Internet Protocol used to define the network location of a device (192.168.xxx.xxx) and can be good to know when trying to install a wireless printer on a computer.
TIJ – Thermal Ink Jet which is the means to which ink is heated up so that it drips out of the cartridge.
TKIP – Temporal Key Integrity Protocol that describes the type of encryption used during a password-protected setup on a router.
TWAIN – (Technology Without An Interesting Name) Standard for linking applications and image acquisition devices.
UDP – User Datagram Protocol
UI – User Interface
URL – Uniform Resources Locator also known as a web address or hostname and begins with http://
URP – User Replaceable Part that can be purchased to fix a printer.
USBSOW – Universal Serial Bus Statement of Work
VGA – Video Graphics Adaptor
VoIP – Voice Over IP
VPN – Virtual Private Network
WEP – Wired Equivalent Privacy which also means the passphrase or password for a protected network setup (Wireless Setup Wizard or USB to Wireless installation will ask for this and that is just the password used to get on the internet or to connect a device to your router).
WIA – Windows Image Acquisition is the name of the service used to scan with an HP printer.
WINS – Windows Internet Name Service
WLAN – Wireless Local Area Networking or another type of internet connection.
WOOBE - Wireless Out Of Box Experience often associated with Web-Services setup of ePrint on a new printer.
WPA – Wifi Protected Access or another type of encryption used on a router.
WPAN – Wireless Personal Area Networking
WPS – Wifi Protected Setup often associated with a push button connection on the router instead of using a password. If you have this off then other people in the area can access your router for internet service.
WWAN – Wireless Wide Area Networking
Don't forgot to say thanks by giving "Kudos" if I helped solve your problem.
When a solution is found please mark the post that solves your issue.
Every problem has a solution!
This question was solved.
View Solution.

At one point I was somewhat uneducated as a consumer on certain abbreviations. I began to check around the internet but I never found a complete list of all of the abbreviations used in today’s technological world. Over time I have collected a list of every network and printer-related term in relation to HP. I am happy to share this with the world because sometimes when trying to troubleshoot within the forums and other web-based documents the writers can forget that not everyone knows the abbreviations and if you do not know sometimes you can get left behind and feel frustrated. If you know of any other industry-standard abbreviations regarding printers, faxing, and network-connections feel free to post more here.
Don't forgot to say thanks by giving "Kudos" if I helped solve your problem.
When a solution is found please mark the post that solves your issue.
Every problem has a solution!

Basic Mail and DNS help

I'm sorry to ask something that I'm sure has been dealt with many times. I've searched all around and found many threads that seem very close, but I guess there's some little difference that always ends up confusing me. I also get confused by what seems to me to be ambiguous terminology. Anyway, I'm pulling my hair out, so I've finally decided to ask for help.
I'm sorry that this post is so long -- I just don't know what bit of info might be important. I'm trying to give a detailed description of my setup so experienced people can give me better advice.
Here's my situation.
EXTERNAL DNS
(1) I've purchased a domain name through my ISP. Let's call it mydomain.tld
(2) This comes with a very rudimentary control panel that allows me to define 10 A records, 10 CNAME records and 10 MX records.
(3) I have defined an A record pointing to my static WAN IP.
(4) I have deifined an MX record pointing to the same static WAN IP.
(5) This seems to be OK, because if I "dig mydomain.com" or "dig MX mydomain.com" I get my static WAN IP.
MY LITTLE NETWORK
(6) The Internet comes into a 4-port router/modem. (192.168.0.x) This is my "Outer LAN"
(7) One port goes to a Mini with SLS -- Say it's on 192.168.0.99
(8) Another port goes to another router (192.168.1.x) This is my "Inner LAN"
(9) I have forwarded port 80 through the outer router to the SLS. That seems to work fine.
(10) I have also forwarded port 25 through the outer router to the SLS. That does not work yet.
The SLS
(11) When I did the initial install, I gave the SLS the name mydomain.private (I some places, Server Admin gives the name mydomain.local ... I don't know why.)
(12) I set up the INTERNAL DNS on the SLS to handle all initial DNS queries from my LANs, with my ISP's DNS as a forwarder.
(13) I set up the DHCP on my routers to assign the internal DNS server on the SLS as the primary DNS, and my ISP's DNS server as the secondary -- so clients on my LANS are looking at the right DNS servers.
(14) DNS seems to work fine on both my LANs.
BEFORE GOING ANY FURTHER:
If anyone sees any problems with what I have done so far -- Please say so.
... and now THE MAIL
(15) I created a few network user accounts on SLS.
(16) Using squirrelmail, they were able to send and receive messages to each other -- using a browser on the SLS machine or a browser on any other computer on the LANs. But this is all resolved through the internal DNS, using mydomain.private
(17) Mail clients (Mail.app) on the LAN can also retrieve these messages. But I can't send mail using a regular mail client ... and squirrelmail only works internally with mydomain.private
Now, I want to get my mail server working normally for sending and receiving mail both within my LAN and over the Internet. And here is where I get confused. There's the EXTERNAL DNS server that clients on the Internet will use to find my server -- and there's the INTERNAL DNS server that clients on my LAN (?and possibly some services on the server itself?) will use. Then there are terms like HOSTNAME and DOMAIN NAME ... and I'm not really very clear as to the disnction (despite, or because of, reading so many articles). I don't know where I should be using mydomain.com and where I should be using mydomain.private)
in the Mail Service Configuration Assistant:
(18) I use mydomain.com for both the Domain Name (Enter the local Internet domain name) and for the Host name (enter the Internet host name of this mail system). These match the A and MX records of my EXTERNAL DNS (ie. what I see on my ISP's control panel).
(19) To try to make things easier to start with, I enabled all options for both secure and non-secure authentication.
(20) I added a host alias mydomain.private
(21) Setup appeared to go fine.
(22) Back on the LAN, "dig MX mydomain.com" gives my static WAN IP
(23) In the outer router, port 25 is forwarded to the SLS
(24) In SLS, in Server Assistant, In DNS, Mail Exchanger is set to mydomain.private -- this works for sending mail within the LAN only.
(25) I tried changing this to mydomain.com, and then nothing worked.
(26) The Nameserver for my primary zone is set to:
Zone: mydomain.private.
Hostname: mydomain.private
When I try to send a message FROM an account on the Internet TO an account on the SLS, I get an error: "Couldn't find a Mail Exchanger or IP address."
When I try to send a message FROM an account on the SLS TO an account on the Internet, the Mail Delivery System returns it to the sender.
Well, that's where I stand now.
I hope people reading will give me some ideas of some other paths to run down, and tests or experiments to try. I'm not afraid of the command line -- but I'm not very experienced with it either -- so maybe there are some useful diagnostic commands that I should know about.
My ISP is not blocking port 80.
Is there some way that I can tell if my ISP is blocking port 25? (Their customer support doesn't know anything.)
Thanks a lot for your attention and patience.
(Intentionally Blank)

Oops. Sorry for the delay getting back to you.
Thanks David_x. That was really helpful information. It opened up more questions, but it gave me some good ideas of things to try.
I reinstalled SLS. This time I used my FQDN and accepted the installer's
David_x wrote:
Firstly, remove the secondary from DHCP. Otherwise clients will 'randomly' use info from either inside or outside DNS. You want them to use the internal DNS so use that alone.
I see. So "secondary" doesn't mean "in case the primary fails" -- it means something more like "another one in the pool of possible DNS servers". Doesn't that present a problem in the event that my server is down? Why is this preferred as opposed to clearly defined prioritized list? (Then there is another issue of some services using mDNSResponder in some cases and resolv.conf -- at least that's fairly well documented.)
DNS & Hostname, etc...
If you want to be able to access services from inside and outside your LAN, using the server's hostname (same one inside and out), then set up your internal DNS using your .com domain, same as is used externally.
Okay. Got it. I did that with the reinstall.
DNS is only an "IP lookup" system so you want the hostname inside to resolve to your LAN IP and the hostname outside to resolve to your WAN IP. Forget about the .private stuff - it just confuses things.
Okay. Thanks.
Public MX Record…
(3) I have defined an A record pointing to my static WAN IP.
(4) I have deifined an MX record pointing to the same static WAN IP.
The above may not be what you meant to say but just to check… Your public MX record should resolve to your A record hostname. Then the hostname resolves to an IP address. Your MX record should not be pointing directly to an IP address.
Yes. You are right. That's very good of you to point that out. I did have it pointing to an IP address. (My ISPs simplistic DNS control panel is in Spanish, and I was confused about whether "nombre" referred to a name or number.) I had discovered this through brute force trial and error. This sort of thing was very difficult to test, since I don't have control over many of the DNS parameters (like TTL). That was probably my main problem. Now I can send and receive mail from my server to outside accounts, and from outside accounts to my server.
At the moment, I can't retrieve mail on my server from a computer outside of my network. I suppose that's an authentication problem, or a hostname alias or something. I'll continue trying different things.
Testing Port 25...
To see if port 25 is blocked, get an outside computer and "telnet your-wan-ip 25". If you can switch on logging at the firewall for your port-forwarding rule, all the better as this will be only sure way to see that it is reaching the WAN firewall.
By "logging at the firewall", I suppose you mean at the router? Alright. I still have to try this. From my point of view, this kind of suggestion is great advice.
Instead of using an outside computer, would it be possible to do this sort of checking using an anonymizing proxy? I suppose they usually don't allow telnet.
...any chance this could be tested from my "inner" LAN? (My guess is that it needs to be from a computer that is "upstream" relative to the "outer" router. I'm under the impression that routers handle upstream connections differently than downstream connections, this wouldn't work.)
After that, test at server... open Terminal and enter: "tcpdump -v tcp port 25"
Tcpdump will listen on port 25. When the telnet session gets port-forwarded, you will see a listing of information about the packet received. If you get nothing then the port-forwarding is not working.
So, to make sure I've got this straight:
Turn on logging on port 25 in my outer router.
Go to Terminal on my server.
Start tcpdump listening on port 25.
Take my netbook out to some WiFi hotspot (for example).
Telnet into my server.
Come home and check my logs.
(Maybe I should check out this VPN stuff.)
I'm looking to see that the router forwarded the port correctly.
That's great trouble shooting advice.
Now you'll see how slow I am. I'm reading along, running through all of this in my head, imagining all of my steps ... And only now do I realize that if (as of my latest experiments) my server has been able to receive mail from outer accounts -- then the router must be forwarding things and the mail server is, to some extent, working fine. Okay. I'm still going to go through these steps anyway to see what it should look like.
Server Admin: Domain Name & Hostname...
The Domain Name is just your domain name... e.g., mydomain.com
The Hostname is ideally the same as your external MX hostname... e.g., mail.mydomain.com
The main thing about the Hostname is that this is what your server will report as it's HELO name to other connecting mail servers. Some will check this against the public MX record and use any discrepancy to increase likelihood of spam filtering.
Is there really any reason that a small setup like mine should use "mail.mydomain.com" instead of just "mydomain.com". Since I don't have a separate machine dedicated to mail, maybe it's just an unnecessary complication. I was just copying what I've seen around (configuration for mail and articles I've read).
Under Advanced-> Hosting, tick the "Include server's domain as local host alias".
Okay. What exactly does this do? I understand the words, but not the sense of the phrase. (I find this happening a lot.)
Checking Server Settings…
Use a terminal session to debug any basic configuration issues on the server. The error responses are much more informative than just using a mail client. Open Terminal in a local computer… "telnet server-lan-ip 25" and carry out following…
I could connect with telnet to port 25 on the server:
(1) From a remote computer.
(2) From a local client.
(3) From the server
As we step through the experiment, you will see that we have a few problems.
Server Response:
Trying...
Connected to fqdn.or.ip.
Escape character is '^]'.
220 fqdn.or.ip ESMTP Postfix
#1. Declare where you are sending the email from:
HELO something.name
You can use a real hostname but the mail server has no choice but to accept whatever you type.
Response: 250 servers.hostname
So far, so good.
On remote computers, I couldn't get any further than this.
I'll try again tonight.
#2. Give senders address:
MAIL FROM:<mail@senderdomain>
Response: 250 Ok
I could get this to work for either a local email account or a remote email account, from telnet sessions initiated either on the server itself or on a local client.
#3. Give recipients address:
RCPT TO:<mail@otherdomain>
Response: 250 Ok
Here, I did not get consistent results.
From a local account to a remote account, I could get "Relay access denied".
From a local account to a local account, I could get "Recipient address rejected. Service is unavailable. But this was not consistent. I used three different local accounts, and all could send or receive at one time or another.
#4. Start composing the message:
DATA
Response: 354 End data with <CR><LF>.<CR><LF>
#5. Type a message. Finish with a single "." on a line on it's own.
Response: 250 Ok: queued as dah,de,da
#6. Close the connection by typing: QUIT
Response:221 Bye... Connection closed by foreign host.
suggestion for hostname.
Were you going to add something else here?
Well, any comments or insights that you might add will be very much appreciated. I'm going to continue sending and receiving and making little tweaks. It's really pretty confusing for a newbie. I thank you a lot for all the time you spent reading and helping me.
(Intentionally Blank)

Mac mini server networking and DNS setup help

Thanks in advance to anyone who can help me with this. I'm working at a small business where I'm the only guy with any IT experience at all, but I'm new to Macs and OS X (<1 year) and being a server admin so please bear with me.
We just bought a Mac mini server as we are expanding from a bunch of workstations and Google Docs. I've just gone through the installation process, but nothing else is on the server, no user data at all, so if the answer is to reinstall from scratch, I can do it.
We'd like the mini to be a file server, print server as well as the gateway for the internet. I realize we could stick to our router and have the server as another node in the network, but we also got a Time Capsule for backing up the server and will locate it in another room to be another wireless access point there.
When going through Server Assistant, I didn't really know what to name the machine so I used corp-Server.local for the Current Hostname and corpserver.private for the DNS Hostname (though i actually use a 3-letter company acronym instead of "corp").
However, i realized after setup we'd want to access the server externally by name, so I changed the DNS hostname to server.companyname.com in the Zones tab of the DNS section of Server Admin (edited primary zone name, changed Nameservers entry for both primary and reverse zone).
I don't know what else I need to do though because there are loads of instances where corpserver.private still shows up, like in the Open Directory section of Server Admin (which btw always hangs when I open it) and the Contact Info of users (eg. user email is [email protected]). I also had trouble earlier using Server Preferences and Server Admin either not connecting or not recognizing my login, but that seems to have abated.
I guess my problem is, where else do I change the DNS hostname? Or do I have to change the DNS hostname back to corpserver.private (in Server Admin)? That way, I think at least everything will be consistent, but would I be able to still configure it somehow so that externally, we could access the server by the server.companyname.com URL?
Also, can the mini be a wireless router for the office? As mentioned before, we want to cut the existing wireless router out and use the mini instead (and use the Time Capsule as a wireless bridge).

So the ISP<->router connection can have a dynamic IP address, but the router<->server one should be static? I guess that means I have to set the IP address in the router. I hope I can get access to it. I don't suppose it matters which one I set first?
An IP router does not assign addresses.
A DHCP server does assign IP addresses upon receipt of a DHCP request from a client.
Some routers (and many firewall routers) do include a DHCP server.
A box with a static IP address does not need to send a DHCP request; it has a static address.
You'll need to ensure that the IP address pool within the DHCP server does not overlap the addresses that are manually assigned to your local hosts; the static IP addresses on your LAN.
[Here is an overview of the pieces involved here, and some of the typical terminology|http://labs.hoffmanlabs.com/node/275].
I hate to belabour the point, but I just want to clarify: in my setup where ISP<->router<->server<->clients, where the server is the only machine connected to the router, which one should be the local DNS server? The server, right? So if the DNS server is turned on in the router, I should turn it off? Or do I need both (ie. router for its LAN (to server), and server for its LAN (to clients))?
So to confirm, the configuration includes (probably) a modem, a router (firewall) and a router (Mac), and then the rest of the (local) show? That is not the simplest configuration, and it's Particularly given that Mac boxes make expensive and slow routers.
The usual configuration is ISP>firewall>LAN and the LAN is usually built from WiFi, wired connections and switches. Within one subnet (which is typical) any host inside your firewall is connected on the LAN, and can communicate (directly) with any other LAN client. The firewall is configured as the gateway; that's the default route for outbound connections.
One more thing that's bugging me: I still don't understand why I couldn't connect to the internet when I plugged in the Ethernet cable from server to router. Even if I was using DHCP to get a dynamically allocated IP, shouldn't it still have worked? I'm worried that I'm going to set up everything as it should be but the connection still won't work.
That's likely because you're trying to use the Mac as a router, and that takes specific configuration steps. It's easier to have ISP>firewall>LAN, and have the Mac OS X Server box and the rest of the stuff as peers on your LAN. If you really want to use the Mac as an IP router, look around for setting up static routes on Mac; there are postings around for that.
If your data is more valuable and your security preferences and requirements are higher, then you may want a firewall with a DMZ, and put your web-facing boxes over in the DMZ. If you're serving stuff to the web or a mail server or such, it's possible to get breached, and a breach means folks can potentially get further into your LAN. With a DMZ, they're somewhat more isolated from your LAN.

Batch Script using System Varriable for Hostname and FQDN results in large space between

I have a batch script running on Windows 7 that I've created to help a physical computer, connect to his virtual cousin. Problem is when I try to make
it use the FQDN (required by the View Client) it puts a large space between the hostname and the domain.
Result
ECHO Connecting View Client to PREFIX-SERIAL .domain.comOR"C:\Program Files\VmWare\View.exe" -Args -serverURL PREFIX-SERIAL .domain.com
Our computers are named a combination of a prefix and the serial number. Our virtual computer names are the same, but with a different prefix. So my attempt was to make a connection
script, using the computer serial number. My Process:
Setting %serial% variable.
for /F "skip=1 tokens=*" %%b in ('wmic bios get serialnumber') do if not defined serial set serial=%%b
Set %hostname% variable.
set hostname=PREFIX-%serial%
Installation command line
"C:\Program Files\VmWare\View.exe" -Args -serverURL %hostname%.domain.com
That results in the output at the beginning of my post.
I've also tried
%hostname%.%userdomain%.com
PREFIX-%serial%.%userdomain%.com
PREFIX-%serial%.domain.com
SET FQDN=.domain.com
PREFIX-%serial%%FQDN%
%hostname%%FQDN%
I also tried carets and quotes on set commands without any improvement.
I'm sure I'm missing something simple here. Any advise?
There's no place like 127.0.0.1

Will something like this get you what you are looking for?
(gwmi win32_bios).SerialNumber+(gwmi WIN32_ComputerSystem).Domain
Or
$hostname=(gwmi win32_bios).SerialNumber+"."+(gwmi WIN32_ComputerSystem).Domain
Sorry just realized your looking to do this in a Batch file...so maybe something like this
@echo off
for /F "skip=1 delims=" %%j in ('powershell "[System.Net.Dns]::GetHostByName((hostname)).HostName"') do (
set Host=%%j
goto :DONE
:DONE
echo %HOST%

Setting up SLS & DNS in particular

I would really appreciate some step-by-step guidance on setting up SLS and DNS in particular. I've read all Apple's documentation and dozens of guides and discussions but remain confused about several points, and my set-up still isn't working correctly.
I have the latest SLS on a Mac Mini, which is behind my Draytek 2820vn router. I have 3 Mac clients (all 10.6.6) and 3 OSX devices. I primarily want to share address books and both share and sync (between devices) iCal. I want to be able to do this from outside my LAN, so need to run Mobile Access.
I have a static IP address from my ISP, to which my sub-domain (e.g. network.mydomain.com) points via DNS with my domain registrar.
I seem to have DNS running ok on the server, at least for my LAN (the -checkhostname and dig commands all return the right results). I can get my clients to log on to the network from within the LAN but not get iCal or the address books playing along.
I have enabled port redirection in my router for:
* iCal Server SSL on 8443
* Address Book Server SSL on 8843
* DNS on 53
* Web service on 80
* HTTPS on 443
I prefer to use SSL for maximum security (though am not sure if I also need to open up the non-SSL ports for these services).
So my questions are:
1. Do I need to redirect any other ports?
2. Do I need a reverse DNS with my ISP (i.e. external to my LAN), for the services I am wanting to run?
3. Do I have to enter the static IP address of the SLS in my router as the primary DNS, with my external DNS as the secondary? (I have done this.)
4. How should I configure the firewall on SLS, given its location behind the Draytek? I want a very secure set-up.
5. Does anyone have any other pointers on getting everything to work with this particular arrangement?
Many thanks for any expert feedback. Please note that I'm pretty Mac-proficient for a amateur, but have never set up a server before, so have a limited grasp of the lingo and things like command line.
Many thanks.

* iCal Server SSL on 8443
* Address Book Server SSL on 8843
* DNS on 53
Close that DNS port. You don't want to be fielding in-bound DNS translations.
* Web service on 80
Unless you're planning to serve web sites, close that.
* HTTPS on 443
Ibid.
I prefer to use SSL for maximum security (though am not sure if I also need to open up the non-SSL ports for these services).
[What IP ports need to be opened|http://support.apple.com/kb/ts1629] depends on what services are required, and whether or not you're using a VPN.
1. Do I need to redirect any other ports?
That's one only you can answer, as it is dependent on what you want to do here.
A different question that you want to consider for cases such as this is "how can I close more ports?".
The usual answer is via VPN.
One of many other answers can include a firewall with DMZ capabilities, and a network where you park the server in its own network jail. (A DMZ is a two-firewall firewall box; where you can have an untrusted WAN network, a slightly trusted but still restricted DMZ, and a more trusted internal LAN.)
2. Do I need a reverse DNS with my ISP (i.e. external to my LAN), for the services I am wanting to run?
For secure services, you'll want reverse DNS. That can include ssl services, though (with control over your clients and the boxes that are attempting to connect your LAN) it's not critical.
Reverse DNS is (far) more central to SMTP services, and to ecommerce, and to any cases where you don't control the remote clients, and where the clients are thus dependent on your forward and reverse DNS, and your certificates matching your DNS.
You need LAN-based DNS with Snow Leopard Server, either on the server or with another DNS server on your LAN. [Here is how to set up LAN DNS|http://labs.hoffmanlabs.com/node/1436]
Your ISP will not typically be in a position to provide DNS translations for the private address space. (That's shared and non-routed IP address space, so your ISP would needs to set up DNS for you.)
3. Do I have to enter the static IP address of the SLS in my router as the primary DNS, with my external DNS as the secondary? (I have done this.)
I don't run hosts as gateways. That's more work, and it's less secure.
4. How should I configure the firewall on SLS, given its location behind the Draytek? I want a very secure set-up.
There's no direct answer for that, and there are many different network designs and many different degrees of risk aversion and different degrees of budgets. For some environments, I run locked down. For others, not so much.
5. Does anyone have any other pointers on getting everything to work with this particular arrangement?
[Here is how to set up LAN DNS|http://labs.hoffmanlabs.com/node/1436], and [here is the public-facing DNS set-up|http://labs.hoffmanlabs.com/node/1594] and [here is a quick intro to networking pieces and parts|http://labs.hoffmanlabs.com/node/275].

Having trouble setting up Open DNS with mac.

When I try to set up Open DNS I get the following error message:
Safari can’t open the page “http://192.168.1.1/Basic.tri” because the server unexpectedly dropped the connection. This sometimes occurs when the server is busy. Wait for a few minutes, and then try again.
I have a Linksys router. I can get the router so save the settings using my Microsoft laptop, but I get an "oops" error message from Open DNS saying I am not set up on their site and just sends me back to step one. Does this sound familiar to anyone?

No, you cannot put the router in front of the modem.
You might look for any information your ISP gave you for your modem, such as a user guide. Or use the instructions at OpenDNS for a Motorola router, it should be similar. Remove the router and directly connect just one computer to the modem and try to access the modem's built in utility, as you have with your Linksys router. Motorola's default address appears to be "http://192.168.10.1/", the default username is "admin", and the password "password". If you encounter a question about obtaining the DNS service dynamically, check NO, then handset the OpenDNS servers, save and possibly restart the modem.
If you are successful in configuring the modem, go back to the router and leave the DNS settings blank, as well as on each computer. Then the computers should receive the service dynamically from the modem.
After all that, hopefully the OpenDNS website detects you using their service and allows you to proceed with setting up your account.
Dah•veed

Help setting up Open DNS with new airport extreme

I cant seem to get Open DNS to work with a new airport extreme. The status says I am not using Open DNS and its not filtering anything. I have followed the exact steps for set up listed on their website, checked the dns settings, cleared both caches and restarted the computer, modem and router with no success. I set the airport up in bridged mode, although I tried the other option under setup, but not sure what I was doing? I picked up this router because I wanted easy set up and the apple store assured me it would work with Open DNS. Oh, and I also downloaded the latest firmware update on the router. Can anyone help me with the settings or what else I need to check?

Sorry, I am not familiar with this product, so I checked online to pick up some information. Here I am referring to the information found here:
http://www.dslreports.com/faq/6096
I found that your device is mentioned as follows in the intro under Section 1 of this document:
The BellSouth supplied Westell 2100, 2200 and 6100 models (Models A90-210030-04, B90-220030-04, and B90-610030-06/C90-610030-06, respectively) share many features and functions.
Next, I am referring to the information under Section 2, under the heading of Standard Default Mode Connection (separate hub or switch present). Unless you have changed the configuration on the Westell, this is how your device is operating. In this mode, the Westell device is acting both as a modem and router in one unit.
So, an attached router (AirPort Extreme) must be configured as a switch to work correctly. That is what Bridge Mode is....the AirPort Extreme is operating as a switch when it is in Bridge Mode (which would be the correct setting to use when the Westell is set to its Standard Default Mode).
Any changes that you want to make regarding DNS settings would need to be made on the Westell device, since it is acting as the main router on your network.
In Bridge Mode, the AirPort Extreme simply passes that information through to its connected devices. You will not be able to make any DNS related changes on the AirPort Extreme since it receives that info from the Westel device. Some service providers force you to use their DNS servers, so you might want to check with Bell South or AT&T for more information in this regard.
If you want to be able to configure the AirPort Extreme as the main router on your network, and instruct it to use the DNS information that you want, you will need to refer to the section under the heading of Bridged Ethernet Mode ( separate router present).
Please note that the first item under this heading specifies that "This is the preferred configuration when using a separate external router..." (which would be the AirPort Extreme in your case)
So, it appears to me that this would be the way that you must reconfigure the Westell device to allow the AirPort Extreme to function as the "main" router on your network. In this type of setup, you will be able to enter the DNS information that you want to use under the setup for the AirPort Extreme and it will act as you instruct.
The AirPort Extreme would not be configured in Bridge Mode for this....it would be configured to "Share a public IP address".
The next item in the article specifies that you "Must use a PPPoE client on the Router." This means that the AirPort Extreme would be configured to Connect Using = PPPoE as follows:
AirPort Utility - Manual Setup
Click the Internet icon
Click the Internet Connection tab
Connect Using = PPPoE
You would enter your user name (probably your email address), password, etc in this area. Leave the Service Area box completely blank. Set Connection to Always On, and Disconnect if Idle to Never
Click Update to save the new settings. Power off the Westell device after this and then restart it so that it will pick up the new information that you have programmed into the AirPort Extreme.
I want to stress that this is how I would try to configure the Westell and AirPort Extreme. But, as I said, have not used a Westell device, so I cannot say that this will work correctly for you.
It might be an excellent idea to contact Bell South or AT&T Support to ask for their opinion on this before you decide to change the configuration of the Westel device and the AirPort Extreme.
This type of thing can be intimidating for users, so you might elect to use the services of someone like the Geek Squad at Best Buy, or a similar service from a local computer firm. Perhaps the Apple store could help as well.
If it is not critical that you use Open DNS, you might want to simply leave things "as is", with the AirPort Extreme in Bridge Mode.

Purchased a new Apple TV and the remote double clicks each time I press the button. It worked fine during set up and for the first two days. I have since moved it and this problem started. Restarted,reset,unplugged,change remotes, no change.Help please.

Purchased a new Apple TV and the remote double clicks each time I press the button. It worked fine during set up and for the first two days. I have since moved it and this problem started. Restarted,reset,unplugged,changed remotes, no change. Latest software update. This is really annoying. iPhone remote app works just fine. Any suggestions?

That's one of the weird things.. it recognizes it maybe 10% of the time. And usually, only after I do the two-button reset. Problem is.. since it won't charge above 2%, anytime I try to do a restore or anything like that using iTunes, my device shuts off and I lose whatever progress I'd made.
So, an update... after reading through a bunch of similar complaints (there are literally 1000's of them so there's NO WAY this isn't somehow ios7 related, thanks a lot APPLE ) I decided to try a restore in recovery mode. After 3 hours and several disconnections... I ended up having to just set it up as a new iPad, as the restore did nothing. Weirdly though... as I was doing the restore in recovery mode.. I noticed I'd gotten up to a 10% charge.. higher than it's been since September, so after setting it up as a new device, I turned it off and plugged it in using the wall charger. 2 hours later and I was up to 38%. Still not great, as my iPad, before ios7 could've fully charged twice in the amount of time it took for me to now get 28% more of a charge. And that's with a fully cleaned out device.. so that really ***** and I'm now more confused than ever.
But I'm gonna leave it overnight charging and see what I come up with tomorrow. Sadly, when I paid $600 for it in February, I never expected to have to play "wait and see" with it...

How to set up dynamic dns?

Hi everybody,
could anybody help me to set up Dynamic DNS in the Airport Extreme? I am using Airport Utility 5.5.3
I also have dlink dns service active
Thank You
Manolo Fernández

The following is the basic setup for DDNS on the AirPort using AirPort Utility v5x:
AirPort Utility > Select the base station > Manual Setup >AirPort > Base Station tab > Edit ...
Use dynamic global hostname (checked)
Hostname: <enter your DDNS service domain here>
User: <enter your DDNS user account name>
Password: <enter your DDNS user account password>
Click "Done."
AirPort Utility > Select the base station > Manual Setup > Disks > File Sharing tab > Share disks over the Internet with Bonjour (checked)

Confusion on setting hostname and DNS

Similar Messages

Maybe you are looking for