• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

DNS-records I recently modified on Master DNS-server sets the SOA-record to the 2nd

F

Frater

Regular Pleskian
I wrote a script to test the integrity of my DNS and run it from time to time on my server...

I just ran it today and it discovered I suddenly have 5 domains with SOA-records that doesn't point to itself.
They point to the secondary nameserver.

They are records that exist for years and were for sure correct before (I know this because of that script).

If I do a "restore defaults" it isn't corrected and if I switch to slave and then back to master it doesn't change either...

The file /var/named/run-root/var/obfuscated.com is updated, but the slave-DNS stays in that file...
The only way I'm able to correct it is by deleting the NS-record with the slave DNS and adding it again.

I assume there's some mechanism that scans the NS-records and then decides to make that one the SOA.
This has always worked fine... also on this server.
 
Funny you mention it....
I have a problem with adding new zones. They are not added to the slave server.
After they are manually added there, the syncing works as it should.

That slave server is 3rd party and I have to debug it together with them.
Thus far we can't find the reason.
They are using that slave server for their Plesk servers and some other 3rd parties and they don't have a problem.

I haven't seen any reports of the slave server not working.
Could you point me to it?
That server was running 10.x and it wasn't working then. (for new zones)
 
Could I have an answer?
I really want my 11.53 version to properly work with my secondary DNS
 
You must log in or register to reply here.

Similar threads

B
Issue Slave DNS servers not updating zone from target server after migrating domain from source server.
Replies
3
Views
700
BigBlock
B
Polli
Nameserver DNS entrys for subdomains are set wrong when plesk is primary DNS
Replies
2
Views
803
Sebahat.hadzhi
Sebahat.hadzhi
N
Question Two Plesk Obsidian Linux Servers Master and Slave DNS
Replies
2
Views
877
Geisti
G
Polli
Issue Subdomain show wrong DNS entrys but is reachable
Replies
3
Views
790
scsa20
scsa20
Dmytro
Issue Slave dns do not work on some servers
Replies
2
Views
459
Dmytro
Dmytro
Back
Top