How to manually edit zone records?

jndawson

• September 22, 2020 16:59

CLOUDLINUX 7.8 WHM

• 

  cPanelLauren

  • September 30, 2020 22:22

  Hello, First of all, what you're requesting is a feature request before this doesn't exist by default:

  0
• 

  jndawson

  • October 02, 2020 19:38

  First of all, what you're requesting is a feature request before this doesn't exist by default:

  0
• 

  cPanelLauren

  • October 02, 2020 22:29

  The cache is most certainly the issue, I'm not understanding why it's not reloading the zone files based on the serial number increment and clearing the cache. If you dump the cache manually it should work: rndc flush
  then reload rndc reload
  You can create a cache dump at /var/cache/bind/named_dump.db
  by running: rndc dumpdb -cache
  

  0
• 

  jndawson

  • October 05, 2020 19:07

  The cache is most certainly the issue, I'm not understanding why it's not reloading the zone files based on the serial number increment and clearing the cache. If you dump the cache manually it should work: rndc flush
  then reload rndc reload
  You can create a cache dump at /var/cache/bind/named_dump.db
  by running: rndc dumpdb -cache
  

  
  Not sure why you thought this would work when it didn't work the dozen or so times we've tried it.

  0
• 

  cPanelLauren

  • October 06, 2020 15:46

  @jndawson I completely overlooked the fact that you'd flushed the cache prior, please excuse my oversight. I am human and make errors on occasion. For some reason, I thought you'd just run rndc reload
  . I can't replicate this behavior on a system running CentOS 7 w/ cPanel & WHM v90.0.12 The steps I took were:

  • Edit DNS zone file : vi /var/named/domain.tld.db
    
  • Modify A record IP for one domain
  • Update serial
  • Clear any caches rndc flushrndc reload
    
  • Restart the nameserver (just for good measure though it shouldn't be necessary) /scripts/restartsrv_named
    
  • Check zone file and WHM for update

  The only difference I have is that my server is not clustered. Does any other server in the cluster make changes to this one (i.e., are any set to write or synchronize changes to this one)

  0
• 

  jndawson

  • October 07, 2020 23:43

  @jndawson [snip] The only difference I have is that my server is not clustered. Does any other server in the cluster make changes to this one (i.e., are any set to write or synchronize changes to this one)

  
  Yes, clustered as noted in the original post. I would expect that after flushing, stopping, making the changes, restarting, one would think that DNS would use the newly edited zone.

  0
• 

  jndawson

  • October 08, 2020 19:36

  Update: We rebooted the server for a kernel update. We expected that the edited zone would be picked up. It wasn't. The server is still displaying the old zone in WHM, even though the hard file is the edited zone. We have done manual edits in the past with no issues, but it was a couple of years ago. Clearly something was broken on the back end while trying to implement the new zone manager. Our next effort will include disabling DNS clustering and see if THAT works.

  0
• 

  SamuelM

  • October 09, 2020 03:15

  Hello @jndawson Based on the information you provided, it does sound as though DNS Clustering is the culprit. If disabling DNS Clustering temporarily does not solve the problem, then please feel free to submit a ticket using the link my signature.

  0

Please sign in to leave a comment.