Is the initial DNS zone created during a DirectAdmin setup needed?

kristian

Verified User
Joined
Nov 4, 2005
Messages
100
Location
Norway
Hi,

I'm working on fully automating (with ansible) the setup of DirectAdmin on Debian 9, and at some point during the setup, a zone entry will be created in /etc/bind/named.conf with the hostname of the server, e.g. "server01.somedomain.com". This domain is not present in /etc/virtual/domainowners, and considering it is a subdomain, and the NS for it probably exists somewhere else, my questions are:

Why is this zone created? Can it be removed entirely, or will something fail to work? The hostname of the server already exists in DNS, and the server does not use itself as a resolver.

From what I can tell, Bind will never serve requests for this zone, because nothing will ask it. I have two slave DNS servers that are my public ones, so I'm syncing all zones on server01.somedomain.com to them, but it also doesn't look like I should sync this particular zone, even if I should leave it on the server itself.

Code:
# grep ^zone /etc/bind/named.conf
zone "server01.somedomain.com" { type master; file "/etc/bind/server01.somedomain.com.db"; };
Any insights appreciated.
 

zEitEr

Super Moderator
Joined
Apr 11, 2005
Messages
13,818
Location
GMT +7.00
Hello,

Directadmin checks named.conf for a domain existence. At least it protects against adding the hostname by an user.
 

kristian

Verified User
Joined
Nov 4, 2005
Messages
100
Location
Norway
If that check is all it's really used for, I would think a better check would be against the server's actual hostname, not the name in an otherwise unnecessary DNS zone?
 

zEitEr

Super Moderator
Joined
Apr 11, 2005
Messages
13,818
Location
GMT +7.00
There is a direct usage of the zone file, you know it...

If you don't need it on your server feel free to remove it, you are the boss on your server.

If you have a feature request please open a ticket with Directadmin support.
 
Top