Possible Routing Issue
When using BT/PN DNS, I have no access to my domain site/email because there is no valid dns data available. Everything was OK yesterday evening but all look-ups have failed to provide any sensible response since circa 0500 hours today.
The authoritative nameservers do not appear to be contactable and any cached data has obviously long since expired.
Pinging ns25.domaincontrol.com [97.74.102.13] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 97.74.102.13:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Tracing route to ns25.domaincontrol.com [97.74.102.13]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms redacted [192.168.1.1]
2 8 ms 8 ms 11 ms 254.core.plus.net [195.166.130.254]
3 9 ms 10 ms 9 ms 213.120.163.4
4 9 ms 9 ms 10 ms 217.32.240.93
5 9 ms 9 ms 10 ms 213.121.192.132
6 9 ms 10 ms 10 ms peer7-et-4-1-5.telehouse.ukcore.bt.net [194.72.16.142]
7 9 ms 9 ms 9 ms 166-49-214-194.gia.bt.net [166.49.214.194]
8 10 ms 9 ms 10 ms ldn-b3-link.ip.twelve99.net [213.248.71.146]
9 10 ms * * ldn-bb2-link.ip.twelve99.net [62.115.140.70]
10 15 ms 14 ms 15 ms adm-bb2-link.ip.twelve99.net [62.115.137.235]
11 14 ms 18 ms 14 ms adm-b10-link.ip.twelve99.net [62.115.138.251]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
However, everything is mostly OK (at the mo, anyway) when using cloudflare/google/open-dns for dns lookups. Also, someone on another forum can apparently ping/tracert both of my authoritative nameservers via a BT wholesale connection.
Anyone have any thoughts ? I can't get any response let alone any sense from 123-reg 
Thank you for posting that 
Hmmmmmm, so do I now The very first time I've seen anything other than a blackhole since 0500 hours this morning !
Pinging ns25.domaincontrol.com [97.74.102.13] with 32 bytes of data:
Reply from 97.74.102.13: bytes=32 time=16ms TTL=51
Reply from 97.74.102.13: bytes=32 time=16ms TTL=51
Reply from 97.74.102.13: bytes=32 time=16ms TTL=51
Reply from 97.74.102.13: bytes=32 time=16ms TTL=51
Ping statistics for 97.74.102.13:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 16ms, Average = 16ms
Tracing route to ns25.domaincontrol.com [97.74.102.13]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms redacted [192.168.1.1]
2 8 ms 8 ms 8 ms 254.core.plus.net [195.166.130.254]
3 9 ms 9 ms 9 ms 213.120.163.4
4 9 ms 9 ms 9 ms 217.32.240.93
5 9 ms 10 ms 9 ms 213.121.192.132
6 16 ms 9 ms 10 ms peer7-et-4-1-5.telehouse.ukcore.bt.net [194.72.16.142]
7 10 ms 11 ms 9 ms 166-49-214-194.gia.bt.net [166.49.214.194]
8 9 ms 10 ms 9 ms ldn-b3-link.ip.twelve99.net [213.248.71.146]
9 * 9 ms * ldn-bb2-link.ip.twelve99.net [62.115.140.70]
10 15 ms * * adm-bb2-link.ip.twelve99.net [62.115.137.235]
11 15 ms 14 ms 15 ms adm-b10-link.ip.twelve99.net [62.115.138.251]
12 16 ms 16 ms 17 ms ae0-u613.ams3-cr-oberon.bb.gdinf.net [62.115.156.203]
13 17 ms 17 ms 17 ms 243.149.109.208.host.secureserver.net [208.109.149.243]
14 16 ms 16 ms 20 ms ns25.domaincontrol.com [97.74.102.13]
Trace complete.
After almost 2 hours of 123-reg apparently ignoring a chat session which had an alleged 3-minute wait, they simply say it is/was a BT problem and nothing whatsoever to do with them.
@Dan_the_Van wrote:
Have you seen this BBC news story?
https://www.bbc.co.uk/news/articles/c8xq0gey2pno
Reports started spiking from 05:00 GMT on Saturday according to outage-tracking site Downdetector, which received a peak of more than 5,000 complaints from customers.
Yup, after the 2-hour wait to respond to the chat session, 123-reg were clearly absolutely delighted to give me that link and just say it's a BT problem and nothing whatsoever to do with them !
It may or may not be. My money would be on maybe related but not the cause of my problem(s) this week. I've only seen issues various with anything if not everything related to 123-reg. No such issues have been noticed with any other website, company or service provider whatsoever. Just 123-reg. Especially today with the apparent loss of connectivity some 12 hops down the line to a 123-reg service !
@Townman wrote:
I wonder if 123-reg have name server issues?
I just needed to lookup kitz.co.uk and could not route to it. Digging I found that Google can resolve the address.
Researching the domain identified that its name servers are
ns63.domaincontrol.com ns64.domaincontrol.com
Neither of which were resolvable by Plusnet's DNS servers. Having drafted a rather long diagnostic post for the SU escalation space, I rechecked details ... and found that it was all working as expected.
This problem sounds similar ... with the same domain hosting company.
It might be worth poking this again. Use nslookup to query your domain and the relevant name servers.
It's exactly the same problem. Now mysteriously fixed as if by magic. 123-reg are blaming BT/PN and denying any responsibility whatsoever.
It's clearly an issue with twelve99 or 123-reg and/or their data centre providers etc.Everything ground to a halt some 12 hops down the line to a paid-for 123-reg service. There has also been ongoing issues all week with various fortunately short duration connectivity issues to 123-reg services and ONLY 123-reg services, not connectivity issues in general.
123-reg are currently forcing TSOhost customers onto their system(s) so my money would be on it being down to network or data centre changes related to that mass migration. No shortage of very unhappy TSOhost customers apparently ... and I very much feel their pain having been on the receiving end of much the same screwing over by 123-reg 
Clearly it wasn't just me and Kitz. Realtime confirmation of 123-reg service outage available HERE with an archived copy of the chart which should appear above also available HERE just in case it doesn't !
Most if not all domain-related services affected - hosted site, ftp, email etc - due to being unable to connect to the authoritative nameservers when cached data expired. Cloudflare/google/open-dns were presumably using different routing or maintaining previously cached data for far longer than expected.