Namserver named.conf not set to slave on slave server

A

Alexvg82

New member
Joined
Jan 18, 2022
Messages
2
Hi,

I have setup an multiserver setup on DirectAdmin.
Everything is working and updating between the master and slave, only when I look at the slave named.conf all zones are added with type master instead of the type slave that we are seeing on other servers that we own.

I have checked every file but can't seem to find where this is set.

Any ideeas?

We need this to be like below:
Master server named.conf
zone "domain.com" { type master; file "/var/named/domain.com.db"; };

Slave server named.conf
zone "domain.com" { type slave; file "/var/named/domain.com.db"; masters { IP address of master ; }; };

But at the moment the zone files on master and on slave are identical.
zone "domain.com" { type master; file "/var/named/domain.com.db"; };
 
Last edited:
Don't worry about it. That's working as designed.

When using the multiserver setup, the records are created and exchanged via DA and not via the official master-slave setup of named. Directadmin will keep the records up to date and not named itself, so that is the reason.
So this will result in all records in the named.conf files to be type master and not slave, that is normal.

When you look in the DNS Administration in Directadmin, you will see the difference. There is a local data and local mail column. For the domains on the master server, you will see no and no on the slave server, vice versa.

So it's working as it should be.
 
You must log in or register to reply here.
Back
Top