cPanel DNSONLY

Answered

Unnamed User

• November 11, 2024 18:37

Is anyone noticing that when you delete a cpanel account then cpanel does not remove the zone file entry in named.conf in any cpanel dnsonly remote servers, but it does remove the actual zone file in /var/named 

This causes a major issue in that if you then re-add the cpanel account later on then cpanel does not check if the zone entry in named.conf exists 'before' re-adding the zone entry in named.conf and you then end up with duplicate entries in named.conf furthermore if you restart your dnsonly server it brings your nameserver down/offline as bind will not restart with the duplicate entries in named.conf.

 

• 

  cPRex Jurassic Moderator

  • November 12, 2024 15:16

  Hey there!  I wasn't able to reproduce this on a test cluster as the entry in /var/named was removed.  Here is the file after creating the domain:

  # grep rextesting.com /etc/named.conf
  zone "rextesting.com" {
      file "/var/named/rextesting.com.db";

  and here is that file after I terminated the account from cPanel:

  # grep rextesting.com /etc/named.conf
  [root@45-63-66-195 ~]# 

  Is it possible that you have the "keep DNS Zone" option enabled on the server and that is causing this behavior?

  If not, and if you have a server that is reliably exhibiting this behavior, could you create a ticket so this can be investigated?

  0
• 

  Unnamed User

  • November 12, 2024 15:46

  I notice that when you grep the domain after adding it, it only comes up once for you, in my system it has Internal & External views and it appears twice after adding a zone, once in the Internal view and once in the External view? and both entries are still there after deleting the zone, although it does remove the actual .db zone file from /var/named/

  The "keep dns zone" checkbox is not selected when deleting. I have two dnsonly servers that this happens on exactly the same, they are on cpanel version 122.0.27.

   

  0
• 

  cPRex Jurassic Moderator

  • November 12, 2024 15:55

  It's normal for it to come up twice - I just edited my grep for clarity.

  Could you create a ticket for that behavior?

  0
• 

  Unnamed User

  • November 12, 2024 16:09

  Sure I would open a ticket, but I just tested again, before placing the ticket, and its working now and appears to be removing the entry from named.conf and the zone file from /var/named

  I noticed that it happened for several domains in the past, but as I say it appears to be working now

  Thanks for looking into this for me

  0
• 

  cPRex Jurassic Moderator

  • November 12, 2024 16:12

  I'm glad to hear things are working well now.  It's possible there was a bit of a delay before those were removed to avoid unnecessary restarts of the named service.  If you run into anything else just let me know!

  0
• 

  Unnamed User

  • November 12, 2024 17:07

  Whoops I spoke too soon. I just deleted another account and it left the zone entires in named.conf so it seems to be intermittent. Then I deleted the test account again that I tried previously and this time it also left the named.conf entries behind

  0
• 

  cPRex Jurassic Moderator

  • November 13, 2024 14:56

  It would likely be best to create a ticket on this issue so the problem can be seen in action.

  0

Please sign in to leave a comment.