cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Contributor
670 Views
Message 11 of 35

Re: Problem reaching Google?

Go to solution

Is there a way we can make someone who has the power to do something about this notice?

 

It's a fairly serious network issue.

 

I don't relish the 20 minutes wait for first line support to tell me to reboot my router ...

0 Ratings
Highlighted
Newbie
660 Views
Message 12 of 35

Re: Problem reaching Google?

Go to solution
I have this issue as well in Coventry. Google apps not updating, music and YouTube not working, chromecast not working. I'm using factory defaults for DNS etc
0 Ratings
Highlighted
Contributor
656 Views
Message 13 of 35

Re: Problem reaching Google?

Go to solution

I just switched back from OpenDNS to BT DNS and everything works fine, but this is not a solution.

 

I need to be able to choose my own DNS, I make use of OpenDNS' additional services.

 

There are devices (Chromecase, Samsung TVs, as an example) that hard-code DNS.

 

We should, and must, be able to route to public Google IPs in order for BT to claim they are providing a service. I've no idea why they think hiijacking Google DNS is a sensible thing to do, and I view it with nothing but suspicion.

 

0 Ratings
Highlighted
Beginner
649 Views
Message 14 of 35

Re: Problem reaching Google?

Go to solution

I was on BTDNS and nothing works. Switched to Google and still the same. Switched back and nothing has changed. I'm currently on hold waiting to talk to a manager. I refused point blank to talk to the opening technician as they go through a script, all of which I went through with someone last night only to be told the fault wasn't with them.

0 Ratings
Highlighted
Contributor
645 Views
Message 15 of 35

Re: Problem reaching Google?

Go to solution

What's google.com resolving to for you?

 

This is very not right:

 

>nslookup google.com 8.8.8.8
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
Name:    google.com
Addresses:  2a00:1450:4009:80c::1000
          31.55.184.121
          31.55.184.122
          31.55.184.118
          31.55.184.117
          31.55.184.120
          31.55.184.116
          31.55.184.123
          31.55.184.119 <--- all BT IPs

 From outside BT's network:

 

[~]# nslookup google.com 8.8.8.8
Server:         8.8.8.8
Address:        8.8.8.8#53

Non-authoritative answer:
Name:   google.com
Address: 173.194.113.78
Name:   google.com
Address: 173.194.113.73
Name:   google.com
Address: 173.194.113.65
Name:   google.com
Address: 173.194.113.71
Name:   google.com
Address: 173.194.113.66
Name:   google.com
Address: 173.194.113.64
Name:   google.com
Address: 173.194.113.67
Name:   google.com
Address: 173.194.113.72
Name:   google.com
Address: 173.194.113.70
Name:   google.com
Address: 173.194.113.68
Name:   google.com
Address: 173.194.113.69

 

0 Ratings
Highlighted
Newbie
631 Views
Message 16 of 35

Re: Problem reaching Google?

Go to solution
I've been in contact with BT, they are saying nobody else has this problem.... suggest you log it with them... if enough of us do it they will investigate. Ridiculous I know...
0 Ratings
Highlighted
Contributor
626 Views
Message 17 of 35

Re: Problem reaching Google?

Go to solution

I reported it via their Twitter 'contact me' page late last night if that does any good.

 

0 Ratings
Highlighted
Moderator
Moderator
618 Views
Message 18 of 35

Re: Problem reaching Google?

Go to solution

Hi Everyone,

 

I'm sorry to see you're having issues reaching Google. I've raised this for further investigation and we'll post back here when we have any updates.

 

Thanks

 

Neil

0 Ratings
Highlighted
Newbie
610 Views
Message 19 of 35

Re: Problem reaching Google?

Go to solution

I'm having the same problem. When I use OpenDNS I can't access any Google sites.

By switching back to BT DNS servers everything works, but I want to use OpenDNS because of the additional functionality.

Actually, not everything works because apparently my Chromecast has hardcoded DNS servers, so now it just says it can't access the internet.

 

Additional information. DNS request from outside BT (Amazon VM) using a Google DNS server:

 

root@ip-10-233-129-60:~# nslookup google.co.uk 8.8.8.8
Server:		8.8.8.8
Address:	8.8.8.8#53

Non-authoritative answer:
Name:	google.co.uk
Address: 74.125.28.94

 From inside BT using the same Google DNS server:

 

