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.
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.