Hi @Steve_M . Apologies for the direct approach, you seem to be the main guy who has resolved similar issues for customers. Before I get stuck into a loosing battle of trying to find the right contact at BT to talk to about this, thought I'd post here.
At ~ 6:00 Am this morning 15/02/2025, our site scopay.com is not being resolved by nameserver 81.139.56.100 and 81.139.57.100:
nslookup scopay.com 81.139.57.100Server: UnKnownAddress: 81.139.57.100*** UnKnown can't find scopay.com: Server failed
Can resolve fine against other name servers:
nslookup scopay.com 8.8.8.8Server: dns.googleAddress: 8.8.8.8Non-authoritative answer:Name: scopay.comAddress: 193.200.80.94
And for completeness, I can resolve other domains against the BT nameserver
nslookup google.com 81.139.56.100Server: UnKnownAddress: 81.139.56.100Non-authoritative answer:Name: google.comAddresses: 2a00:1450:4009:822::200e172.217.16.238
We haven't made any changes to the DNS zone in may months, but did see you helping many others on here who's site had ended up on some sort of BT DNS blacklist. If you are around and could check this, it would be most appreciated
Edit: "nslookup google.com 81.139.56.100", same results (works) for 81.139.57.100
I have just seen reports of BT email not working. Same behavior that as I'm seeing for out site.
nslookup email.bt.com 81.139.56.100
Server: UnKnown
Address: 81.139.56.100
*** UnKnown can't find email.bt.com: Server failed
And for google public:
nslookup email.bt.com 8.8.8.8
Server: dns.google
Address: 8.8.8.8
Non-authoritative answer:
Name: webmail.bt.prod.cloud.openwave.ai
Address: 65.20.50.199
Aliases: email.bt.com
So where the status page reads:
"We're aware of login issues with BT Mail and you may not be able to login until this is resolved. We’re working to get them sorted as soon as possible."
It should read "We're aware of login issues with BT Mail and other sites and you may not be able to login until this is resolved. We’re working to get them sorted as soon as possible." 😄
Also experiencing issues getting to at least one site boardgamegeek.com - fault reporting with BT obviously doesnt cater for this level of granularity when looking to report an issue - going to assume for now this is related to the same root fault as the BT email issue.....guess logging into the router and changing the default DNS server would be the way to go if BT allowed that - guess its down to device level then.....
There are a couple of sites that check DNS resolution across multiple locations - you'll need to look it up as last time I posted I was told off for including links to third-party sites. What I would say is that two of the three web addresses I own were not propagating properly yesterday - about 50% of the DNS servers had either the wrong or no IP-Address associated.
*In my case though, the BT DNS servers were not the ones on the naughty step!
I see - boardgamegeek.com DNS provider is godaddy. Same as ours and all of the other sites (6 now), that are not BT email, that are affected in the same way.
We only use godaddy for DNS, so I'm just talking to them to see if they have any contacts at BT, or if they know whats going on, or can recommend any nameserver changes that may resolve this. After plugging through the AI bot and a convo with a human, I'm at this stage:
"I got you! Let me check with our advanced technical team to explore all possible solutions we can offer from our end."
I'll let you know if they come back with anything useful (assuming you host boardgamegeek, if they come back with anything useful, I'll let you know
@Crimliar Thanks for the info... Propagation checks looked fine for ours this morning, nor have we haven't made any adjustments to our zone in months
I'm told that the difficulty of accessing email is due to a WiFi issue at BT. I'm also told you can access email on a mobile phone by turning off WiFi on your mobile and then accessing BT email
Looks like boardgamegeek.com is working now.
Hopefully the issue is resolved for OP too.
Cheers
Hi All,
We’re working on this with GoDaddy who have had DNS server issues this morning.
Steve
Seems to have been stable since 13:05 when GoDaddy refreshed their DNS propagation.
Steve