Solved Named randomly not resolving

[klasje]

Hello,

In Directadmin I run my own nameservers.
However, when doing lookups, randomly some countries do not properly resolve DNS queries to client domains.
I then have to restart named and then usually a few hours later they resolve again.
A few weeks later, I start having the same issue again and need to restart named again.

Any clue what could be the cause of this random issue, forcing me to restart named?

Eg: https://dnschecker.org/#A/thunderwrites.com if you press search you see that some countries resolve, others do not.

 

[Richard G]

Any clue what could be the cause of this random issue, forcing me to restart named?

Well... might be the configuration is not what it should be.

Did you see this?

intoDNS: thunderwrites.com - check DNS server and mail server health

intoDNS: Checking health and configurtion of DNS server and mail server for domainthunderwrites.com.

intodns.com

When I check dimoweb, they are not using their own nameservers either, it looks like they are using Versio nameservers.

If you want to run your own nameservers, you should setup your nameservers at your registrar (dus bijv. bij Versio, niet bij Dimoweb).
And ns1 and ns2.dimoweg.com are pointing to totally different ip addresses.

So to me it looks like you did not setup your nameservers correctly, which is causing the issue.

Stuur me anders evt. even een prive bericht, dan kunnen we Nederlands schrijven.

 

[klasje]

I switched the nameservers to use directadmin nameservers and most of it started working correctly.

Except for 1 major issue:
The hostname of the directadmin server (server.dimoweb.com) is not working.
Even tough an A record exists in dimoweb.com for the server. subdomain,
it only resolves on the server and not outside of it.

Things I tried:
- Created a CNAME for server.dimoweb.com => not working outside the server
- Created A / AAAA records for server.dimoweb.com => not working
- Creating a new user with hosting for server.dimoweb.com => not allowed in directadmin for the hostname
- Creating following file manually with the correct records: vi /etc/bind/server.dimoweb.com.db, restart named => not working

Any clue why the hostname server.dimoweb.com won't resolve to the outside world?

DNS Checker - DNS Check Propagation Tool

Check DNS Propagation worldwide. DNS Checker provides name server propagation check instantly. Changed nameservers so do a DNS lookup and check if DNS and nameservers have propagated.

dnschecker.org

intoDNS: server.dimoweb.com - check DNS server and mail server health

intoDNS: Checking health and configurtion of DNS server and mail server for domainserver.dimoweb.com.

intodns.com

 

[Richard G]

I just replied to your PM. Never use Cname for hostname.
Do not create a new user, but just a dns record, I explained in the pm.
Remove that user again.

With my PM things should be fixed if you do what is in there.

 

[klasje]

Solution:
the dns zone server. existed already, but couldn't be opened in the directadmin dns administration tool.
There was no .db file.
I deleted that damaged zone and added the server.domain.com zone back in the dns administration tool on admin level.
That solved the issue.

Thank you!

 

[Richard G]

You're welcome.