Tuesday, August 18, 2015

how not to go to hell or run named commands


some times is to good to named-checkzone before you commit those changes to bind.
  
i have a little script that issues named-checkzone on my zone off of the db. 
i do this for forward and reverse zones.  
   
 ...  
 #!/bin/bash  
   
 echo aplace forward  
 named-checkzone aplace.calledhell.com db.aplace.calledhell.com  
   
 echo anotherplace forward  
 named-checkzone anotherplace.calledhell.com db.anotherplace.calledhell.com  
   
 echo 6.66 reverse  
 named-checkzone 66.6.10.in-addr.arpa db.10.6.66  
   
 echo 6.67 reverse  
 named-checkzone 67.6.10.in-addr.arpa db.10.6.67  
 ...  
   
 and then i will load everything and tail my syslog for any lingering errors in another terminal.  
   
 ...  
   
 #!/bin/bash  
   
 echo 6.66 reverse  
 rndc reload 66.6.10.in-addr.arpa  
   
 echo 6.67 reverse  
 rndc reload 67.6.10.in-addr.arpa  
   
 echo aplace forward  
 rndc reload aplace.calledhell.com  
   
 echo anotherplace forward  
 rndc reload anotherplace.calledhell.com  
   
 ...  
   
i heart doing this domain by domain and subnet by subnet so i am not in a place called hell.
i mentioned keep another terminal open, right?  
Post a Comment