Home › Forums › OS X Server and Client Discussion › DNS › Leopard Server DNS
I’ve just purchased Leopard Server to run on a Mac Mini and am in the process of setting it up to replace a Windows DHCP/DNS server.
Eventually I want it handle login accounts for both Macs and Windows computers completely replacing the Windows AD box.
I got the 2 services running now per Apple’s setup guide but upon testing discovered it does not perform Dynamic DNS.
A search through google pointed me to a doc that was put up here in 2006 to configure it.
“Combining DHCP and DNS” address: https://www.afp548.com/article.php?story=20060529143335323
Is this doc still valid? Its been 3 years now and I assume Apple’s built-in packages would have changed by now.
I’m not quite sure what you’re trying to do with it. If you tell me what you are trying to do, i.e. setup dhcp to resolve internal dns queries and still provide internet.
Just need a little bit more info. I know it’s been a while since your post, sorry.
Robert
[QUOTE][u]Quote by: guitar24t[/u][p]I’m not quite sure what you’re trying to do with it. If you tell me what you are trying to do, i.e. setup dhcp to resolve internal dns queries and still provide internet.
Just need a little bit more info. I know it’s been a while since your post, sorry.
Robert[/p][/QUOTE]
Off-topic, but that’s actually exactly what I’ve been trying to do for a while. I’m not able to get an FQDN on our schools DNS, so I need to roll my own for my lab. I’ll be running DHCP and NAT. I have gotten, barely, the DNS working enough so that a query in the lab to say server.film resolves to the server, but even with forwarding on, can’t get anything outside. eth(0) is on an outside accessible static IP, eth(1) will be serving up the IP addresses to the 30 iMacs in the lab (as well as being OD master). Any chance you can help?
I would be happy to help. The best suggestion I can make right now is to setup the dns server to forward non-authoritative queries to OpenDNS (my favorite)
208.67.222.222
208.67.220.220
just to make sure the forwarders work correctly; If you are on leopard server, the best thing to do would be to use the setup wizard under one of the services (dhcp or gateway or nat?).
To test if the dns server is the problem, type in 74.125.157.147 on the server in a browser and see if it resolves to google. Then type 74.125.157.147 in a client browser and see if it does the same.
I am away from high speed internet access right now and a connection to my server, but when I get home on Sunday, I will post a guide that should work if I can figure it out with my existing services. I don’t have a clean install to test it on right now (and I don’t want to mess up what I have 😀 ). (Just for the record, I use OpenSUSE with Webmin installed to provide dns, but I have gotten Mac to work (eventually)).
I assume that you are using a setup with an internet router that connects to your server through a lan and that you need different dns servers for each area of your building.
If you can have the same dns server provide answers to the whole building, you could have the router provide the ip of the one server to all of the clients in the building for dns and connect the iMacs directly to the router (not quite sure of your setup there).
I will do my best to help and good luck,
Robert
I was able to access my server a bit sooner than I thought.
In Server Admin:
On the overview tab of the NAT service, there is a button in the bottom right corner of the screen that says gateway setup assistant. Click it to automate the setup of the gateway. This will overwrite your DHCP subsets, but it will not be that difficult to set them up again. When you get to the part that asks for the gateway WAN interface, make sure you select the interface with the internet connected. You can verify this using the network settings in system preferences – NOTE: these will not necessarily match eth0 (or en0) and eth1 (or en1) in order. Then when it asks which LAN interfaces to use, make sure you use the other ethernet that you did not use previously.
Finish the wizard. Make sure that the DNS, DHCP, and NAT services now are all running.
Switch to the DHCP service and click on the Subnets tab.
There may or may not be a (few) subnet there already. If there are, delete them all; we will start from scratch.
As a demo:
Add a new subnet.
For the subnet name (for example) type 192.168.1
For the starting address, type 192.168.1.2
For the ending address, type 192.168.1.199
For the subnet mask, type 255.255.255.0
For the network interface, make sure you are using the port that the clients are connected to by checking it with the network utility (not system preferences).
For the router, type the address of the router that your server is connected to (from system preferences). (I’m not sure if this will work for you. You might have to enter the ip address of your server?? If it doesn’t work the first way, it can’t hurt to try :D)
Under the DNS tab, type the ip address of your server. You can also enter any LDAP info and WINS info you need to, but that won’t have a bearing on the internet.
You can substitute any ip address you wish for the demo as long as they follow a conventional scheme. If there is no way you can make it work with your ips, try the same ips as the demo here.
Lastly, test the clients! Hopefully this will work. If not, I might be free sometime next week. I can setup a remote session with a vpn. If you wish to do this, contact me through my site [url]http://www.studiosoundandvision.com/[/url]
I imagine you want this fixed soon with the school year starting 😯
Good Luck,
Robert
I’m 90% of the way there.
I’ve got DNS, DHCP, and NAT up and running. My server has an external IP (say 10.0.1.52) and the second interface is 192.168.1.1 and is sharing the external with DHCP now over the 192.168.1.x
DNS is setup to forward all non-authorative inquiries to the external DNS. All services in and out on server work fine.
The second interface goes to the WAN port on an airport base station which is setup to just forward everything on. If I associate a client computer with the airport it gets a valid IP (say 192.168.1.120) from my server. It can see my server fine (can open lab.beta.karr in safari just fine). If I use lookup to search for lab.beta.karr I get back its 192.168.1.1 address, if I reverse lookup 192.168.1.1 I get the correct domain. If I lookup google.com I get the correct info from the forwarded DNS server. Looks like everything SHOULD work fine, but now for the weird part: I can’t actually access google.com (or any external site for that matter). Lookup finds them, but no access. Even if I try the IP for google.com, no luck.
Anyone have any suggestions?
Not sure if this will help but…
If you try to access the site from the same client computer every time, you might want to flush the dns cache.
In addition to this, clear the history, cookies, and caches of Safari.
To flush the dns cache, open terminal and type
[code]dscacheutil -flushcache[/code]
This has helped me many times when my dns was failing in a browser.
Because the ip doesn’t work either, nslookup is probably using a cached record for google.
Try nslookup google.com again after you flush the cache.
Good Luck,
Robert
Just a thought I had…
Try turning the firewall off on the server if it is running (Gateway Setup turns it on by default). The Mac Firewall has caused me so many problems 😡 I can’t even begin to explain.
Good Luck,
Robert
Firewall was off…
After replicating your configuration, I have found the solution!!! 😀
However, you won’t believe me until you try it.
As a preliminary test, open system preferences > network and choose the gear-wheel icon in the bottom left and choose set service order. Drag ethernet 1 to the top and ethernet 2 right below it. Click ok then apply settings. Now verify that the server itself is able to access google.com.
Now for the REAL problem…
The problem was AGAIN the firewall, only this time BECAUSE it was off.
[code]To fix your problem, turn the firewall on and try to access the internet from the clients[/code]
To me this would sound like a far-fetched fix if I had not experienced this problem myself.
If you notice any lags in services on the server, I’m sure the firewall will be the problem. I suggest using another computer, maybe running linux? 😀
Really hope this will do it for you. If you still have problems, try the gateway setup assistant to configure the firewall for DHCP and NAT.
Good luck once again,
Robert
[QUOTE][u]Quote by: guitar24t[/u][p]After replicating your configuration, I have found the solution!!! 😀
However, you won’t believe me until you try it.
As a preliminary test, open system preferences > network and choose the gear-wheel icon in the bottom left and choose set service order. Drag ethernet 1 to the top and ethernet 2 right below it. Click ok then apply settings. Now verify that the server itself is able to access google.com.
Now for the REAL problem…
The problem was AGAIN the firewall, only this time BECAUSE it was off.
[code]To fix your problem, turn the firewall on and try to access the internet from the clients[/code]
To me this would sound like a far-fetched fix if I had not experienced this problem myself.
If you notice any lags in services on the server, I’m sure the firewall will be the problem. I suggest using another computer, maybe running linux? 😀
Really hope this will do it for you. If you still have problems, try the gateway setup assistant to configure the firewall for DHCP and NAT.
Good luck once again,
Robert[/p][/QUOTE]
As I’d tell one of my kids, “You’re a rockstar!” Turning firewall on worked. Why it worked I have no clue, but it did the job. Thanks again. With a full lab of new iMacs and being the only mac person in the district it’s nice to be able to give my kids mobile accounts and actually have all the wonders of Mac OS X server work for them.
-eric
No problem, glad I could help.
Robert