Richard G
Verified User
I'm running 1.58.2 so the newest DA and multiserver setup.
Yesterday I created some DNSSec domains which worked fine. Today suddenly 1 (from my company) wasn't signed anymore and my domain was not reachable anymore from a lot of servers.
I had to use this command do get the files over to the other server, after that things started to work again:
So far so good.
But I also removed a DNSSec from another domain and forgot 1 thing:
But this brought me to the idea to also check this on the remote server of the multiserver setup.
I've seen the remove server of the multiserver setup only uses the .db files and not the .db.signed files. Is that correct?
Because if the main server would shut down, the secondary server is asked, and since dnssec is missing there, won't this generate incorrect answers?
Yesterday I created some DNSSec domains which worked fine. Today suddenly 1 (from my company) wasn't signed anymore and my domain was not reachable anymore from a lot of servers.
I had to use this command do get the files over to the other server, after that things started to work again:
Code:
echo 'action=rewrite&value=named&domain=mycompany.com' >> /usr/local/directadmin/data/task.queue
So far so good.
But I also removed a DNSSec from another domain and forgot 1 thing:
after that, named would start again.Edit the named.conf. Change the zone entry for that domain from domain.com.db.signed to domain.com.db
But this brought me to the idea to also check this on the remote server of the multiserver setup.
I've seen the remove server of the multiserver setup only uses the .db files and not the .db.signed files. Is that correct?
Because if the main server would shut down, the secondary server is asked, and since dnssec is missing there, won't this generate incorrect answers?