• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Something switched Master/Slave DNS setting

N

Northern Outdoors

New Pleskian
I discovered today that something has switched the DNS Master/Slave setting for the only domain hosted in my Web Pro installation. (I'm the only person with a Plesk login on this server.) I had it set as a slave because our DNS records are hosted at StackPath. I don't know what might have switched to a default Master DNS config for the domain but it made a mess of things for a bit. Maybe the recent DNSSEC extension upgrade had something to do with it?

Is there a way for me to see when and how this setting was changed from slave to master? Log files of these kinds of changes anywhere?

Thanks.
 
You must log in or register to reply here.

Similar threads

wasiwarez
Issue Issues with Plesk/bind configuring as master and slave nameserver
Replies
7
Views
4K
wasiwarez
wasiwarez
R
Question INWX as a secondary Nameserver
Replies
1
Views
4K
ralerbon
R
V
Issue Cannot migrate domains because of error 'Subscription xxxx has no IP addresses on target system'
Replies
2
Views
4K
scsa20
scsa20
B
Issue Slave DNS servers not updating zone from target server after migrating domain from source server.
Replies
3
Views
4K
BigBlock
B
E
Resolved Made a mistake, changed server hostname, please advise
Replies
2
Views
2K
elliotpa04
E
Back
Top