nsd+CRLF = confusing error messages
Arnt Gulbrandsen
arnt at gulbrandsen.priv.no
Mon Mar 27 17:58:24 UTC 2006
Hi,
I think it would be better if nsd accepts CRLF as well as LF as line ending.
Not because it's such a great idea to use Windows, but because at
present the error messages are a little misleading.
zonec: reading zone "beispiel.de".
primary/db.beispiel.de:1: error: invalid TTL value: 86400
primary/db.beispiel.de:7: error: syntax error
primary/db.beispiel.de:11: error: RR before SOA skipped
primary/db.beispiel.de:13: error: RR before SOA skipped
'rimary/db.beispiel.de:13: error: invalid IPv4 address '212.125.101.195
'rimary/db.beispiel.de:19: error: invalid IPv4 address '212.125.101.194
'rimary/db.beispiel.de:20: error: invalid IPv4 address '212.125.101.195
zonec: processed 0 RRs in "beispiel.de".
I suspect it's easier to accept CRLF than to generate a less misleading
error message ;)
Arnt
More information about the nsd-users
mailing list