DNS problems

[Kurt111780]

Hello,

We have an sbs2003 server. DNS does not seem to be setup properly. The server is set to use itself as the DNS server. On the server I can get to most websites however, yahoo doesn't come up at all and Symantec live updates take a really long time. If I use our ip DNS server 206.141.193.55 as secondary in the network connection properties then the problem goes away. This is the same ip address in the forwarders tab.

The workstations dynamically obtain the server as the primary DNS and 206.141.193.55 as the secondary. If I disable the dynamic DNS entries and punch in the server ip then the work stations have the same exact problem as the server, can not get to yahoo and a few other sites. The majority of the websites work fine.

Using the server ip as the DNS does not work correctly. Some sites are slow and others do not come up at all.

Any suggestions or things I could check?

Thanks,
Kurt

 

[serhino320]

Kurt-

Is this something that just started happening or did you just set up DNS? One thing I would check is the Root Hints tab under the DNS server properties settings (right click on the computer icon in DNS, not in your zones) Do you have any Root Hint servers listed? If you remove the forwarder (your ISP's DNS server) then your DNS server should be using its' root hints to locate the appropriate DNS server for resolution's it does not have cached or in its' zone records. I would start by seeing if your server is able to resolve on its' own using just root hints. I'd remove you ISP's Ip number from network properties as well to start.

 

[Kurt111780]

Hi,

DNS was just setup on this server. I checked the Root Hints tab and several were listed. I removed the dns servers from the Forwarder tab. After I did that it was able to resolve DNS on its own, sorta. Connecting to the symantec server still takes forever and yahoo only half loaded. The graphics did not load. I then put the dns servers back into the forwarders tab and then yahoo did not work at all. Added the dns server back as the secondary in network properties fixes the problems.

Kurt

 

[technome]

Search google for EnableDnsProbes

http://www.tek-tips.com/viewthread.cfm?qid=744486

 

[Kurt111780]

This command seemed to have done the trick. Though I'm not exactly sure what it did. Restarting the server tomorrow, I'm wondering if it will continue to work then.

dnscmd /Config /EnableEDnsProbes 0

We do have a Pix firewall and I found there answer here as well.

http://www.tek-tips.com/viewthread.cfm?qid=743698

Thanks,
Kurt

 

[technome]

This is a sneaky problem affecting many.