DNS problems with Snow Leopard 10.6

I’ve had some bizarre problems with my DNS today. I checked /etc/resolv.conf but everything looked ok. Checked the settings dialog for my network and at first glance, that one seemed ok as well.

Screen shot 2009 09 09 at 00.34.55 300x252

But normally there should be a dimmed version of the DHCP assigned values there.

Screen shot 2009 09 09 at 00.35.08 259x300

Just select the empty one and press the minus sign. Sneaky little bug there!

Screen shot 2009 09 09 at 00.35.16 227x300

Save your settings and you should be good to go.

Comments

  1. tim crawford says

    Has this fix stuck? I am having bizarre DNS issues with a client’s system that was just upgraded to 10.6. I will try this fix on Monday.

    Thanks for posting.

  2. Brad says

    Yeah I am having this problem strictly with corporate network web servers and the Access server. No problem getting to public sites. Or getting to corporate sites when I VPN back into the network. I am on 10.6.1… I would of thought they would of fixed this between 10.6 and 10.6.1

  3. tim crawford says

    from other reading I have found that Apple now uses the mDNS responder to resolve DNS as well. This is just a big giant mistake. I believe the the problem is coming out because of a Windows .local domain being propagated. mDNS doesn’t like this.

  4. ralph says

    What is the relation between DNS and internal mail that doesnt send it to the recipient that i’m sending it. I received ERRORS for the local mail on the internal mail of the company , Am I missing something!!! i would appreciate any help, thanx in advanced

  5. ralph says

    What is the relation between DNS and internal mail that doesnt send it to the recipient that i?m sending it. I received ERRORS for the local mail on the internal mail of the company , Am I missing something!!! i would appreciate any help, thanx in advanced Mac OS Server snow leopard 10.6 I have Mac and inXP Pcs on the network that use internal mail

Leave a Reply

Your email address will not be published. Required fields are marked *