humbletech99 Posted December 3, 2006 Report Share Posted December 3, 2006 I have a strange problem on my XP workstation at home. It seems that sometimes when I open a cmd window and try to reach a host I can't resolve the name. If I ping a hostname then I getping hostnamePing request could not find host hostname. Please check the name and try again.but when I immediately donslookup hostnameServer: dns1.mydomain.comAddress: 10.0.0.8Name: realname.mydomain.comAddress: 10.0.0.8Aliases: hostname.mydomain.comit shows dns working fine. If I then repeat the ping command expecting it to find the host it again fails the same.I am a dns administrator and am very confident regarding how this is supposed to work. I don't see why it fails to resolve the host when it worked fine a few mins ago. I am convinced this is a problem with the workstation.I have checked the hosts file to make sure there is nothing short circuiting the name resolution method and can see that the file is empty.The dns server is not loaded, it is connected to the same 100Mbit switch as the workstation and there is no other heavy traffic going on at the time.I just flushed the cache and it works again now. But I don't understand how this could happen. This setup is very simple compared to what I usually do. At exactly the same time I try these things from my Linux laptop it works fine showing that the problem appears to be confined to this workstation.The next time this happens I will look at the actual dns cache itself (can't now since I just flushed it - Doh).Any ideas or feedback welcome. Quote Link to comment Share on other sites More sharing options...
cozofdeath Posted December 4, 2006 Report Share Posted December 4, 2006 I know some internet speed optimizers change some dns registry settings to make the query timeouts/TTL shorter and I think clearing the cache sooner. Do you think someone may have installed something like this? Quote Link to comment Share on other sites More sharing options...
humbletech99 Posted December 4, 2006 Author Report Share Posted December 4, 2006 no, besides, the answer from the dns server will be the same as before since I'm using the same server and I haven't changed it's configuration. Quote Link to comment Share on other sites More sharing options...
Scarecrow Man Posted December 4, 2006 Report Share Posted December 4, 2006 I have checked the hosts file to make sure there is nothing short circuiting the name resolution method and can see that the file is empty.I trust it contains 127.0.0.1 localhostNot that this could be an issue, but you did say it was empty :)What do you do before the lookup fails? Have you tried it immidiatley upon recieving an IP address, or is it after a while? Quote Link to comment Share on other sites More sharing options...
humbletech99 Posted December 5, 2006 Author Report Share Posted December 5, 2006 I have tried it immediately, the time it takes to hit up up enter...I will have to post back when this happens again and look at it more closely before making it work again to try to find the root cause. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.