I can’t get DNS to work

[gspiese]

I’m trying to setup an OS X Server v10.3.8 so I can keep User folders on the Server. I want to use LDAP and Open Directory. Apparently I need to setup a DNS to do this. I don’t run a DNS locally but Server requires I do to get the services I want to run. My Host Name is geo.server.net and the IP Address is 192.168.1.25. After I setup the Zone and create the NS and reverse lookup records I try to do a Lookup from another computer on the LAN. I’ve configured the Network Preferences to have a DNS of 192.168.1.25 on both the server and Mac client. From the client I launch Network Utility and do a Lookup of 192.168.1.25 and get the following:

Lookup has started …

Server: 199.224.86.15
Address: 199.224.86.15#53

** server can’t find 25.1.168.192.in-addr.arpa: NXDOMAIN

Doing a lookup of geo.server.net results in:

Lookup has started …

Server: 199.224.86.15
Address: 199.224.86.15#53

** server can’t find geo.server.com: NXDOMAIN

I understand what needs to happen: if 192.168.1.25 is entered it will be taken to geo.server.net and if geo.server.net is entered it will take it to 192.168.1.25. How in the heck to I make that happen? The DNS setup in OSX Server is clear as mud to me.

Thanks!

[stevie_w]

Is “server.net” your domain or are have you just made up a fake internal domain for your own network?

If you make up a fake internal domain, don’t have it end in a real top-level domain like “net” or “com” or you can get into some real DNS muddles. Don’t use “local” either as this is used by other stuff.

I’d suggest something like “lan” e.g “office.lan” if you go down the fake domain route.

You can see a list of real top-level domains (i.e. ones to avoid) here:
http://www.norid.no/domenenavnbaser/domreg.html

Of course, if “server.net” really is your domain, then none of the above applies.

[Author]

Posts