Maintained by: NLnet Labs

Unbound local zone limit?

W.C.A. Wijngaards
Fri Oct 2 16:07:38 CEST 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Yuri,

On 10/02/2015 03:50 PM, Yuri Voinov via Unbound-users wrote:
> 
> Hi there,
> 
> does anybody know, is Unbound has local zone limit?

No, they are kept in a lookup structure that is similar in design to
the data structure in NSD (authoritative server).  So as big as you
want it.

> 
> Question:
> 
> If I include this file or add lines to unbound.conf: [..]
> 
> Unbound won't start. If I delete or comment out 4 rows - it
> starts.
> 
> So, does Unbound has local zone limit and what is it amount?

Well unbound prints errors on startup:
unbound[31474:0] warning: duplicate local-zone
unbound[31474:0] error: could not enter zone 23.218.212.69 redirect

And this is in there twice:
local-zone: "23.218.212.69" redirect
local-data: "23.218.212.69 A 127.0.0.1"

So comment out one pair. You could also use unbound-checkconf to find
the error.

Also, the literal IP-address "23"."218"."212"."69" as a domain name is
most likely error, maybe you wanted to list the reverse in-addr.arpa
lookup here, or maybe whatever puts that query on the wire just wants
that IP-address (or its reverse)?  Or maybe you wanted to firewall
that IP-address?

Best regards, Wouter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJWDo+qAAoJEJ9vHC1+BF+N7BkQAKfLagGN3PeBpgxORQc/2Dv4
+gp81jmhKUGHTm9IM3LXAgv/E+PnwOdld+0ysO+6r6qvMi7LPesCa1CBzSM2y+pz
p4HmCleZ0elgD28rCOZF9dhEPRu71TxdrALmhgmdrCHT0zkOhPrffkxtWJoq2Kz9
n7xWzzUd5pk/mm3cJtfxGVEkfjPrQMA8Y/qEvJFSQmWAgN4y8zL3tWjVtHmpXvAo
VZDiuLq821x5PMMoUWk2E3RuKcIx510TfsUzUYaWsTXxOp28cDD4L4Reo/nR0Dn+
XnPVstR7KDt5MfP9YkqHXtyUTvIyhl7Jki//5A2d+jF9mrCw5Pwp/1fDjVH8Oicq
cn1UIHNUCrV8XYSI42207zfyfjzMM0BR3+/sGB3uXg1svvS1KULxeP21Np9I1oc7
oK0P3Ot0ufCk6kHuzv3wInJgkCHh/iczgkayJZ8wdJFcijfVhxj1+UyegGCi5Fxq
ce2hlw4ujJewNSUX3D7ujD1YkL5yeSx02I9iXKT6mLQrljYIvchPfDPgGZGbMl7Y
ZL+cHpKUHFDbc2sWudonzzwkD41HOFc1saqo3r/cIRD+HB06xP+ZTrxgrmkW6D5n
AII6TVEdvca/LUkE9FQzbNzcB2EE3tH1EzhyHjTSwerkzHqkUeHcHNWSCjxXXt88
SdivH+CpOuXrEBRDLIHY
=tuu3
-----END PGP SIGNATURE-----