Bug#710362: ldap2zone: will some time generate invalid DNS host name entries

[Petter Reinholdtsen]

Control: reopen -1
Control: found -1 0.2-4
Control: tags -1 + help

[Petter Reinholdtsen]
> Running 'cd /etc/bind; git log -p' as root you should be able to see
> what the zone file looked like when it was broken, and how it was
> before it was broken.

I very much welcome details on how your zone file was broken.

I've finally been able to reproduce this issue myself by adding a MX
record with only one word in the following text field in gosa.  MX
should be followed by a number and a host name, but bind accept also
non-number values.  But if there is only one value (aka for example
"MX mail" instead of "MX 10 mail"), bind will reject the zone.

If one uses gosa to add a MX entry with only one word in the text
file, the DNS subsystem break.

> The ldap2zone version I uploaded yesterday will check if bind liked
> the new zone file, and revert to the old one if bind did not, and
> syslog an error when this happen.  It should ensure bind never end
> up with a broken file after restart.

This fix did not work.  The ldap2bind script would call 'rndc reload
intern', which I expected would return an error if something is wrong.
But it do not, it only print 'zone reload queued' and return success
no matter how broken the zone is.

Not quite sure how to fix this.

-- 
Happy hacking
Petter Reinholdtsen


-- 
To UNSUBSCRIBE, email to debian-edu-REQUEST at lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster at lists.debian.org
Archive: https://lists.debian.org/20141004191313.GW10128@ulrik.uio.no