Re: DNS Issues

gpetelov · ‎03-06-2024

Currently experiencing an issue when attempting to reach any site on the brew.sh domain. Looks like a BT DNS problem as everything works when going through my mobile data which is on 3. Can anyone from BT please investigate?

Keith_Beddoe · ‎03-06-2024

This is just a customer to customer help forum, everyone here, including myself, are just customers.

The only BT Employees are the forum moderators, who may offer to help.

Try calling 0330 1234 150

You can message BT using the "message us" links on the help pages. That is usually effective.

https://www.bt.com/help/contact-bt

AJDB · ‎03-06-2024

I am experiencing the exact same issue, but I don't believe it's DNS related. I use Google DNS (8.8.8.8 and 8.8.4.4) but I've also tried Cloudflare and both resolve to the same IP's. I've tested connectivity over a non-BT network and it works just fine.

My NSLookup:

nslookup brew.sh

Server: 8.8.8.8

Address: 8.8.8.8#53

Non-authoritative answer:

Name: brew.sh

Address: 185.199.108.153

Name: brew.sh

Address: 185.199.109.153

Name: brew.sh

Address: 185.199.110.153

Name: brew.sh

Address: 185.199.111.153

Dig:

dig brew.sh

; <<>> DiG 9.10.6 <<>> brew.sh

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52454

;; flags: qr rd ra ad; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 512

;; QUESTION SECTION:

;brew.sh. IN A

;; ANSWER SECTION:

brew.sh. 4 IN A 185.199.108.153

brew.sh. 4 IN A 185.199.109.153

brew.sh. 4 IN A 185.199.110.153

brew.sh. 4 IN A 185.199.111.153

;; Query time: 16 msec

;; SERVER: 8.8.8.8#53(8.8.8.8)

;; WHEN: Mon Jun 03 15:24:11 BST 2024

;; MSG SIZE rcvd: 100

and my Traceroute:

traceroute: Warning: brew.sh has multiple addresses; using 185.199.108.153

traceroute to brew.sh (185.199.108.153), 64 hops max, 52 byte packets

1 10.10.12.1 (10.10.12.1) 1.832 ms 3.036 ms 1.647 ms

2 host81-148-32-1.in-addr.btopenworld.com (81.148.32.1) 9.980 ms 8.028 ms 7.999 ms

3 217.32.25.114 (217.32.25.114) 8.619 ms 8.764 ms 8.479 ms

4 host213-123-18-51.in-addr.btopenworld.com (213.123.18.51) 8.540 ms 8.595 ms 8.371 ms

5 * * *

6 * * *

7 * * *

8 * * *

I'm a BT Business user and I called BT to report this, but spoke to someone in first line who didn't understand what routing was, and just continually referred to the face that I'm using a non-BT router and that must be the issue (I use Ubiquiti Edgemax for various reasons). I asked to be escalated to second line but this would apparently incur a charge of £25 regardless of if this is their fault of mine, something I'm not willing to pay when I spend over £90/month on connectivity.

Basically, I seem to have hit a wall and given that support don't understand the issue I'm not sure how best to proceed.

bobpullen · ‎03-06-2024

I don't think it's DNS.

I'm running my own DNS resolver and I'm unable to access the site either. I suspect a wider issue affecting connectivity between the BT network and sites hosted on Github.

See similar reports of issues over on the Plusnet and EE forums.

~$ dig brew.sh

; <<>> DiG 9.18.24-1-Debian <<>> brew.sh
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7271
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;brew.sh.                       IN      A

;; ANSWER SECTION:
brew.sh.                3600    IN      A       185.199.108.153
brew.sh.                3600    IN      A       185.199.111.153
brew.sh.                3600    IN      A       185.199.110.153
brew.sh.                3600    IN      A       185.199.109.153

~$ whois 185.199.108.153
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See https://apps.db.ripe.net/docs/HTML-Terms-And-Conditions

% Note: this output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to '185.199.108.0 - 185.199.111.255'

% Abuse contact for '185.199.108.0 - 185.199.111.255' is 'abuse@github.com'

inetnum:        185.199.108.0 - 185.199.111.255
netname:        US-GITHUB-20170413

madness800 · ‎03-06-2024

I'm strongly to believe there is a BGP routing issue inside BT network. github.io is untrace routable and also ping request just refuse to respond on my home network (on BT).

I've tried visiting the site via my work VPN which is not BT network that site is reachable.

gpetelov · ‎03-06-2024

Thanks @Keith_Beddoe . I've seen able to find solutions on these forums before and was hoping get some traction and maybe the mods can escalate to the appropriate internal support. I also wasn't mentally prepared to fight my way through the levels of customer support until the issue got escalated properly.

I'll try the chat and check in tomorrow with updates.

Cheers

Keith_Beddoe · ‎03-06-2024

@gpetelov

Unfortunately the moderators are a very small team and are very busy sorting out many customer issues, and do not have the resources to investigate routing issues.

AJDB · ‎03-06-2024

I posted here earlier, but it would seem my post was removed, ho-hum.

I have been experiencing the same issue today. DNS resolves fine but the routing fails at BT:

traceroute: Warning: brew.sh has multiple addresses; using 185.199.108.153
traceroute to brew.sh (185.199.108.153), 64 hops max, 52 byte packets
110.10.12.1 (10.10.12.1)1.845 ms1.424 ms1.498 ms
2host81-139-176-1.in-addr.btopenworld.com (81.139.176.1)9.205 ms7.918 ms7.749 ms
3217.32.25.98 (217.32.25.98)8.030 ms8.382 ms8.044 ms
4host213-123-18-53.in-addr.btopenworld.com (213.123.18.53)8.254 ms11.902 ms8.285 ms
5* * *
6* * *
7* * *
8* * *
9* * *
10* * *
11* * *
12* * *

I've raised this with numerous support departments with limited success (please don't remove my post just because I'm being honest!), however I raised it over twitter with BT Business Care and they've asked the High Level Repair Team to investigate, so with any luck they'll hopefully be able to sort it soon. It would probably help if other people logged the issue, and it would seem that due to the complexity of the issue in this instance that the Twitter team may be able to expedite the process.

Keith_Beddoe · ‎03-06-2024

@AJDB

If you are a business user, you are posting on the wrong forum. Try,

http://business.forums.bt.com/

ch · ‎04-06-2024

Same here

github.io inaccessible through my BT connection (with my own DNS), but works fine via a VPN or via a TOR circuit.

How can we raise a support ticket?