Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am trying to set up Address Book server in Mac OSX Snow Leopard server. To do this, a requirement is that I have a FQDN set up with reverse lookup. I created a DNS entry on the godaddy DNS server to link to my static public IP address. How do I set up reverse lookup on my private DNS server so that it talks to the Internet DNS servers for reverse lookup?

When I use the Network Utility on the server, the FQDN I have set up resolves correctly to my static public IP address, but I cannot figure out how to get the reverse lookup to resolve correctly.

I am somewhat new to managing DNS, so this may be a simple fix, but I just can't figure out what to do.

Thanks

share|improve this question
add comment

1 Answer

The reverse DNS records should generally be handled by your ISP (they "own" the IP number, so the reverse DNS for it gets delegated to them). Contact your ISP's support to find out how to have them set it up.

If your server is behind an NAT (network address translation, i.e. it has a private internal address as well as its public address), you'll also need to set up internal DNS (both forward and reverse) with the internal numbers instead of the public numbers. You can do this in OS X's DNS service by creating a forward zone and machine record for your server, and it'll create the reverse info automatically.

Suppose your server's full DNS name is server.example.com, and its internal IP address is 192.168.1.5. You'd create a zone named "server.example.com." (be sure to include the trailing period), and add an entry to its Nameservers list with both the Zone and Nameserver Hostname set to "server.example.com.". Then, add a Machine (A) record to that zone, with the Machine name "server.example.com." (again, the trailing period is very important), and the IP address 192.168.1.5.

Once that's set, start the DNS service, and configure your server's network preferences to use 192.168.1.5 as its DNS server. If you have other computers on the network with manual IP setups, change them similarly. If you have a DHCP server running, set it to hand out 192.168.1.5 as the DNS server. That should do the trick.

share|improve this answer
    
I currently have my server named "server.local." Does this mean that I need to change the name of my server to "server.example.com?" (supposing my FQDN is example.com) –  advis12 May 12 '11 at 19:40
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.