Strange DNS problem

[Peter]

Hi,

I have a PC running win2k sp4, accessing the net via a Draytek router.
Several other PCs are connected to the same router, all via ethernet.

DNS is as usual via DHCP.

Every 10-20 mins, I find that I can't get onto any websites. Running

ipconfig /all

shows the ISP's nameservers are still shown correctly, and I can ping
an outside IP but cannot ping the equivalent name (e.g.
www.cisco.com).

If I do ipconfig /flushdns followed by ipconfig /renew that *appears*
to fix it but that could be just coincidence, as it seems to fix
itself eventually.

The other PCs don't show this problem at all.

What could it be?


Peter.

 

[Santhosh Sivarajan]

Do you have a DNS server?

 

[Peter]

The Draytek router is the DHCP server, otherwise the system wouldn't
work at all. It issues IPs to several other PCs on the LAN, and they
work fine at all times.

For some reason, this particular PC (only) has problems accessing
objects on the internet that require a name lookup. It never has
problems accessing them by their IP. Whenever I get the problem, I do
"ipconfig /all" and I can see that the ISP's DNS server IPs (two of
them) are shown correctly.

What could cause for example a failure of the ISP's nameservers, for
this PC only?

Do you have a DNS server?

Peter.

 

[Peter]

In case anyone is interested, having got no response here I did a
google search and found that this has happened to others. The fix is
to disable the windows DNS service. This works perfectly.

It looks like there is something in the DNS service which causes total
loss of DNS lookup.

Hi,

I have a PC running win2k sp4, accessing the net via a Draytek router.
Several other PCs are connected to the same router, all via ethernet.

DNS is as usual via DHCP.

Every 10-20 mins, I find that I can't get onto any websites. Running

ipconfig /all

shows the ISP's nameservers are still shown correctly, and I can ping
an outside IP but cannot ping the equivalent name (e.g.
www.cisco.com).

If I do ipconfig /flushdns followed by ipconfig /renew that *appears*
to fix it but that could be just coincidence, as it seems to fix
itself eventually.

The other PCs don't show this problem at all.

What could it be?


Peter.

Peter.