DNS sporatically cannot resolve hostname

[flubbard]

I have a Windows 2000 server serving as the DNS server on our company intranet. I also have a linux server acting as our main intranet webserver. Recently, I had to change the address of the Linux box so that it was consistent with the address scheme. Prior to the change, I had no problem resolving the name (Typically trying to resolve from a Windows XP Pro machine). After the move, the address resolves for a while, but randomly (seemingly) the address can no longer resolve. If I do a "repair" operation on the XP machine, the name will resolve again.

When I changed the address, I removed the entries in the forward and reverse zones and created a new host with the associated pointer for the host at the new address.

Any suggestions would be welcome.

 

[GlenJohnson]

Using dhcp or fixed? Anything in the logs showing problems? I had a machine that wouldn't resolve, and I found it was losing it's ip. Created a batch file that said

Ipconfig /release
Ipconfig /renew

and placed a shortcut to the file on the desktop. If I couldn't connect to the net, running the batch file worked great. (Problem was with my ISP, but my fix worked until they admitted the problem.) Good luck.b

Glen A. Johnson
"Fall seven times, stand up eight."
Proverb

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

 

[flubbard]

The XP machines are using DHCP. They retain their address even when they cannot ping the host that moved. They can still ping other computers on the network by name and ping the host using the ip address. The DNS just won't resolve the name for the linux host until I do the repair operation.

 

[flubbard]

In case anyone else encountered this. I was eventually able to get the machine to recognize and hold the new address for the server by flushing the dns. Did this by using the command ipconfig \flushdns
This was run on the dos machine trying to connect.