root@jan-ThinkPad-W530:/home/jan/4525docs# nslookup google.co.uk 8.8.8.8
Server:		8.8.8.8
Address:	8.8.8.8#53

Non-authoritative answer:
Name:	google.co.uk
Address: 31.55.184.119
Name:	google.co.uk
Address: 31.55.184.121
Name:	google.co.uk
Address: 31.55.184.118
Name:	google.co.uk
Address: 31.55.184.120
Name:	google.co.uk
Address: 31.55.184.122
Name:	google.co.uk
Address: 31.55.184.116
Name:	google.co.uk
Address: 31.55.184.123
Name:	google.co.uk
Address: 31.55.184.117

 From inside BT using a BT DNS server:

 

root@jan-ThinkPad-W530:/home/jan/4525docs# nslookup google.co.uk 62.6.40.178
Server:		62.6.40.178
Address:	62.6.40.178#53

Non-authoritative answer:
Name:	google.co.uk
Address: 74.125.230.159
Name:	google.co.uk
Address: 74.125.230.151
Name:	google.co.uk
Address: 74.125.230.152

Clearly, BT is hijacking DNS requests to non-BT DNS servers and replying with IP addresses in some BT range for any Google site.

0 Ratings
Highlighted
609 Views
Message 20 of 35

Re: Problem reaching Google?

Go to solution

I'm also having this issue, symptoms are thus:

*** Google DNS:

No access to Google services yesterday.
Having just tested it now, I get sporadic but extremely slow access to Google, traceroute as follows:

Edit: The sporadic access may have been a fluke, unable to access Google having tested again via 3rd party DNS.

 

Tracing route to google.com [31.55.184.122]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  BTHUB3 [172.16.0.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    19 ms    18 ms    19 ms  31.55.187.216
  5     *        *        *     Request timed out.
  6    20 ms    21 ms    21 ms  31.55.184.32
  7    21 ms    20 ms    20 ms  31.55.184.33
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 ----- All results between 11-27 also timed out, shortened for easy reading.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

 
Note: BT's DNS resolves google.com to 74.125.230.100, which is a Google IP.
Attempting to use OpenDNS/Google DNS results in various BT IP addresses within the 31.55.184.* range.


*** OpenDNS:

Behaviour identical to Google DNS.


*** BT DNS:

Immediate and reliable access to Google returns, but roughly half of all YouTube videos simply will not play, infinite loading circle until eventual failure.
Videos verified as working via a mobile connection, both on a phone and on a tethered laptop.

Specifically videos hosted at r4---sn-cu-ajtd.googlevideo.com being problematic, which under BT's DNS resolves to 31.55.184.111, which is a BT address.

Traceroute to this address gives me:

 

Tracing route to r4.sn-cu-ajtd.googlevideo.com [31.55.184.111]
over a maximum of 30 hops:

  1    <1 ms     1 ms     1 ms  BTHUB3 [172.16.0.254]
  2     *        *        *     Request timed out.
  3     *        *       17 ms  31.55.187.193
  4    19 ms    19 ms    19 ms  31.55.187.224
  5     *        *        *     Request timed out.
  6     *       24 ms    24 ms  31.55.184.34
  7    23 ms    22 ms    23 ms  31.55.184.35
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 ----- All results between 11-27 also timed out, shortened for easy reading.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.


Previously in the month or two prior to this, I've also had BT blocking me from using alternate DNS providers outright, always leading me to a page with wording to the effect of "you're using an external DNS, so no internets for you", which seemingly resolved itself a few days after. Around the same time, having been forced back to the BT DNS in order to browse, I clicked a link to a news article and had a BT iframe embedded in it asking me whether I'd like to use parental controls, which had come from "http://nom-proxy."

I am incredibly unhappy that BT appear to be manipulating my data in such a way, particularly without any obvious warning. Not only is it concerning from a privacy standpoint, it could also mislead those who cannot tell whether there's any malware involved.

Even if I put aside my concerns around data manipulation/interception, whatever systems are in place to do this are clearly broken, so not only is my connection adulterated, it's flat out not working as it should. This is the third issue I'm now attributing to BT's filtering/parental control systems in perhaps a month and a half and to say I'm mildly annnoyed would be an understatement.

0 Ratings