Resolved MAster DNS problems for 3rd DNS Server

[Edward Dekker]

Hello and a Happy and Good 2019,

I do have issues found about a 3rd DNS server that i've created into the Plesk panel for an active domain.

My DNS template from Master (ns1.example.com) will results this by SSH:

Find in Master> sudo less /var/named/chroot/var/example.com

; *** This file is automatically generated by Plesk ***
$TTL    86400
@       IN      SOA     ns3.example.com. dnsmaster.example.com. (
                        2019010603      ; Serial
                        10800   ; Refresh
                        3600    ; Retry
                        604800  ; Expire
                        10800 ) ; Minimum
example.com.                 IN NS   ns3.example.com.
example.com.                 IN NS   ns2.example.com.
example.com.                 IN NS   ns1.example.com.

Than the SOA reffer to a 3rd Slave server where i could find the master zone files. This has to be a SOA with ns1.example.com. Also the NS3.example.com are not willing to update their NS records. My conclusion are also that the serial are not correspond to a next number and out of sync by serial. And at last do i missing all of my PTR records.

So, a lot of the generated data are incorrect and not included by the master DNS.

jan 06 00:23:02 server1.example.com named[5150]: zone example.com/IN (unsigned): ixfr-from-differences: new serial (2019010603) out of range [2019010604 - 4166494250]
jan 06 00:23:02 server1.example.com named[5150]: zone example.com/IN (unsigned): not loaded due to errors.

------------------------------------------------------------------------------------------------------------------------
Product version: Plesk Onyx 17.8.11
Build date: 2018/09/20 15:00
OS version: CentOS 7.6.1810
Revision: c3fb546fb867ac424d65da14d8b023f11ec0d150
Architecture: 64-bit
Wrapper version: 1.2

 

[Edward Dekker]

Hi,

I want to announce that i solved my issue.
As for now i've more mx records at the same priority.
That creates the problem by my domain name server (DNS).
My suggestion are to announce the user when there are more than one mx record set by a specific priority into their records.
And it will be a safe thought to set a NS record with number 1 at top.