BT DNS problems on .co.uk domains

[davesussex]

Since Tuesday morning i have found a few domains that i can no longer get, i get the page DNS Error / Page cannot be not found. I see there are other people on Twitter with similar issues on BT DNS.
 
Have been trying www.apronworld.co.uk which is fine on all my friends broadbands who are not on BT Broadband.
 
I am on BT Broadband, both in my office and at home, and neither can see the domains. I have spoken to many other people also on BT Broadband and they can no longer see the domains either. I have also tried getting the domains from NON BT ISPs, and all other broadband networks get them with no trouble, so it appears to be a BT DNS problem only. I have spoken to the webhost, who has checked all DNS settings which are fine, and i have checked on www.dnsstuff.com, and the tracert works fine also.
 
I have phoned BT twice in the last 2 days, but have heard nothing back so far. 

Anyone else have similar issues?
 

[Redflake]

Yes your right, just tried the link and it fails on BT dns settings. Changed network dns settings on pc to google dns settings (8.8.8.8 alternate 8.8.4.4) and works ok.

[gpierre]

as above

[NanoTm]

well to fix those problems gfolow this guide for win7 or vista.

1. Click the Microsoft Vista Start logo in the bottom left corner of the screen
2. Click All Programs
3. Click Accessories
4. RIGHT-click on Command Prompt
5. Select Run As Administrator
6. In the command window type the following and then hit enter: ipconfig /flushdns

for xp

start

run

type cmd.exe hit enter

In the command window type the following and then hit enter: ipconfig /flushdns

inall cases you will see the following confirmation;

Windows IP Configuration
Successfully flushed the DNS Resolver Cache.

this should remove all dns entries from the local table, then google for the address your looking for, click the link and you will be taken there, replace the favourits link in your pc,

the reason why this happened is becasue either the dns server has been compromised or (more likley atm) you went to a website that changed to a forced virus scan telling you about errors on your pc, that number counter was changing dns entries in your pc for common websites that have been replaced.

so flusshing the dns cache will clear the problem, now get some script blocker enabled for your browser and if your running vista or win7 switch uac on so you dont inadvertently try using a dodgy bank site before it gets shut down, theres no publicity becasue there no need to tell everyone that the sites are only available for about 30 seconds before there blocked by isp's hence the dns error's

[davesussex]

Hi folks,

Thanks for replies, yep tried flushdns etc, nothing like that cures it.

Yes changed dns server to google works, so like i said it is only BT DNS servers that have an issue.

Currently on the phone with BT, they have given me 3 dns settings none of which work, so hopefully they will now try and solve it.

[NanoTm]

its odd that your experiancing hte problem unless you setup a default dns server in eithre the pc or the hub,

personally i removed them and if i cant just run to the correct site i google it then go there and save it, it would appear the dns cache on my pc is quite large now but no matter if i need to i will flush it again seriously dotn preset a default dns server, i removed them last year when they were all getting compromised through various vulnerabilitys in the executable code, since then i rarely get a re-direct to one of theose not quite kosher websites, on the odd occasion i cant get to one by typing its address i simply search for it and then once its in the local cache it never gets any more problems

[Stanny]

Hi

I run a small web hosting business and have been experiencing the same problem with my domains.

For instance

www.scion.co.uk

www.countyalarms.co.uk

Resolve fine for myself to

77.240.2.194

87.237.58.161

However I am getting an increasing number of clients who cannot access these sites and get "Site not found" messages from their browser. A ping or tracert gives an "Unable to resolve target system name" message. Changing their DNS servers to Google's resolves the problem.

This affects BT and Virgin customers also, who I am informed use BT's DNS servers.

Not really sure what to do about this?

Ian

[davesussex]

Hi Ian,

Yes we have the same problems then, tracert does not work, ping does not work.

A few of the domains i cannot get are:

www.apronworld.co.uk

www.villaspain.co.uk

www.sussexsportscars.co.uk

Also same with it only being BT and Virgin customers who do not seem to be able to get the sites.

I am phoning BT everyday, plus leaving comments in forums and twitter, hoping that BT will finally do something!

Dave

[CBIL]

Similarly, we run a small web server for our clients, and are experiencing DNS problems across a number of networks - most appear to be related to BT customers, but also some Virgin and Orange customers are effected.

We've seen problems with access to all web services over the past 48 hours. We spent most of yesterday working on efforts to minimise DNS outage by adding 3rd and 4th nameservers (outside of our own nameserver) to all our domains. This seems to have has a positive effect, allowing some clients and customers to access web services again.

The main issue we're having at the moment is delivery of emails. Some emails get through straight away, others are taking hours or days. Some don't get through at all.

Our server is hosted with Rapidswitch, and we've seen a number of people with similar circumstances having similar issues, over the social networks.

We've done many DNS lookup tests over the last 48 hours, and results show that there are major DNS inconsistencies across a lot of networks, not just BT. Unfortunately, no one is taking responsibility or even admitting that there's anything wrong.

If anyone knows of further solutions, they would be most appreciated.

Thanks,

Matt

[NanoTm]

this happened afew years ago with most of the world being affected by the end of the week, last time it was caused by a bgp router naming problem, a new bgp peer was added to the backbone in one of the former soviet republics and it was the new 6digit name when a lot of the older routers could only resolve 5 digit headers, that stopped dns from working etc etc

it was identified and fixed by changing the header length on the new style router to 5 digits and after a few mins the as name state propgation had resolved most of the related problems.

there was supposed to be a mass upgrade program where all bgp owners would upgrade to the new standard compatable devices by 2010 however seeing the problems recently it is possible this has not happened, i would advise tech requests for any website or domain hosters to rectify this problem with your providers, for normal users the problem is dns lookup cant be established where the as name state is not wroking on the unresolved illegal header, its possible that the recent updates to secure dns servers restarted an age old problem of header length in the bgp as namestate protocols and so traffic cannot be direct through affect routers resulting in the dns error, as a short term fix chnge yor dns provider and hastle the one you had to fix there shizzle.