Windows 7 stopped resolving fqdn with primary dns suffix when not connected to domain
This is a split dns scenario. When client is connected to domain via LAN or VPN, name resolution for primary dns suffix works fine. But as soon as the client is on a different network it cannot resolve hosts with primary dns suffix, despite there are several external registered hosts in public dns. Network monitor shows that the client does not even try to resolve the names, but instantly responds to ping with "Ping could not find host <fqdn>. The hosts are reachable using ip address. Any suggestion? Ole Thomsen
July 26th, 2010 8:30pm

The problem is the same when you are using another client computer? Best regards.
Free Windows Admin Tool Kit Click here and download it now
July 27th, 2010 12:34am

Hi, Thanks for posting in Microsoft TechNet forums. I am assuming that the DNS cache might be corrupt while disconnecting to Domain. Please flush DNS and test again, type: ipconfig /flushdns , then type: ipconfig /registerdns. If the issue persists, please manually add the primary DNS suffix in the TCP/IP Advanced Properties of the network adapter. 1) Open Network and Sharing Center, click Change Adapter settings. 2) Right click the Network Adapter and click Properties. 3) Click TCP/IPv4, click Properties. 4) Click Advanced tab, click DNS. 5) Select “Append these DNS suffixes (in order)”, click Add. 6) Type the primary DNS suffixes of your domain, click Add. 7) Click OK. Now resolve the computer again to see if it works. Best Regards Dale Qiao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
July 27th, 2010 5:23am

We have several hundred laptop clients in the network/domain, noone else reports this error. Ole Thomsen
Free Windows Admin Tool Kit Click here and download it now
July 27th, 2010 2:06pm

Try to do what is mentioned in this procedure and check if the problem is persisting: 1-Verify that you are using the correct IP address of the DNS server 2-Verify that the DNS client service is started (Start>RUN>services.msc) If the DNS resolution still not possible, disable your internal firewall and check if the problem is solved. (Use only FQDN names like dc1.microsoft.com because the non resolution of DNS names like dc1 is another problem which Mr Dale Qiao gave you the solution) Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Best regards.
July 27th, 2010 3:23pm

I've used ipconfig /flushdns and /displaydns along with Network Monitor to troubleshoot this for days without noticing anything out of the ordinary, except being unable to resolve ourdomain.tld when not connected to the LAN. Making a static primary suffix for the network adapter did not make any change. This was expected as the error persists on all available connections, cable, wireless and wireless broadband. I'm sure this a result of some installation/configuration change I've done, or a sideeffect of troubleshooting something else. But as this started months ago I have no chance remembering what :-) All I remember is that at some point I had to use the IP address for connecting to our VPN server because the name could not be resolved. Ole Thomsen
Free Windows Admin Tool Kit Click here and download it now
July 27th, 2010 6:28pm

Have you tried to follow the procedure I gave you? Best regards.
July 27th, 2010 6:34pm

I have no problem with DNS servers, as all other domains resolve fine. I use the laptop a lot out of the office, and never noticed anything around DNS except this strange problem with not being able to resolve our own hosts. Ole
Free Windows Admin Tool Kit Click here and download it now
July 27th, 2010 6:36pm

Try to repair the Microsoft Windows operating system of your laptop. I think it will resolve the problem you've got. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Best regards.
July 27th, 2010 6:42pm

Have you tried to follow the procedure I gave you? Best regards. Yes, it made no difference. Ole Thomsen
Free Windows Admin Tool Kit Click here and download it now
July 29th, 2010 4:05pm

It is a strange problem. Try to repair your operating system installation. Best regards.
July 29th, 2010 4:18pm

Hi Have you scan your pc iwth malwarebytes. can you check you host file as well please. has the host file been modified. thanksNaeem Bhatti MCITP EA, MCITP, MCTS Exchange 2007 MCSE security,MCSE AD, MCSE in Messaging, MCDST SBS2003 and SBS2008 Specialist
Free Windows Admin Tool Kit Click here and download it now
July 29th, 2010 5:11pm

If the host file had been modified, to repair the operating system install will solve the problem. It is for that I proposed it as a solution. Best regards.
July 29th, 2010 5:13pm

Hosts file is ok. It is not that big a problem for me to want to go into repair or reinstall. Thanks, Ole Thomsen
Free Windows Admin Tool Kit Click here and download it now
September 23rd, 2010 12:46am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics