Issue with just one domain not resolving NS correctly

Maintenance
1

I have been running my MiaB for a few months now without any issue. Have setup a secondary DNS with puck.nether.net and everything has been great.

Now I get an error on one domain (I have seven hosted currently on my box) that is now having issues finding the nameservers I have set on the domain with the host. The error I get in the system page is the following

The nameservers set on this domain are incorrect. They are currently [Not Set]. Use your domain name registrar’s control panel to set the nameservers to ns1.box.domain.tld; puck.nether.net.

Nothing changed with my host so not sure what to tell them to show them that the issue is on their end. I even did a DNS test and found that certain geographies are having issues getting NS records for the domain.

Screenshot 2024-06-25 144919
Screenshot 2024-06-25 1449191203×768 99 KB

I have all of the other domains hosted with the same provider but in a separate account and all of them are working fine.

Any thoughts on what to try next?

2

I use buddydns https://www.buddyns.com/

Make a free acount and a zone and just paste these in MIAB Secondary Name server:

uz5x6wcwzfbjs8fkmkuchydn9339lf7xbxdmnp038cmyjlgg9sprr2.free.ns.buddyns.com uz56xw8h7fw656bpfv84pctjbl9rbzbqrw4rpzdhtvzyltpjdmx0zq.free.ns.buddyns.com uz588h0rhwuu3cc03gm9uckw0w42cqr459wn1nxrbzhym2wd81zydb.free.ns.buddyns.com uz5154v9zl2nswf05td8yzgtd0jl6mvvjp98ut07ln0ydp2bqh1skn.free.ns.buddyns.com uz5dkwpjfvfwb9rh1qj93mtup0gw65s6j7vqqumch0r9gzlu8qxx39.free.ns.buddyns.com uz5w6sb91zt99b73bznfkvtd0j1snxby06gg4hr0p8uum27n0hf6cd.free.ns.buddyns.com uz52u1wtmumlrx5fwu6nmv22ntcddxcjjw41z8sfd6ur9n7797lrv9.free.ns.buddyns.com

Paste them at your registrar, as well, by making NS entries there too!
They will propagate all the way to Mars :slight_smile:

3

I will try this, but I think the issue is that when requests are being sent to my domain host to get the nameservers, that is failing at that point and not due to my box or nether.net DNS settings being the issue.

Is there any way I can test that?

4

Just to be sure: this was working before? puck.nether.net has your domain registered and your domain registrar has both nameservers registered?
What sometimes gets in the way is dnssec. If you have it enabled, disable it for the domain, then wait for everything to work, and then you can re-enable it.

5

The domain is registered at GoDaddy (yeah, I know) and puck.nether.net is setup as the backup DNS.

It was all working fine and suddenly stopped without any changes on my end besides updating the packages on the box periodically to keep the OS and everything up to date.

It does have DNSSec setup so I will try disabling that and see if that fixes things. Could that just start failing all of a sudden without changes on my end?

6

Well, not suddenly, but in my experience it sometimes just fails even if you only changed something that didn’t seem related.

Maybe a site like Zonemaster.se or https://dnsviz.net/ might provide a hint…

1 Like
7

DNSSEC is evil, so yeah. Most likely it has been broken for a while, but DNSSEC issues do not always manifest themselves immediately.

1 Like
8

Always disable DNSSEC at the registrat before making changes there. Wait to see if all is OK and reanable.

1 Like
9

You all are awesome. Turned off DS and my MiaB status went back to all green. So now I can turn it back on? Why would DS mess with this? So dumb.

10

As an update, it looks like my host has issues with DNSSec and that may be the issue. I cannot add back the record to my domain so I wonder if they have an issue that caused the issue.

I’ll call them tomorrow to report the issue and see what they say. I’ll post the response here for future.

11

This topic was automatically closed 40 days after the last reply. New replies are no longer allowed.