Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Use different DNS servers for different domains' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Use different DNS servers for different domains
Authored by: kyngchaos on Dec 19, '05 01:50:12PM

(Reviving an old hint)

No luck with this. Tried both Panther and Tiger. Adding this resolver file has no effect on where Mac OS X looks for DNS. It always tries the first DNS server listed in the System Prefs-Network that is reachable, starting with the primary (builtin) ethernet. And reachable seems to mean the first network port that is active, without even trying to contact the DNS server.

So:

Builtin: network 192.168.1.x, foo.bar domain, DNS 192.168.1.100
Airport: network 192.168.2.x, nowhere.net domain, DNS 192.168.2.200
zaphod is a Mac on the nowhere.net network and has a DNS entry on 192.168.2.200

/etc/resolver/nowhere.net:
nameserver 192.168.2.200

if both network connections are active on the Mac, and both DNS servers are running, nslookup zaphod.nowhere.net returns domain not found, and says it tried 192.168.1.100 - not what I told it in the resolver file!

If both connections are active, but 192.168.1.100 is not reachable for some reason, nslookup times out trying to reach it, and doesn't try 192.168.2.200.

If the Builtin ethernet is disconnected, and wireless is connected, all lookups will go thru 192.168.2.200. zaphod.nowhere.net will just happen to work now.

It seems that some Mac OS X configuration thing must be overriding this resolver feature.



[ Reply to This | # ]