Trying to rename a parent domain comes up with:
Failed to change domain name : The following DNS sub-domains are using this server's zone file
Even moving the sub server to another parent or making it a parent server the original parent still cannot be renamed. I need to change a domain for a server parent and sub I created on a noip enhanced hosting service using sytes.net to a TLD I just purchased .com. With this bug I cannot change the server over and would have to delete everything and re set it up on the new virtual server.
I created a thread here and had no replies so I thought id submit a ticket. I don't want to have to re-install everything just to change the domain name and details.
Changing a parent without a sub works and changing a sub works as expected but changing a parent with a sub errors out. What I expect to happen to be able to able to change the parent domain name and update both the parent and sub together to the new domain, users and mail addresses etc.
Comments
Submitted by JamieCameron on Sat, 05/19/2018 - 14:17 Comment #1
This is sort-of expected when DNS zone sharing is in use. The work-around is to turn off DNS for the sub-domain, rename the parent, then turn DNS back on again (on the Edit Virtual Server page).
Submitted by drguild on Sun, 05/20/2018 - 02:50 Comment #2
I have tried that, already tried turning off dns for the sub and trying to rename the parent, the error message still shows. I have tried turning off dns for both the patent and sub and the error still shows. I have tried disabling the sub after removing the dns the error still shows.
Updates: I got it going but there are bugs I will outline how I had to do it. I turned off the dns and disabled the sub server backed it up and deleted it and renamed the parent which worked fine. Upon re-importing the sub server and enabling dns this error showed. Also bind would no longer start.
Re-starting DNS server ..
.. failed : Failed to start BIND : Starting named: Error in named configuration: zone localhost.localdomain/IN: loaded serial 0 zone localhost/IN: loaded serial 0 zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 0 zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0 zone 0.in-addr.arpa/IN: loaded serial 0 zone server.revnet/IN: loaded serial 1404637639 zone 1.168.192.in-addr.arpa/IN: loaded serial 1404710841 zone drguild.noip.me/IN: loaded serial 1404737594 zone revnet/IN: loaded serial 1404993344 zone 192.168.1.1/IN: loaded serial 1405921936 zone 110.175.205.112/IN: loaded serial 1405923871 zone david-ocau.noip.me.disabled/IN: loaded serial 1409150156 zone cloudmin.revnet/IN: loaded serial 1452053310 zone suptest.sytes.net/IN: loaded serial 1503631689 zone papiolti1.sytes.net/IN: loaded serial 1525352993 zone cajgo-support.com/IN: loaded serial 1526398640 /var/named/community.cajgo-support.sytes.net.hosts:1: no TTL specified; zone rejected /var/named/community.cajgo-support.sytes.net.hosts:2: no TTL specified; zone rejected /var/named/community.cajgo-support.sytes.net.hosts:3: no TTL specified; zone rejected /var/named/community.cajgo-support.sytes.net.hosts:4: no TTL specified; zone rejected /var/named/community.cajgo-support.sytes.net.hosts:5: no TTL specified; zone rejected /var/named/community.cajgo-support.sytes.net.hosts:6: no TTL specified; zone rejected /var/named/community.cajgo-support.sytes.net.hosts:7: no TTL specified; zone rejected /var/named/community.cajgo-support.sytes.net.hosts:8: no TTL specified; zone rejected /var/named/community.cajgo-support.sytes.net.hosts:9: no TTL specified; zone rejected zone community.cajgo-support.sytes.net/IN: loading from master file /var/named/community.cajgo-support.sytes.net.hosts failed: no ttl zone community.cajgo-support.sytes.net/IN: not loaded due to errors. _default/community.cajgo-support.sytes.net/IN: no ttl [FAILED]
I then changed the domain name on the sub but bind couldn't start as all the entries are for the older dns were still listed in bind, even though I disabled dns before doing the backup. Manually deleting the 'old' sub servers zone that was still listed then restarting bind and retoggling the dns off and on the server is now all ok the new domain.
So Now I have things on the new domain but I 'had' to:
Now everything seems to be working apart from updating lets encrypt and making some alias to point the old dns name to the new one which is easy. So yea theirs some bugs with changing dns but I sorted it here a kinda long way I hope that this helps you guys see what the issue is.
Submitted by JamieCameron on Mon, 05/21/2018 - 00:07 Comment #3
Ok, I found the bug that can cause this problem with the rename - it will be fixed in the next Virtualmin release.
Submitted by IssueBot on Thu, 10/11/2018 - 20:07 Comment #4
Automatically closed - issue fixed for 2 weeks with no activity.