4 Čec
2012
4 Čec
'12
12:57
Hello again. Here's another one.
I noticed that zone data contains relative notation such as
'@' but no $ORIGIN causes error.
knotc checkzone says:
-----
kohi@lars[1]% /usr/bin/sudo /proj/knot-1.0.6/sbin/knotc checkzone example1.jp
[sudo] password for kohi:
2012-07-04T19:52:19.603883+09:00 Using '/proj/knot-dns/etc/knot.conf' as default
configuration.
2012-07-04T19:52:19.615871+09:00 [error] /proj/dns/namedb/example1.jp:3: @ used, but no
$ORIGIN specified.
2012-07-04T19:52:19.631618+09:00 [error] /proj/dns/namedb/example1.jp:11: Zone file does
not contain SOA record!
-----
And knotc compile says:
-----
kohi@lars[2]% /usr/bin/sudo /proj/knot-1.0.6/sbin/knotc compile
2012-07-04T19:54:02.023025+09:00 Using '/proj/knot-dns/etc/knot.conf' as default
configuration.
2012-07-04T19:54:02.039299+09:00 Parsing file '/proj/dns/namedb/example1.jp',
origin 'example1.jp.' ...
2012-07-04T19:54:02.051637+09:00 [error] /proj/dns/namedb/example1.jp:3: @ used, but no
$ORIGIN specified.
2012-07-04T19:54:02.052790+09:00 [error] /proj/dns/namedb/example1.jp:11: Zone file does
not contain SOA record!
2012-07-04T19:54:02.053653+09:00 [error] Compilation of 'example1.jp.' failed,
knot-zcompile return code was '1'
-----
It complains even though it knows that "origin 'example1.jp.' ...".
Is this behavior by design policy? Or I wish it to be
enhanced.
Best regards,
Koh-ichi Ito
4 Čec
4 Čec
13:17
Hello,
first of all, thanks a lot for trying Knot-DNS. As for you report,
indeed, using '@' with no $ORIGIN specified is an error on purpose.
Although origin is always given in config we thought that '@' should
only correspond to what is in the zone file itself. But I suppose we
could change that if there is a valid case when using '@' with no
$ORIGIN would make sense.
Regards,
Jan.
On Wed, 2012-07-04 at 19:57 +0900, Koh-ichi Ito wrote:
Hello again. Here's another one.
I noticed that zone data contains relative notation such as
'@' but no $ORIGIN causes error.
knotc checkzone says:
-----
kohi@lars[1]% /usr/bin/sudo /proj/knot-1.0.6/sbin/knotc checkzone example1.jp
[sudo] password for kohi:
2012-07-04T19:52:19.603883+09:00 Using '/proj/knot-dns/etc/knot.conf' as default
configuration.
2012-07-04T19:52:19.615871+09:00 [error] /proj/dns/namedb/example1.jp:3: @ used, but no
$ORIGIN specified.
2012-07-04T19:52:19.631618+09:00 [error] /proj/dns/namedb/example1.jp:11: Zone file does
not contain SOA record!
-----
And knotc compile says:
-----
kohi@lars[2]% /usr/bin/sudo /proj/knot-1.0.6/sbin/knotc compile
2012-07-04T19:54:02.023025+09:00 Using '/proj/knot-dns/etc/knot.conf' as default
configuration.
2012-07-04T19:54:02.039299+09:00 Parsing file '/proj/dns/namedb/example1.jp',
origin 'example1.jp.' ...
2012-07-04T19:54:02.051637+09:00 [error] /proj/dns/namedb/example1.jp:3: @ used, but no
$ORIGIN specified.
2012-07-04T19:54:02.052790+09:00 [error] /proj/dns/namedb/example1.jp:11: Zone file does
not contain SOA record!
2012-07-04T19:54:02.053653+09:00 [error] Compilation of 'example1.jp.' failed,
knot-zcompile return code was '1'
-----
It complains even though it knows that "origin 'example1.jp.' ...".
Is this behavior by design policy? Or I wish it to be
enhanced.
Best regards,
Koh-ichi Ito
_______________________________________________
knot-dns-users mailing list
knot-dns-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users
14:56
Hello,
strike my last email, after a short discussion we decided to allow
usage of '@' even when no $ORIGIN directive is used. The fix is now in
our "development" branch in git repository (see our webpage for more
info) and will be present in upcoming Knot version 1.1. Thanks for your
report!
Regards,
Jan.
On Wed, 2012-07-04 at 19:57 +0900, Koh-ichi Ito wrote:
Hello again. Here's another one.
I noticed that zone data contains relative notation such as
'@' but no $ORIGIN causes error.
knotc checkzone says:
-----
kohi@lars[1]% /usr/bin/sudo /proj/knot-1.0.6/sbin/knotc checkzone example1.jp
[sudo] password for kohi:
2012-07-04T19:52:19.603883+09:00 Using '/proj/knot-dns/etc/knot.conf' as default
configuration.
2012-07-04T19:52:19.615871+09:00 [error] /proj/dns/namedb/example1.jp:3: @ used, but no
$ORIGIN specified.
2012-07-04T19:52:19.631618+09:00 [error] /proj/dns/namedb/example1.jp:11: Zone file does
not contain SOA record!
-----
And knotc compile says:
-----
kohi@lars[2]% /usr/bin/sudo /proj/knot-1.0.6/sbin/knotc compile
2012-07-04T19:54:02.023025+09:00 Using '/proj/knot-dns/etc/knot.conf' as default
configuration.
2012-07-04T19:54:02.039299+09:00 Parsing file '/proj/dns/namedb/example1.jp',
origin 'example1.jp.' ...
2012-07-04T19:54:02.051637+09:00 [error] /proj/dns/namedb/example1.jp:3: @ used, but no
$ORIGIN specified.
2012-07-04T19:54:02.052790+09:00 [error] /proj/dns/namedb/example1.jp:11: Zone file does
not contain SOA record!
2012-07-04T19:54:02.053653+09:00 [error] Compilation of 'example1.jp.' failed,
knot-zcompile return code was '1'
-----
It complains even though it knows that "origin 'example1.jp.' ...".
Is this behavior by design policy? Or I wish it to be
enhanced.
Best regards,
Koh-ichi Ito
_______________________________________________
knot-dns-users mailing list
knot-dns-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users
22:00
[ Quoting <jan.kadlec(a)nic.cz> in "Re: [knot-dns-users] origin
doesn't..." ]
Hello,
strike my last email, after a short discussion we decided to allow
usage of '@' even when no $ORIGIN directive is used. The fix is now in
our "development" branch in git repository (see our webpage for more
info) and will be present in upcoming Knot version 1.1. Thanks for your
report!
Shouldn't default for @ just be . (the root). I use that in some code of
mine, and it works OK.
grtz Miek
5 Čec
5 Čec
11:09
Hi Miek,
as I found out, according to RFC 1035: 'A free standing @ is used to
denote the current origin.' and from various other references to
'origin' it seems that the default origin should be the zone name. This
also corresponds with Bind behaviour (see their manual:
http://ftp.isc.org/isc/bind9/cur/9.9/doc/arm/Bv9ARM.ch06.html#id2598969).
Regards,
Lubos
On 04-Jul-12 22:00, Miek Gieben wrote:
[ Quoting<jan.kadlec(a)nic.cz> in "Re:
[knot-dns-users] origin doesn't..." ]
--
L(ubos( Slovák Knot DNS
CZ.NIC Labs http://www.knot-dns.cz
-------------------------------------------
Americká 23, 120 00 Praha 2, Czech Republic
Email: lubos.slovak(a)nic.cz
WWW: http://labs.nic.cz http://www.nic.cz
-------------------------------------------
Please consider the environment before printing this email.
Join the campaign at http://thinkBeforePrinting.org
Hello,
strike my last email, after a short discussion we decided to allow
usage of '@' even when no $ORIGIN directive is used. The fix is now in
our "development" branch in git repository (see our webpage for more
info) and will be present in upcoming Knot version 1.1. Thanks for your
report!
Shouldn't default for @ just be . (the root). I use that in some code
of
mine, and it works OK.
grtz Miek
_______________________________________________
knot-dns-users mailing list
knot-dns-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users
12:44
[ Quoting <lubos.slovak(a)nic.cz> in "Re: [knot-dns-users] origin
doesn't..." ]
Hi Miek,
as I found out, according to RFC 1035: 'A free standing @ is used to denote the
current origin.' and from various other references to 'origin' it seems that
the default origin should be the zone name. This also corresponds with Bind
behaviour (see their manual: http://ftp.isc.org/isc/bind9/cur/9.9/doc/arm/
Bv9ARM.ch06.html#id2598969).
hello,
Yes, you are right. But even before you start parsing a stand-alone zonefile, you
need to to start somewhere.... If no $ORIGIN is defined and you have no clue on
which zone you are about to read, what $ORIGIN do you append to the ownername
of SOA record if that was unqualified?
(Again, if you are writing a nameserver, this case doesn't apply, because you
*always* now what zone you are reading, but for a stand alone library it is
important, see: https://github.com/miekg/dns/blob/master/zscan.go#L162)
Kind regards,
Miek Gieben
14:43
Ok, right, didn't consider that (as I'm writing only a nameserver :-).
Nevertheless, I would say that it's not eligible to consider root to be
the default origin. I personally would reject zone which has no $ORIGIN
directive at the beginning, nor a FQDN as the owner of the SOA record.
But I suppose this is one of the points where the standards get blurry
and any interpretation is right as long as one documents it properly.
LS
On 05-Jul-12 12:44, Miek Gieben wrote:
[ Quoting<lubos.slovak(a)nic.cz> in "Re:
[knot-dns-users] origin doesn't..." ]
--
L(ubos( Slovák Knot DNS
CZ.NIC Labs http://www.knot-dns.cz
-------------------------------------------
Americká 23, 120 00 Praha 2, Czech Republic
Email: lubos.slovak(a)nic.cz
WWW: http://labs.nic.cz http://www.nic.cz
-------------------------------------------
Please consider the environment before printing this email.
Join the campaign at http://thinkBeforePrinting.org
Hi Miek,
as I found out, according to RFC 1035: 'A free standing @ is used to denote the
current origin.' and from various other references to 'origin' it seems that
the default origin should be the zone name. This also corresponds with Bind
behaviour (see their manual: http://ftp.isc.org/isc/bind9/cur/9.9/doc/arm/
Bv9ARM.ch06.html#id2598969).
hello,
Yes, you are right. But even before you start parsing a stand-alone zonefile, you
need to to start somewhere.... If no $ORIGIN is defined and you have no clue on
which zone you are about to read, what $ORIGIN do you append to the ownername
of SOA record if that was unqualified?
(Again, if you are writing a nameserver, this case doesn't apply, because you
*always* now what zone you are reading, but for a stand alone library it is
important, see: https://github.com/miekg/dns/blob/master/zscan.go#L162)
Kind regards,
Miek Gieben
_______________________________________________
knot-dns-users mailing list
knot-dns-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users
4318
days inactive
4319
days old
6 comments
4 participants
participants (4)
-
Jan Kadlec -
Koh-ichi Ito -
Lubos Slovak -
Miek Gieben