How to properly terminate accounts after using Transfer Tool when you have a DNS cluster?

[benito]

Hello!

Today we have a big problem. We usually move accounts between our servers, and after a couple4 of days we terminate them with the option to keep the dns zone.

Keep the DNS zones

When you terminate an account, you can keep the domain’s zone file in the DNS server. This is useful, for example, if you move an account to a different server that is a part of the same DNS cluster as the previous server, and you want to delete the account information from the original server. To keep the DNS zones for an account that you wish to terminate, select the associated checkbox in the Keep DNS Zone column.

The thing is we needed to sync servers to a new DNSONLY in the cluster and then we screwed. A lot of previously moved accounts zones with wrong data where pushed to the cluster.

Now we are working with the tool /scripts/autorepair unmanaged_zones to remove all the unwanted zones on each server.

So, my question is, we need to use that tool after each use of Transfer Tool or there is a better way to terminate the account and delete the zone in the server but not in the cluster?

Thanks

 

[benito]

By the way, we always thought that this option (Keep the DNS zones) only retained the DNS zone in the cluster. Not on the server.

Additional question, do I need to disable DNS cluster before run /scripts/unmanaged_zones or this script only remove the zone from the current server?

 

[cPRex]

Hey there! I confirmed that choosing the "Keep DNS Zone" option when terminating he account does keep the zone on the cluster machine and allows you to terminate the account on the source.

You do not need to disable the cluster before running the unmanaged_zones tool as long as you're sure you're performing the correct action.

 

[benito]

Hey @cPRex,

I understand that " Keep DNS Zone " it keeps the records in the cluster. My problem was a lot of unwanted zones left on source server and later sync that server with the cluster pushing old zones.

So, how I have to terminate an account to keep the zone only in the cluster and not in the source server?

 

[cPRex]

On my test cluster, that isn't what I experienced. The zone was removed from the Source machine but left on the Cluster member, which didn't lead to any unmanaged zones getting pushed to the cluster in the future since they didn't exist.

If that isn't what you're seeing on your end, it might be best to create a ticket so we can replicate this on your particular cluster.

 

[benito]

On my test cluster, that isn't what I experienced. The zone was removed from the Source machine but left on the Cluster member, which didn't lead to any unmanaged zones getting pushed to the cluster in the future since they didn't exist.

If that isn't what you're seeing on your end, it might be best to create a ticket so we can replicate this on your particular cluster.

Interesting, do you know if this behavior is recent? Maybe my problem was with cPanel accounts terminated several years ago. I will test it right now.

 

[cPRex]

I tried to look through the system but I couldn't find any exact details on when this change happened.

 

[benito]

Hello!

Yes, I can reproduce the thing.

1. Created a new account on server 1.
2. Used transfer tool in server 2 and moved the account.
3. Go to terminate accounts on server 1 and terminated the account keeping the dns zone.
4. In server 1 the zone still exists in /var/named/

I will open a ticket if this is not the right way to terminate an account.

 

[cPRex]

If you could open a ticket that would be great!

 

[benito]

If you could open a ticket that would be great!

Done. 94537922

Thanks

 

[cPRex]

Thanks - I'm following along now.

 

[cPRex]

It looks like we were able to recommend some changes to the cluster configuration to get this resolved on your side. Let us know if you need anything else!

 

[benito]

Thanks, now everything is clear.

 

[wintech2003]

1. Created a new account on server 1.
2. Used transfer tool in server 2 and moved the account.
3. Go to terminate accounts on server 1 and terminated the account keeping the dns zone.
4. In server 1 the zone still exists in /var/named/

This is a common issue for us too - would you mind sharing the recommended changes to avoid this from happening?

 

[scottc]

It looks like we were able to recommend some changes to the cluster configuration to get this resolved on your side. Let us know if you need anything else!

This is a common problem for us as well. Can you give us information on how to fix it or do we need to open a ticket?

 

[cPRex]

The original poster had an issue with their cluster configuration, so it would likely be best to create a ticket so we can see the issue in real-time on the affected machine.