• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Slave DNS Manager does not work for subdomains?

JohnD87

New Pleskian
Hello,

i have an issue with the slave dns manager extension on one of my plesk systems.
It works great for Domains but all subdomains (or just manually added A Level entries) are completely ignored:

Example query directly on plesk server daswill.domain1.de:
Code:
dig blahblah.domain2.eu @daswill.domain1.de

; <<>> DiG 9.10.4-P1 <<>> blahblah.domain2.eu @daswill.domain1.de
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62185
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;blahblah.domain2.eu.    IN    A

;; ANSWER SECTION:
blahblah.domain2.eu. 86400    IN    A    1.2.3.4

;; AUTHORITY SECTION:
domain2.eu.        86400    IN    NS    ns.domain2.eu.

;; ADDITIONAL SECTION:
Same for ns3.domain1.de (Slave DNS Server)
Code:
dig blahblah.domain2.eu @ns3.domain1.de

; <<>> DiG 9.10.4-P1 <<>> blahblah.domain2.eu @ns3.domain1.de
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30214
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;blahblah.domain2.eu.    IN    A

;; AUTHORITY SECTION:
domain2.eu.        10800    IN    SOA    ns3.domain1.de. info.domain3.de. 2016071007 10800 3600 604800 10800

;; Query time: 12 msec
;; SERVER: 80.82.223.204#53(80.82.223.204)
;; WHEN: So Jul 10 15:51:05 CEST 2016
;; MSG SIZE  rcvd: 118
ns.domain2.eu.    86400    IN    A    80.82.223.203

;; Query time: 15 msec
;; SERVER: 80.82.223.203#53(80.82.223.203)
;; WHEN: So Jul 10 15:49:22 CEST 2016
;; MSG SIZE  rcvd: 101

Any ideas why that happens?

Thanks.

edit: I found this in bind9 log on slave dns servers:
zone domain2.eu/IN: serial number (1468157910) received from master 80.xxx.xxx.202#53 < ours (2016070807)
 
Hello John,

According to the error message the master server had changed SOA format from date (2016070807) to timestamp (1468157910).
Zones on slave servers should be either removed (and then synced from master) or manually updated with new SOA numbers (e.g. any timestamp in the past).
 
Back
Top