You are currently viewing our boards as a guest which gives you limited access to view most of the discussions, articles and other free features. By joining our Virgin Media community you will have full access to all discussions, be able to view and post threads, communicate privately with other members (PM), respond to polls, upload your own images/photos, and access many other special features. Registration is fast, simple and absolutely free so please join our community today.
Same here, but I did have some problems getting armerican sites earlier that day (on a non-ntl connection)
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.
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.
perhaps there were more issues here than we have been told about. Its possible ntl took their dns offline,as it appeared to be a dns issue - that would be why i couldn't ping the dns servers. when they went back online and ppl still couldn't connect they must have realised there was something else afoot
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.
Quote:
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.
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?
Quote:
An NTL spokeswoman told The Register that because of knock-on effects users still experienced problems when traffic was re-routed (see NTL status page here).
Put under extra pressure, NTL's DNS servers failed, she said. That meant users were unable to log onto Web sites using their host name, even though the sites were reachable to users who knew their IP address.
Email and other services were hosed for the same reason.
Yeah right-it was that cable that's been causing the ntl mail server problems for the last 8 or so months was it?
Join CF
You are here: 
) and did not update everything when they realised it was something bigger... I'm just glad it seems to be working at the moment. 
