DNS for second domain no longer functioning

[mockingbird]

On my server I have two domains setup on Directadmin. I have DNS set up with two NS records for each domain using the default DA hosted DNS thusly:

ns1.server-x-x-x-1.da.direct.
ns2.server-x-x-x-1.da.direct.

And for the second server:

ns1.server-x-x-x-2.da.direct.
ns2.server-x-x-x-2.da.direct.

(where "x" is the IP address).

Now this has been working fine, and the first server still resolves. But as of this morning, the DNS for the second server no longer works.

Am I not supposed to use your DNS servers (i.e. are they only meant to be used initially for setup?)

Thanks

 

[Richard G]

Am I not supposed to use your DNS servers (i.e. are they only meant to be used initially for setup?)

Not if you also point to them at your registrar, in that case you should run your own nameservers.

If you use your domain registrars DNS (most likely), then it doesn't matter that this ns2 does not resolve anymore as this is only used locally on the DA server/vps you're using of internal lookups.

So as long as your A records (for example) for your domain.com point to the ip of your vps/server it doesn't matter if ns2 is working or not.

If you have multiple ip's and want to use your own nameserver, then it's a complete other story.
Anyway, if you want to send mail from that system I would advise to change the hostname anyway if that is still a da.direct hostname.

 

[mockingbird]

Would you please elaborate on your answer?

Perhaps I should clarify as well:
On my registrar, the domain is pointing to ns1.server-x-x-x-2.da.direct. (and ns2...). I am not using my registrar's DNS.

I have two IPs on my server, this was working fine for both domains until this morning. Now only the first one works but the second one doesn't. I am wondering if this is because of some limitation on what DA allows (because I am essentially using DA for my DNS hosting).

It's not a big deal, I already moved the second domain to a different DNS host, but I would still like to know.

 

[Richard G]

On my registrar, the domain is pointing to ns1.server-x-x-x-2.da.direct. (and ns2...). I am not using my registrar's DNS.

Yes that's not good because those are not your nameservers and also not your registrars nameservers so then things can go wrong. Those are created for easy setup for users which are using the registrars nameservers and don't want to run their own.
So they are also only used locally.

If you want to run your own nameservers (like you do know), then it's best to set your system up according to RFC's and so not use the da.direct nameservers.

First hostname https://forum.directadmin.com/threa...e-your-servers-hostname-in-directadmin.70371/
and you can use something like ns1.domain.com and ns2.domain.com for nameservers if you want to use your own.
Then you need both A and NS record in domain.com for ns1 and ns2 to work correctly.