Anyone else seeing DNS issues?

So far I'm struggling to connect to forums.digitalspy.com - it comes and goes and sometimes returns a different host name.

theregister.com also seems to have gone.

I've rebooted my router and spoken with IDNet support (so nice to be able to get straight through to a technical person at 9pm). He could see issues on one line as well.

Definitely seems to be DNS as it mostly impacts domains with a short TTL or sites I've never visited before (trying to access sites in Google search results).

Edited by Andrue (Thu 05-Apr-18 21:24:55)

In reply to a post by Andrue:

So far I'm struggling to connect to forums.digitalspy.com - it comes and goes and sometimes returns a different host name.

theregister.com also seems to have gone.

I've rebooted my router and spoken with IDNet support (so nice to be able to get straight through to a technical person at 9pm). He could see issues on one line as well.

Definitely seems to be DNS as it mostly impacts domains with a short TTL or sites I've never visited before (trying to access sites in Google search results).

No issues here. I'm using Cloudflares DNS resolver

https://blog.cloudflare.com/dns-resolver-1-1-1-1/

All seems OK here on BT Retail offering. Never visited The Register before, straight in.

Seems fine to me on BT using Googles, BT's and our own DNS's but maybe its fixed due to its an hour after your post.

Paul

Both sites resolving OK for me on IDNet using IDNet's DNS servers.

Cloudflare had issues around the time you posted. If the sites are using their DNS then that may explain why.

Ok using Google DNS (8.8.8.8 / 8.8.4.4).

Have you tried using these in a single PC rather than using your router to resolve DNS via IDNet DNS? (Anyone know if IDNet hijack DNS lookups and redirect them to their own servers?)

Anthony

Seems ok using IBM Quad DNS in router.

Thanks for your replies, folks. It seems to have affected a handful of people but I don't know what ISP they are with. I got around it for half an hour or so by using Google DNS but after switching back all seemed good again. So whatever the problem it seems it was fixed sometime after 10pm. Just had a call from IDNet support checking up so I've closed the ticket.

Some kind of glitch :-/