Discuss mailing list

[Jeff Taylor <shdwdrgn AT sourpuss.net>]

I decided to check my own logs, and did in fact find the same errors.  Of course I don't pay any attention to that particular log file, I only watch the query logs for problems.  If these warnings are taking up so much of your time, maybe you should just filter them into a separate file?  If they are taking too much space, why not rotate your logs daily?  My operational logs only take about 5MB daily despite all the warnings, hardly anything to worry about.

For what its worth, as I said before these are just warnings and not actual errors.  The zone files work fine, they just don't fit into BIND's standard world-view.  You can in fact resolve -.bit (you have to escape the - symbol from linux command-line though) so the zone files are working correctly.  As I said before, BIND wouldn't load them or transfer them if the files were actually bad.

On 12/19/2014 12:16 PM, Administrador wrote:

Ok I agree with you those are not BIND errors, but there is a miscconfigured zone with invalid names.
I am not doing something special to get them...Warnings or errors the log files has a lot of them and take valuable resources (disk and time) ...

El 19/12/2014 a las 12:39 p.m., Jeff Taylor escribió:

I have to ask, what are you doing to get those errors?  BIND won't transfer a zone file unless it is valid and is able to be loaded by the master server.  I've never heard of anyone having issues with the .bit zone, even though there are a lot of oddball entries in it, and the messages you posted below are simply warnings and not actual failures of the zone.

On 12/19/2014 08:53 AM, Administrador wrote:

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

--------
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 Bambusoft http://www.bambusoft.com

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