I have VM Pro on one Cloud VPS
I have another Cloud VPS that I installed Webmin onto.
I followed the instructions here: Secondary DNS
Going by the instructions everything seems to be ok, I checked on Secondary DNS Bind and it said records were received so Bind should be ok.
Question is, for the few websites I have hosted on my VM Pro server, do I add the Secondary DNS NS to them? Such as NS3.backupdns.com
The directions state that new servers will have the secondary dns added.
should I add to the VM pro server already established websites the secondary name server records?
Virtualmin only adds those NS records for domains being newly added, and assuming you’ve configured Virtualmin to know about them.
For existing domains from before you configured Virtualmin to do so, you need to add/update those NS records, if you want them to exist.
Virtualmin doesn’t do things behind your back. If you had it configured in a specific way when you created a domain, it would be dangerous for it to decide it knows better and change that configuration. (You could disable DNS, make sure the records are deleted, and then re-enable DNS and it would generate new records based on the current configuration.)
@Joe
Thanks for the reply and what you stated makes sense (I’m still learning )
I have the Secondary DNS Server Syncing great now. Not sure why but on the Secondary DNS Server (Debian 12 and latest Webmin) the files at /var/lib/bind were root:bind so chowned them to bind:bind and all started syncing. Took me a bit to figure this out, I’m used to RHEL and just getting my feet wet with Debian.
I don’t know what ownership is normal for BIND files on Debian. BIND certainly doesn’t run as the root user, so it would depend on the permissions, as to whether it could work with root:bind ownership…it would need group write permissions to be able to update zones via transfer.
)