Submitted by sonoracomm on Fri, 03/26/2021 - 10:50 Pro Licensee
Hi,
Our Virtualmin seems to be working fine.
We have a Virtualmin Pro hosting server and another for Clustered DNS and the DNS records do appear to be propagating correctly.
The problem is that
virtualmin list-domains --multiline
Shows multiple (historical) DNS slave servers that are no longer correct.
I tried using
virtualmin modify-dns --domain xxxxxx --remove-slave "xxxxxx"
But the command does not work and acts like I entered the command incorrectly.
Any suggestions for me to clean up the output of
virtualmin list-domains --multiline
Thanks much,
G
Status:
Closed (fixed)
Virtualmin version:
6.15
Webmin version:
1.973
Comments
Submitted by sonoracomm on Fri, 03/26/2021 - 10:54 Pro Licensee Comment #1
Submitted by sonoracomm on Fri, 03/26/2021 - 11:16 Pro Licensee Comment #2
Also, it appears that
/etc/bind/named.conf.local
already has the correct ''also-notify'' and ''allow-transfer'' settings for all domains.
G
Submitted by JamieCameron on Fri, 03/26/2021 - 15:08 Comment #3
Virtualmin has it's own internal record for each domain of what the slave DNS servers are.
What error are you getting when you try the
--remove-slave "xxxxxx"
flag?Submitted by sonoracomm on Sun, 03/28/2021 - 14:04 Pro Licensee Comment #4
As I mentioned, no error is thrown.
The command does not execute normally...it displays as if the syntax was wrong and shows 'help':
Also, only the actual slave DNS server is listed in Webmin -> Cluster Slave Servers. There are no 'extra' DNS servers.
Thanks,
G
Submitted by JamieCameron on Sun, 03/28/2021 - 16:22 Comment #5
Ok, in that case, the work-around is the file the domain's config file by running :
virtualmin list-domains --domain yourdomain.com --file-only
then edit that file, and update the
dns_slave
line to remove the incorrect servers.Submitted by sonoracomm on Tue, 03/30/2021 - 12:36 Pro Licensee Comment #6
OK, thanks for that.
I edited all the domain files, which was very tedious, but everything seems fine afterward.
Should this be filed as a bug?
Thanks much,
G
Submitted by JamieCameron on Sat, 04/03/2021 - 21:30 Comment #7
I think the bug is how this situation occurred in the first place. How were these historical slave DNS servers setup or removed?
Submitted by JamieCameron on Sat, 04/03/2021 - 21:44 Comment #8
We will add an API command in future to make it easier to clean up these invalid configs though, by running
virtualmin modify-dns --domain example.com --sync-all-slaves
Submitted by sonoracomm on Mon, 04/05/2021 - 12:12 Pro Licensee Comment #9
I think your future solution is fine.
In our case, this Virtualmin Pro server has been upgraded several times over the years. There's no way I can say "how this situation occurred in the first place".
We have been running slave DNS for many years successfully, but I'm not sure when this situation occurred.
Thanks very much and please close this ticket,
G
Submitted by JamieCameron on Thu, 04/08/2021 - 20:55 Comment #10
Sounds good to me
Submitted by IssueBot on Thu, 04/22/2021 - 20:56 Comment #11
Automatically closed - issue fixed for 2 weeks with no activity.