My airport is passing along 3 DNS server addresses to my systems - and I DON'T WANT the third...

I want my airport to pass along my server address for DNS resolution (10.0.0.2) and OpenDNS 208.something.something.something. I get a third piggybacking along to my machines in the house from ComCast. Now, I don't want ComCast DNS for many reasons, including the fact that we use OpenDNS to limit what is passing onto kids machines.


Since not all the machines that parade through my house are under my control, so I can't just lock down the kids computers and call it a wierd war, but at least get to a truce.


Anybody seen this before and have an answer as to how to get my airport to behave? Core airport in the network is an AirPort Extreme (Simultaneous Dual-Band) which is what is supposed to be passing out DHCP, is hooked into the cable modem, and backbones both the wireless networks and the wired networks in my house.


Thanks in advance,


Ziger.

Posted on Apr 26, 2011 7:09 AM

Reply
6 replies

Apr 27, 2011 8:56 AM in response to Ziger

If I understand you correctly, you have a server on your local network that is performing as a DNS server ... correct?


If that is the case, then this DNS server will conflict with the DNS addresses coming from the DHCP service provided by the AEBSn. To verify that this is the case, temporarily disable your DNS server. Do the network clients now only get the two DNS IP addresses from the AEBSn now?

Apr 27, 2011 12:49 PM in response to Tesserax

None of my equipment has comcast inserted as a DNS server.


I have a local server who performs as a DNS server. It uses the OPENDNS entries for external search. If I only put in 1 entry on the Airport, I still get the comcast entry. So I tried two of 10.0.0.2 entries, which got me three entries on the client computers - two 10.0.0.2 and one from Comcast again. So I put in the OPENDNS entry and my local DNS server and now get three DNS entries propagating to the clients...


Removing my server from the network and changing to only OPENDNS entries in the Airport is not changing anything.


Intent was to ONLY give the clients the 10.0.0.2 DNS entry, but I didn't mind failover to an external DNS. But I don't want ComCast EVER.


That make sense?


Ziger.

Dec 2, 2011 10:00 PM in response to spazeman

Nope. Apple support haven't a clue. Even talking to Enterprise and Server support didn't get a straight answer. My theory is that if you do not have two valid and different DNS IP Addresses to fill in, Apple airports simply pick up the additional information from DHCP, and ignore any more info you give them. Stupid setup, especially in this case.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

My airport is passing along 3 DNS server addresses to my systems - and I DON'T WANT the third...

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.