Airport extreme passing incorrect DNS details to clients?

Question

Level 1

0 points

Airport extreme passing incorrect DNS details to clients?

Hi

I have opted to have OSX act as a DNS server and have entered my ISP DNS details as the forwarding DNS servers. My server's network address is 192.168.0.4 and my airport extreme is 192.168.0.1. In airport extreme I have entere my server as the sole authority for DNS lookups ( 192.168.0.4). My server The problem is that when a client attaches to my network via wifi the DNS details autopopulate as 192.168.0.1 instead of 192.168.0.4 and they have no internet access. What am I doing wrong? I can manually fix this everytime but it's a pain

Thanks

Damian

Posted on Dec 12, 2013 9:32 AM

Reply

Answer 1

cpragman

Level 2

465 points

Dec 12, 2013 4:44 PM in response to dazza222

Airport Extreme config screens have two fields in which to enter DNS server addresses. Make sure you enter your server's internal IP address in both fields. Otherwise the AEBS tends to ask the upstream router for a DNS server to populate into the second field. Your clients can be offered either address, and whenever they are offered the external one, your clients won't see the server.

By manually populating both fields, you prevent it from automatically populating the second field from it's upstream DHCP feed.

Reply

Answer 2

dazza222 Author

Level 1

0 points

Dec 13, 2013 12:28 AM in response to cpragman

Thanks for your help. I have already filled both fields on the AEBS in with 192.168.0.4 (the server) and still have the problem.

Reply

Answer 3

Dec 13, 2013 1:16 AM in response to dazza222

How are IP addresses assigned to your client computers ? Is every client computer configured with a fixed IP address or are you using DHCP to hand out IP addresses ? If so, which device is running your DHCP service ?

Reply

Answer 4

dazza222 Author

Level 1

0 points

Dec 13, 2013 10:17 AM in response to Simon Slavin

Eureka! Turns out both the AEBS and Server were running a DHCP service. I've turned DHCP off on the server and that has fixed the problem. Thanks!

Reply