Why do I keep having to /flushdns /registerdns??

[IanGlinka]

I added a host named "affinity" to my DC's DNS forward lookup zone and pointed it toward a server at the opposite end of a LAN-LAN vpn tunnel that we have set up with a hospital. It works in the sense that if you "ping affinity" it resolves it to an IP address, and the echo replies come back fine. However, sometimes, it just stops working on what seems to be random workstations. I must then go to those workstations and run "ipconfig /flushdns" then "ipconfig /registerdns" - After I execute those two commands, the host name resolution works just like it did before, and just like it is supposed to.

Any ideas why this is happening?

Thanks!
Ian

 

[thawk10]

IanGlinka,

Did you find a resolution to this problem?? I am having the same problem and am unable to find a fix.

If you have found the solutions could you please share it with me??

Thanks.

 

[ITPangaeaArchitect]

are the workstations and other server on the same domain as the DC?

what is your scavenging interval?

-Brandon Wilson
MCSE00/03, MCSA:Messaging, MCSA03, A+
almost got a paragraph there