I've been trying to solve this issue but so far the answer has eluded me. I am attempting to test out a server locally before I configure my external host. Since this is going to act as a web server/DNS, I am running bind on it; BIND is configured with forwarding and recursive lookups disabled. In order to test it I am adding an entry in my network config DNS settings (on the Leopard machine) that points to the local server followed by my primary DNS. For some reason, Leopard refuses to try to secondary DNS and, instead, tries the first one and fails the lookup.
The settings are sticking correctly as scutil outputs (truncated):
and my local resolv.conf correctly lists both nameservers. nslookup also correctly notices that the top server doesn't find anything or support recursion so it immediatly switches to the second server and successfully performs a lookup; nothing else will perform any lookups correctly however (Firefox, ssh, Mail, etc). Has anyone run into this before?
The settings are sticking correctly as scutil outputs (truncated):
Code:
resolver #1
domain : lan
search domain[0] : lan
nameserver[0] : 192.168.0.20
nameserver[1] : 192.168.0.1
order : 200000and my local resolv.conf correctly lists both nameservers. nslookup also correctly notices that the top server doesn't find anything or support recursion so it immediatly switches to the second server and successfully performs a lookup; nothing else will perform any lookups correctly however (Firefox, ssh, Mail, etc). Has anyone run into this before?