There does seem to be an ongoing and unacknowledged problem with BT's DNS servers. I've had similar issues to those the the OP describes (though mine were not connected to email).
Changing the DNS address to 8.8.8.8 (on all my devices, since you can't change it on BT's hub) solves the problems.
There are even problems getting to Microsoft's sites using BT's network - some obscure routing problem and no way of telling anyone there so they can investigate it (one is met with disbelief and intellectual "snobbery").
BT's DNS servers don't respond to pings (or trace route attempts) by design and that is quite a sensible solution for them even though it makes diagnosis harder for its customers.
I'm going to leave all my devices set to 8.8.8.8 now because despite being (or once was) the UK's premier telecom provider they appear to no longer be focussed on giving an excellent customer experience and, I assume, now pursue other goals.
@wuxmediawrote:one way to do it discretely would be logging DNS lookups.
Ideally DNS would work though to do that lol.
Tin foil hat on : It does track though, as I've only seen it have this issue recently.
Looks like I'll be checking some guides out about breaking ties with the hub
Just use a Raspberry Pi and PiHole for both DHCP and DNS.
This is one of the many reasons I've continued to use my Draytek as the gateway to my network after the switch to Digital Voice. My network gets its DNS settings from the Draytek not the SH2.
Just use a Raspberry Pi and PiHole for both DHCP and DNS.
That would form part of the plan, but we come to the impasse that is the hub cannot change the DNS. Many years ago I did but the pi failed and a new hub was given to us.
I'll look for guides that serve my needs, and hopefully others, thanks all