Name resolution stops working after some time, dnscache needs a stop and
start
I have a Windows 2012 Server (on Windows Azure), with AD Controller and
DNS on it. Next to that, I have another machine, who is domain joined.
Now I can ping from the AD controller to that other machine using the FQN:
C:\Users\Alexander>ping exsertuscdtest.exsertuscd.local
Pinging exsertuscdtest.exsertuscd.local [10.0.0.5] with 32 bytes of data:
Reply from 10.0.0.5: bytes=32 time=1ms TTL=125
Reply from 10.0.0.5: bytes=32 time<1ms TTL=125
Reply from 10.0.0.5: bytes=32 time<1ms TTL=125
Reply from 10.0.0.5: bytes=32 time<1ms TTL=125
Ping statistics for 10.0.0.5:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
So, no problem here. But after a while (like 20 minutes), I'm not able to
ping anymore:
C:\Users\Alexander>ping exsertuscdtest.exsertuscd.local
Ping request could not find host exsertuscdtest.exsertuscd.local. Please
check t
he name and try again.
Ping with IP address works without any problem. The only thing that helps is:
C:\Users\Alexander>net stop dnscache
The DNS Client service is stopping.
The DNS Client service was stopped successfully.
C:\Users\Alexander>net start dnscache
The DNS Client service is starting.
The DNS Client service was started successfully.
I can then ping the machine again using the FQDN. There is no
error/warning in event log or whatsoever.. I have no clue what is
happening?
Anyone?
No comments:
Post a Comment