Quote:
|
Originally Posted by Cyrill666
Me too, as soon as I realised it was a DNS issue, I manually entered the addresses I use when at work and bang - all services return without problem.
|
Last night's problems have me confused:
1. I don't use NTL's DNS servers. The only time an NTL DNS should affect me is when one of their web proxies looks up a name.
2. Browsing was next to non-existent last night. But access to my 3rd party email provider (via non-NTL DNS lookup) was fine. I tried switching to different NTL web proxies, and also leaving it up to the local transparent proxies, all to no avail.
3. As soon as I switched to a 3rd party web proxy (a BT Openworld one, as it happens), browsing came back to life.
All the above would seem to suggest it was mainly an NTL DNS issue affecting their web proxies.
And yet, I was unable to ping many sites by explicit IP address (which shouldn't involve any DNS lookups). This suggests some sort of routing problem. Most of the unavailable sites were in the UK, so I don't see how a transatlantic link could be responsible. Access seemed to come and go at random. Maybe the inability to access by IP address was a side-effect of the transatlantic failure putting additional strain on intra-UK links?
If anyone can give a rational explanation for last night's outage that actually fits the symptoms, I'd be most interested.