Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] Updating the server reporting scripts

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] Updating the server reporting scripts


Chronological Thread 
  • From: Administrador <admin AT bambusoft.com>
  • To: discuss AT lists.opennicproject.org
  • Subject: Re: [opennic-discuss] Updating the server reporting scripts
  • Date: Fri, 19 Dec 2014 09:53:13 -0600
  • Organization: Bambusoft - http://www.bambusoft.com

Hi Jeff:

I undesrtand this scripts checks DNS servers, but I don't know if zone transfer files can be checked, ... just see one example:

Each time my server updates zones, some files could contain errors like this:
...
19-Dec-2014 09:24:59.322 general: warning: zone bit/IN: -.bit/A: bad owner name (check-names)
19-Dec-2014 09:24:59.324 general: warning: zone bit/IN: andrey_vasilyev.bit/A: bad owner name (check-names)
19-Dec-2014 09:24:59.324 general: warning: zone bit/IN: *.andrey_vasilyev.bit/A: bad owner name (check-names)
19-Dec-2014 09:24:59.325 general: warning: zone bit/IN: artandhobby.bit/NS: ns5.rcs.-rds.ro: bad name (check-names)
19-Dec-2014 09:24:59.362 general: warning: zone bit/IN: linuxexchange-.bit/A: bad owner name (check-names)
19-Dec-2014 09:24:59.362 general: warning: zone bit/IN: *.linuxexchange-.bit/A: bad owner name (check-names)
...

This type of errors could be avoided with correct input validations, but in the mean time, slaves servers are being filled with unusefull log entries
The real problem is that we spend more time to review logs.

Does the script can validate zone files? (again, some configurations are server owner responsability, but affect others)

Regards

Mario Rdz


El 18/12/2014 a las 05:29 p.m., Jeff Taylor escribió:
I've spent the last couple days rewriting a new test procedure, and it is nearing completion.  The goal was to decrease how hard the testing hits NS0, plus create a single interface that could be used consistently for all testing -- right now there are separate scripts for the tests seen on the report page and the test performed on an individual server.  This is something we've had problems with in the past, where a server may appear to pass the individual page, but fail on the report page.

So as I'm wrapping up this bit of code, and I was wondering if there were any ideas for new tests that should be performed on each server?  Currently I check for proper use of NXDOMAIN, the SOA and NS records for each OpenNIC TLD, and for tier-2 servers I check five ICANN domains (either A or AAAA records, depending on if the tier-2 server is IPv4 or IPv6).  If there are any query failures, I am keeping a copy of the output for troubleshooting.  So what else could be tested for?  What could be useful for troubleshooting?  Any other general information that should be checked?




--------
You are a member of the OpenNIC Discuss list. 
You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org

Administración / Soporte técnico
admin AT bambusoft.com / +52 (33) 1815-6186



Archive powered by MHonArc 2.6.19.

Top of Page