I have a little issue with my airport extreme. I'm using the device in my corporate network which has two DNS server for resolving intern and external names.
When I do an nslookup "public adresse" (such as www.google.com), everything works fine.
…But, when I try to resolve an internal name, for exemple bardo1, I get:
;;SERVFAIL reply from XXX.XXX.XXX.XXX trying next server
;;connection timed out; no servers could be reached
When I try nslookup internalservername my.internal.dns.server everything works thing.
Where is the problem ??? I don't get it.
Is it because apple uses a different way to resolve names then microsoft ?
How can I fix that on the router ? Not on client side…
My PC Config IP: 10.0.1.3/32 Gateway: 10.0.1.1 DNS: 10.0.1.1
Airport Extreme IP WAN: 172.16.1.117 DNS1: x.x.x.13 DNS2: x.x.x.45 domain: mydomain.local
Best Answer
Apple's DNS resolution expects a tiered solution, so you will want to simply point the router and clients to the internal DNS.
That DNS will answer all queries for it's internal responses and refer/forward requests outside it's authority to the outside DNS of your choosing.
In short, you will either need to change your internal DNS or set up a third DNS to know what requests to handle internally and which externally as the AirPort wasn't designed to do that choosing for you.
Here's how you would set up OS X server DNS to do forwarding - it's a simple pane where you place the external addresses.