Originally Posted by downquark1

Same here, but I did have some problems getting armerican sites earlier that day (on a non-ntl connection)

Originally Posted by zovat

Also if you read the very long thread about what went on - other ISPs were having similar issues - including freeserve and BT .

personally - I think NTL saw it as a DNS issue (after all it would not be the first time ;) ) and did not update everything when they realised it was something bigger... I'm just glad it seems to be working at the moment. :smokin:

Originally Posted by patrick73

The reason NTL users are experiencing redirects to our website is because NTL's tranparent web caches are not resolving host names correctly. They are not following the chain of authority for the internet name space as defined by the root servers ultimately run by ICANN.
NTL has been aware of this for a number of months (when this last happened) and have still not fixed it.

Originally Posted by rodd

Well at the moment the only way I can get here is through Freeserve.

I don't know if the following comment is related to what is wrong with ntl's crappy caches and DNS, and maybe they are trying to sort it out now.

Originally Posted by Dooby

if anyone here has any contact with any NTL bods in charge of networks, can you please explain to them that the reason for having TWO ( or more ) DNS available is so that if the first one fails, the second is still available....

how come NTLs seem to fail together? are they connected to the same cable segment or something? wouldnt it make sense for them to be phisically seperate ( perhaps different ends of the country? )
or am i missing something?