Discuss mailing list

[Jeff Taylor <shdwdrgn AT sourpuss.net>]

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