dns client cache

[Simon Felix]

hi there,

absolute newbie here.


my problem is: even after "ipconfig /flushdns" the client doesn't do a
new lookup for some hosts. here's what i tried:

_______________________________________________________________

C:\>ipconfig /flushdns

Windows 2000 IP Configuration

Successfully flushed the DNS Resolver Cache.

C:\>ping cultris.ath.cx

Pinging cultris.ath.cx [62.167.25.45] with 32 bytes of data:

Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.

Ping statistics for 62.167.25.45:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>nslookup cultris.ath.cx
Server: cn005.royalinc.royalinc.net
Address: 192.168.1.5

Non-authoritative answer:
Name: cultris.ath.cx
Address: 84.227.72.55

_______________________________________________________________


i expected that "ping cultris.ath.cx" would reveal that this address
belongs to the ip 84.227.72.55 (just like nslookup did). why not?

62.167.25.45 is ~10 minutes old.



how the heck can i force win2000 to query my dns-server again?

regards,
simon

 

[Jaap de Koning]

Isn't the host cultris.ath.cx present somewhere in a local hosts file?

Otherwise, you can also try to clear your netbios cache using nbtstat
-R

 

[deji]

In addition to what Jaap said, I have also seen situtations where /flushdns
does not do the job. In this situation, I use "net stop dnscache& net start
dnscache" form a cmd prompt and that has always worked.

Deji

 

[Simon Felix]

i haven't had the problem so far - therefore i was unable to test your
suggestions.


simon


btw: i bought myself a static ip yesterday. that'll help too

 

[Simon Felix]

neither "nbtstat -R" nor "net stop dnscache"/"net start dnscache" made
any difference.


is there another way to clear another cache?



regards,
simon

In addition to what Jaap said, I have also seen situtations where /flushdns
does not do the job. In this situation, I use "net stop dnscache& net start
dnscache" form a cmd prompt and that has always worked.

Deji

hi there,

absolute newbie here.


my problem is: even after "ipconfig /flushdns" the client doesn't do a new
lookup for some hosts. here's what i tried:

_______________________________________________________________

C:\>ipconfig /flushdns

Windows 2000 IP Configuration

Successfully flushed the DNS Resolver Cache.

C:\>ping cultris.ath.cx

Pinging cultris.ath.cx [62.167.25.45] with 32 bytes of data:

Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.

Ping statistics for 62.167.25.45:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>nslookup cultris.ath.cx
Server: cn005.royalinc.royalinc.net
Address: 192.168.1.5

Non-authoritative answer:
Name: cultris.ath.cx
Address: 84.227.72.55

_______________________________________________________________


i expected that "ping cultris.ath.cx" would reveal that this address
belongs to the ip 84.227.72.55 (just like nslookup did). why not?

62.167.25.45 is ~10 minutes old.



how the heck can i force win2000 to query my dns-server again?

regards,
simon

 

[Kevin D. Goodknecht Sr. [MVP]]

In

neither "nbtstat -R" nor "net stop dnscache"/"net start dnscache" made
any difference.

Have you checked the hosts file?

Do you get the same ping results when the DNS Client Service is stopped?