Hi,
I am having difficulties running knot on an dualstack host. I want Knot
to listen on all IPv4 and all IPv6 interfaces. I am using this
interfaces section in config file:
interfaces {
allv4 { address 0.0.0.0; }
allv6 { address [::]; }
}
Using this config, Knot listens only on v4 address and gives an error
binding the v6 address:
2012-07-27T13:21:44.646094+02:00 Binding to interface 0.0.0.0 port 53.
2012-07-27T13:21:44.646197+02:00 [error] Cannot bind to socket (98).
2012-07-27T13:21:44.646233+02:00 [error] Could not bind to TCP interface
:: port 53.
2012-07-27T13:21:44.646240+02:00 Binding to interface :: port 53.
Changing interface order the other way around results in listening on v6
only with same error, yet also v4 connections are accepted, probably due
to IPV6_V6ONLY socket option not being turned on by Knot.
When I tried changing listening port on either line, problem
disappeared. I am using Debian package, version 1.0.6-1~bpo60+1.
Cheers,
Ondřej Caletka
Hello,
I'm new to KNOT and I'm trying to install it on a CentOS 6.3 (Final)
minimal install, I already updated openssl to the newest version and
install all the pre-requirements but when I run make command I get the
following error:
*************************
BINDIR=\"/usr/local/sbin\" -g -O2 -fpredictive-commoning
-I/usr/local/include -mmmx -msse -msse2 -msse3 -MT journal.lo -MD -MP
-MF .deps/journal.Tpo -c knot/server/journal.c -fPIC -DPIC -o
.libs/journal.o
In file included from knot/server/journal.c:26:
./common/crc.h:30:18: error: zlib.h: No such file or directory
In file included from knot/server/journal.c:26:
./common/crc.h: In function 'crc_init':
./common/crc.h:49: warning: implicit declaration of function 'adler32'
make[2]: *** [journal.lo] Error 1
make[2]: Leaving directory `/root/knot-1.0.6/src'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/root/knot-1.0.6/src'
make: *** [all-recursive] Error 1
*************************
Can any of you guys help me?
Best regards,
--
Eduardo Duarte
SIT-DNS
DNS.PT - https://www.dns.pt/
FCCN - http://www.fccn.pt/
Sorry, didn't send it to the list before..
L.
-------- Original Message --------
Subject: Re: [knot-dns-users] Fail to serve RFC 2317-ish zone
Date: Wed, 04 Jul 2012 15:12:59 +0200
From: Lubos Slovak <lubos.slovak(a)nic.cz>
To: Koh-ichi Ito <kohi(a)kkdlabs.jp>
Hi there,
thanks for the report! It's true that Knot DNS actually imposes quite
rigid rules to domain names. We will probably change that in future. But
we forgot about the RFC 2317 case, so thanks once more for the notice.
Will add support for / in domain names in the next release - that should
suffice.
Regards,
Lubos
On 07/04/2012 12:48 PM, Koh-ichi Ito wrote:
> Dear team,
>
> I found that Knot DNS v1.0.6(from tarball) fails to serve
> RFC 2317-ish zone, 32/27.2.0.192.in-addr.arpa, in this case.
>
> -----[ knot.conf ]------------------------------------------
> system {
> storage "/proj/knot-dns/var";
> }
> zones {
> 32/27.2.0.192.in-addr.arpa {
> file "/proj/dns/etc/namedb/32_27.2.0.192.in-addr.arpa";
> }
> }
>
> -----[ zone data ]------------------------------------------
> $TTL 1d
> $ORIGIN 32/27.2.0.192.in-addr.arpa
> @ IN SOA ns.example1.jp. hostmaster.example1.jp. (
> 2012070401
> 20m
> 15m
> 4w
> 15m )
> NS ns.example1.jp.
>
> -----[ The result ]-----------------------------------------
> kohi@lars[1]% /usr/bin/sudo /proj/knot-1.0.6/sbin/knotc -c /proj/knot-dns/etc/knot-2317.conf checkzone 32/27.2.0.192.in-addr.arpa
> [sudo] password for kohi:
> 2012-07-04T19:47:33.287327+09:00 [error] Config '/proj/knot-dns/etc/knot-2317.conf' - syntax error on line 5 (current token '32').
> 2012-07-04T19:47:33.287980+09:00 [error] Failed to parse configuration '/proj/knot-dns/etc/knot-2317.conf'.
> kohi@lars[2]%
> ------------------------------------------------------------
>
> Thanks in advance.
>
> 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
--
Ľuboš 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.czhttp://www.nic.cz
-------------------------------------------
Please consider the environment before printing this email.
Join the campaign at http://thinkBeforePrinting.org
Hi,
Is there any frontend for knotdns? We have different kind of users and for
non technicians is more difficult to manage from command line.
¡Thanks!
Hello team,
I experienced the following compile error while installing
knot-1.0.6(tarball from WWW site) on FreeBSD 8.3.
% make
Making all in src
make all-am
/bin/sh ../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -Wall -Ilibknot -DLIBEXECDIR='"/pub/knot-1.0.6/libexec"' -DSYSCONFDIR='"/pub/knot-1.0.6/etc"' -DSBINDIR='"/pub/knot-1.0.6/sbin"' -I/pub/include -I/usr/local/include -mmmx -msse -msse2 -msse3 -MT utils.lo -MD -MP -MF .deps/utils.Tpo -c -o utils.lo `test -f 'libknot/util/utils.c' || echo './'`libknot/util/utils.c
:
:
libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -Wall -Ilibknot -DLIBEXECDIR=\"/pub/knot-1.0.6/libexec\" -DSYSCONFDIR=\"/pub/knot-1.0.6/etc\" -DSBINDIR=\"/pub/knot-1.0.6/sbin\" -I/pub/include -I/usr/local/include -mmmx -msse -msse2 -msse3 -MT dthreads.lo -MD -MP -MF .deps/dthreads.Tpo -c knot/server/dthreads.c -fPIC -DPIC -o .libs/dthreads.o
knot/server/dthreads.c: In function 'dt_setaffinity':
knot/server/dthreads.c:864: error: 'cpu_set_t' undeclared (first use in this function)
knot/server/dthreads.c:864: error: (Each undeclared identifier is reported only once
knot/server/dthreads.c:864: error: for each function it appears in.)
knot/server/dthreads.c:868: warning: implicit declaration of function 'pthread_setaffinity_np'
knot/server/dthreads.c:868: error: expected expression before ')' token
*** Error code 1
Stop in /u1/share/pub/src/knot-dns/knot-1.0.6/src.
*** Error code 1
Stop in /u1/share/pub/src/knot-dns/knot-1.0.6/src.
*** Error code 1
Stop in /u1/share/pub/src/knot-dns/knot-1.0.6.
As an ad-hoc workaround, the following trial works fine.
% cd src
% mv config.h config.h.ORG
% cp config.h.ORG config.h
% ed config.h
10154
/HAVE_PTHREAD_SETAFFINITY_NP
#define HAVE_PTHREAD_SETAFFINITY_NP 1
s/^#define/#undef/
s/ 1$//
p
#undef HAVE_PTHREAD_SETAFFINITY_NP
s/^#define/#undef/
s/ 1$//
p
#undef HAVE_PTHREAD_SETAFFINITY_NP
w
10151
q
% diff -u config.h.ORG config.h
--- config.h.ORG 2012-06-30 14:56:16.000000000 +0900
+++ config.h 2012-06-30 15:08:09.000000000 +0900
@@ -107,7 +107,7 @@
#define HAVE_PSELECT 1
/* Define to 1 if you have the `pthread_setaffinity_np' function. */
-#define HAVE_PTHREAD_SETAFFINITY_NP 1
+#undef HAVE_PTHREAD_SETAFFINITY_NP
/* Define to 1 if you have the `regcomp' function. */
#define HAVE_REGCOMP 1
% cd ..
As long as invoke via knotc and easy query via dig, the
result binary seems to work fine.
Thanks in advance
--
kkdlabs.jp, featuring Koh-ichi Ito as just another DNS freak in town.
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
Hello,
Yesterday I replaced one of my authoritative servers with knot 1.0.5
(previously powerdns). I am already delighted by the simplicity of knot,
so thank you for a nice piece of software.
I tried some configurations and noticed that I was unable to correctly
run as an unprivileged user. It seems that the problem is:
- start knotd as root.root
- create empty pidfile (owned by root.root)
- drop privileges to user 'knot.knot'
- write pid to pidfile (and fail doing so)
- log error:
2012-06-11T22:23:06+02:00 julie knot[31184]: [warning] Failed to create
PID file '/var/lib/knot/knot.pid'.
2012-06-11T22:23:06+02:00 julie knot[31184]: Server started as a daemon,
PID = 31184
2012-06-11T22:23:06+02:00 julie knot[31184]: [warning] Server running
without PID file.
When stopping knotd later on, the following is logged, and knotd does
not stop running.
2012-06-11T22:23:38+02:00 julie knot[31210]: [warning] Server PID not
found, probably not running.
I guess that either the pid file need to be chowned to the unprivileged
user before privileges are dropped, or the pid needs to be written to
the file earlier. Note that the file *is* created (despite the error
messages saying something else), but it is empty.
Kind regards,
Tom
Dear team,
I found that Knot DNS v1.0.6(from tarball) fails to serve
RFC 2317-ish zone, 32/27.2.0.192.in-addr.arpa, in this case.
-----[ knot.conf ]------------------------------------------
system {
storage "/proj/knot-dns/var";
}
zones {
32/27.2.0.192.in-addr.arpa {
file "/proj/dns/etc/namedb/32_27.2.0.192.in-addr.arpa";
}
}
-----[ zone data ]------------------------------------------
$TTL 1d
$ORIGIN 32/27.2.0.192.in-addr.arpa
@ IN SOA ns.example1.jp. hostmaster.example1.jp. (
2012070401
20m
15m
4w
15m )
NS ns.example1.jp.
-----[ The result ]-----------------------------------------
kohi@lars[1]% /usr/bin/sudo /proj/knot-1.0.6/sbin/knotc -c /proj/knot-dns/etc/knot-2317.conf checkzone 32/27.2.0.192.in-addr.arpa
[sudo] password for kohi:
2012-07-04T19:47:33.287327+09:00 [error] Config '/proj/knot-dns/etc/knot-2317.conf' - syntax error on line 5 (current token '32').
2012-07-04T19:47:33.287980+09:00 [error] Failed to parse configuration '/proj/knot-dns/etc/knot-2317.conf'.
kohi@lars[2]%
------------------------------------------------------------
Thanks in advance.
Koh-ichi Ito
Hi all,
we have created page for Knot DNS on Google+ [1]. We will try
to use that channel for communicating short interesting stuff
from the development. You will not be bored, we promise :)
1. https://plus.google.com/u/0/111568815130451558383/posts
Feel free to join the channel and/or spread the word around.
Ondrej
--
Ondřej Surý -- Chief Science Officer
-------------------------------------------
CZ.NIC, z.s.p.o. -- Laboratoře CZ.NIC
Americka 23, 120 00 Praha 2, Czech Republic
mailto:ondrej.sury@nic.cz http://nic.cz/
tel:+420.222745110 fax:+420.222745112
-------------------------------------------
Hi,
another bugfix release of Knot DNS is out. This one corrects behaviour
with wildcard CNAMEs, when DNSSEC is requested (some NSECs/NSEC3s were
missing) and fixes some potential problems from incorrect use of RCU
synchronisation.
The sources are available here:
http://public.nic.cz/files/knot-dns/knot-1.0.6.tar.gz
GPG signature: http://public.nic.cz/files/knot-dns/knot-1.0.6.tar.gz.asc
Packages available at www.knot-dns.cz will be updated soon as well.
We are planning another release soon, with a lot of improvements and
small fixes in answers. Also we found out that the IXFR is still quite
slow with too many changes (more than 50 000 RRs changed) and are
working on that as well.
Regards,
Lubos
--
Ľuboš 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.czhttp://www.nic.cz
-------------------------------------------
Please consider the environment before printing this email.
Join the campaign at http://thinkBeforePrinting.org
