This discussion is archived
1875 Views 3 Replies Latest reply: Nov 13, 2007 12:16 PM by Leif Carlsson
Currently Being ModeratedNov 12, 2007 10:36 PM (in response to Jeff Lambert)It's in the logs : "no name available via DNS for myIPadress"
As you haven't got the DNS configured and running, the machine can't resolve it's IP address to a name : host <ip address of server>
You either have to configure (an internal) DNS (and use only that for DNS - preferably with forwarders - your ISP DNS IPs) or just ignor this in the log.
When setting up a server DNS should be setup first - either in the server itself or in an other machine running (internal) DNS for your LAN/domain. Some servcies require it.
Currently Being ModeratedNov 13, 2007 8:13 AM (in response to Leif Carlsson)Leif,
where do I setup my dns configured? In the network pref pane, I used my ISP's dns, so where else should I "forward" it? We don't have a "name" for the server that is registered on any dns server. We didn't buy a domain name, since this is not for web server. We have that hosted elsewhere. Why do I need to tell it that the server name is my.server.name.local which should map to 127.0.0.1 (or local host)?
since this is giving me two error message every half hour, this is not easy to spot a "true" error. So is there a way make that message not appear in the first place?
JeffMac OS X (10.4.10)
Currently Being ModeratedNov 13, 2007 12:16 PM (in response to Jeff Lambert)You don't HAVE to do anything. But if you don't you'll get the stuff you get in your log...
You can get by by using only Bonjour/mDNS names.
Configure DNS: Server Admin -> DNS
This is for 10.3:
You don't have to open any ports in the Internet router for an Internal DNS.
Forwarders speeds up lookups (ISP DNS are used for every other lookup than your internal domain.)
forwarders has to be entered in /etc/named.conf "by hand" (Leopard has added that functionality into the Server Admin DNS GUI).
You can make up you own internal domainname like <yourdomainname>.private or essentially anything you like (well if you choose apple.com you can't get to apples sites) as your server will think it's responsible for that domainname).
You could use <yourdomainname>.local but I would stay away from it not to confuse it with Bonjour .local, especially if you have Panther clients.
localhost point to 127.0.0.1 but your server/hostname should point to the LAN IP it has - single homed server on (private IP) LAN.
If you use only your internal DNS on your LAN it wouldn't make much sense having the servername point to the localhost IP when a client ask for the address to the server.