Website host moved DNS_PROBE_FINISHED_NXDOMAIN error

[#1]

I moved the host for upontheright.com last Saturday.  If I try to view the site I just get the error DNS_PROBE_FINISHED_NXDOMAIN.

If I use a non plusnet internet connection then I can see the site.

I have flushed the dns, rebooted the router (BT Smart Hub 2) and even left it off overnight. Host says that they can see no errors.Any idea on how to resolve?

[#2]

Moderators Note

This topic has been moved from Broadband to Everything Else

[#3]

I am seeing different answers depending what DNS server I ask!

For the normal PlusNet DNS servers (212.159.13.49, 212.159.13.50, 212.159.6.10, 212.159.6.9) or some public DNS server (eg 8.8.8.8, 1.1.1.1, 9.9.9.9) that hostname does not resolve (so NXDOMAIN error is correct).

>nslookup upontheright.com. 8.8.8.8
Server: dns.google
Address: 8.8.8.8

*** dns.google can't find upontheright.com.: Server failed

or

>nslookup upontheright.com. 212.159.13.49
Server: cdns01.plus.net
Address: 212.159.13.49

*** cdns01.plus.net can't find upontheright.com.: Server failed

Yet if I ask the PlusNet safeguard DNS servers (213.120.234.42, 213.120.234.38) they do reply. Do you have "safeguard" turned on in your account settings?

>nslookup upontheright.com. 213.120.234.42
Server: indnsc92.ukcore.bt.net
Address: 213.120.234.42

Non-authoritative answer:
Name: upontheright.com
Address: 91.238.163.176

and another public DNS server also answers

>nslookup upontheright.com. 4.2.2.2
Server: b.resolvers.Level3.net
Address: 4.2.2.2

Non-authoritative answer:
Name: upontheright.com
Address: 91.238.163.176

Have you made changes to the DNS records since Saturday, they might not have propogated yet?

[#4]

No changes made since Saturday.

Safeguard is off.

Just ran the same nslookups and they return the same values.

[#5 · Accepted solution]

As 2 different public DNS servers give different answers, I can't see it being a particular ISP issue (although the difference between Plusnet normal DNS vs safeguard DNS is strange). Perhaps ask your DNS host, showing them the difference between answers from 4.2.2.2 and 8.8.8.8 for example.

Or make a change to the DNS settings, wait, then change it back to see if it propagates correctly this time?

[#6]

Thanks. I've passed it back to the DNS host who are investigating and taking a proactive interest so hopefully will find the issue and resolve.  I'll post back when i know.

[#7]

It turns out there was an issue with the DNSSEC.  Once they identified and sorted that all is now well.

Thanks for the suggestions.