Weird DNS resolution problem

[nrg2go]

problem: can't resolve IP address on WAN

ipconfig /all points me to the correct dns server

nslookup uses the correct dns server

typing the address in nslookup DOES resolve to the IP

by doing an ipconfig /release and ipconfig /renew the PC now resolves the address fine.

However, in a day or two the problem will be back . . .

any ideas????

 

[LiverpoolFan]

Are you using WINS? And when do you get name resolution issues? When you try to connect or ping?

If it is when you connect can you ping by name?

The reason I ask is because Windows when you connect to another machine as standard uses WINS while Ping will use DNS first.

 

[nrg2go]

The problem occurs both when trying to open a web page on the WAN web server and when trying to ping the server name. Of course, ping by IP is not a problem.

Thanks for your question.

 

[TheRing]

Try with cleaning the cache of the dns by using the command: ipconfig /flushdns and then ipconfig /registerdns to get new info into the cache.

 

[wilson0728]

Don't know if this will help or not but here it is. We had a very similar problem when some made some static ARP entries on the domain (don't know why). Whenever you cleared the arp cache on your machine or did a REPAIR on the network connection (which clears the arp cache) it would work. The fix was having the network admin fix his static arp entries. Maybe this will lead you someway.

 

[theo1881]

seems odd and as last post not sure this will help but have you checked the hosts file ?