Ian said:
Don't know if it helps, but BT Internet connections using TI-chipset routers
(D-link, Safecom ect.) have developed problems with DNS proxying. The
symptom is that an NSLOOKUP of for example microsoft.com returns 1.0.0.0
instead of the IP.
The fault seems to be with the ISP's equipment, the same routers give no
probs on other services, and also used to work without DNS problems on BT
until recently.
A workaround is to set your computer to use a manually-assigned DNS of the
ISP's DNS servers, not the router's IP.
Might help:
http://www.btofaq.net/articles/sstatus1.html
Thanks Ian. That's a bit heavy for me, but I'll study and follow up
for future reference.
Meanwhile I'm happy to say I seem to be back to normal. I had
initially tried switching the router on/off without success (but
guess I waited only 4-5 seconds, and gather that might be inadequate).
Also rebooted. Eventually I got around to checking Services > DNS
Client. That was not started so I did so, and also switched it to Auto
instead of Manual. About the same time, before checking, I pulled and
replaced any phone line plugs I could see. Also once more switched off
the router, this time maybe for at least 10 secs. Happy to say I was
then back up and running OK. So still not sure what was cause/fix.
I think issue was also complicated by fact that I was trying to
download from a genuinely very slow site. Have since found this site
to test speed:
http://www.testmy.net/d_load.php
Three or 4 tests so far have given 3.1 - 3.9 Mbps (the last one a few
minutes ago), which I assume is OK. Before upgrading me from '2 Mbps'
to '6 Mbps' a few months ago, BT advised my line was 'capable of 4.4
Mbps'.
