Unbound local zone limit?

Unbound
1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi there,

does anybody know, is Unbound has local zone limit?

Question:

If I include this file or add lines to unbound.conf:

local-zone: "vortex.data.microsoft.com" redirect
local-data: "vortex.data.microsoft.com A 127.0.0.1"
local-zone: "vortex-win.data.microsoft.com" redirect
local-data: "vortex-win.data.microsoft.com A 127.0.0.1"
local-zone: "telecommand.telemetry.microsoft.com" redirect
local-data: "telecommand.telemetry.microsoft.com A 127.0.0.1"
local-zone: "telecommand.telemetry.microsoft.com.nsatc.net" redirect
local-data: "telecommand.telemetry.microsoft.com.nsatc.net A 127.0.0.1"
local-zone: "oca.telemetry.microsoft.com" redirect
local-data: "oca.telemetry.microsoft.com A 127.0.0.1"
local-zone: "oca.telemetry.microsoft.com.nsatc.net" redirect
local-data: "oca.telemetry.microsoft.com.nsatc.net A 127.0.0.1"
local-zone: "sqm.telemetry.microsoft.com" redirect
local-data: "sqm.telemetry.microsoft.com A 127.0.0.1"
local-zone: "sqm.telemetry.microsoft.com.nsatc.net" redirect
local-data: "sqm.telemetry.microsoft.com.nsatc.net A 127.0.0.1"
local-zone: "watson.telemetry.microsoft.com" redirect
local-data: "watson.telemetry.microsoft.com A 127.0.0.1"
local-zone: "watson.telemetry.microsoft.com.nsatc.net" redirect
local-data: "watson.telemetry.microsoft.com.nsatc.net A 127.0.0.1"
local-zone: "redir.metaservices.microsoft.com" redirect
local-data: "redir.metaservices.microsoft.com A 127.0.0.1"
local-zone: "choice.microsoft.com" redirect
local-data: "choice.microsoft.com A 127.0.0.1"
local-zone: "choice.microsoft.com.nsatc.net" redirect
local-data: "choice.microsoft.com.nsatc.net A 127.0.0.1"
local-zone: "df.telemetry.microsoft.com" redirect
local-data: "df.telemetry.microsoft.com A 127.0.0.1"
local-zone: "reports.wes.df.telemetry.microsoft.com" redirect
local-data: "reports.wes.df.telemetry.microsoft.com A 127.0.0.1"
local-zone: "wes.df.telemetry.microsoft.com" redirect
local-data: "wes.df.telemetry.microsoft.com A 127.0.0.1"
local-zone: "services.wes.df.telemetry.microsoft.com" redirect
local-data: "services.wes.df.telemetry.microsoft.com A 127.0.0.1"
local-zone: "sqm.df.telemetry.microsoft.com" redirect
local-data: "sqm.df.telemetry.microsoft.com A 127.0.0.1"
local-zone: "telemetry.microsoft.com" redirect
local-data: "telemetry.microsoft.com A 127.0.0.1"
local-zone: "watson.ppe.telemetry.microsoft.com" redirect
local-data: "watson.ppe.telemetry.microsoft.com A 127.0.0.1"
local-zone: "telemetry.appex.bing.net" redirect
local-data: "telemetry.appex.bing.net A 127.0.0.1"
local-zone: "telemetry.urs.microsoft.com" redirect
local-data: "telemetry.urs.microsoft.com A 127.0.0.1"
local-zone: "telemetry.appex.bing.net:443" redirect
local-data: "telemetry.appex.bing.net:443 A 127.0.0.1"
local-zone: "settings-sandbox.data.microsoft.com" redirect
local-data: "settings-sandbox.data.microsoft.com A 127.0.0.1"
local-zone: "vortex-sandbox.data.microsoft.com" redirect
local-data: "vortex-sandbox.data.microsoft.com A 127.0.0.1"
local-zone: "survey.watson.microsoft.com" redirect
local-data: "survey.watson.microsoft.com A 127.0.0.1"
local-zone: "watson.live.com" redirect
local-data: "watson.live.com A 127.0.0.1"
local-zone: "watson.microsoft.com" redirect
local-data: "watson.microsoft.com A 127.0.0.1"
local-zone: "statsfe2.ws.microsoft.com" redirect
local-data: "statsfe2.ws.microsoft.com A 127.0.0.1"
local-zone: "corpext.msitadfs.glbdns2.microsoft.com" redirect
local-data: "corpext.msitadfs.glbdns2.microsoft.com A 127.0.0.1"
local-zone: "compatexchange.cloudapp.net" redirect
local-data: "compatexchange.cloudapp.net A 127.0.0.1"
local-zone: "cs1.wpc.v0cdn.net" redirect
local-data: "cs1.wpc.v0cdn.net A 127.0.0.1"
local-zone: "a-0001.a-msedge.net" redirect
local-data: "a-0001.a-msedge.net A 127.0.0.1"
local-zone: "statsfe2.update.microsoft.com.akadns.net" redirect
local-data: "statsfe2.update.microsoft.com.akadns.net A 127.0.0.1"
local-zone: "sls.update.microsoft.com.akadns.net" redirect
local-data: "sls.update.microsoft.com.akadns.net A 127.0.0.1"
local-zone: "fe2.update.microsoft.com.akadns.net" redirect
local-data: "fe2.update.microsoft.com.akadns.net A 127.0.0.1"
local-zone: "65.55.108.23" redirect
local-data: "65.55.108.23 A 127.0.0.1"
local-zone: "65.39.117.230" redirect
local-data: "65.39.117.230 A 127.0.0.1"
local-zone: "23.218.212.69" redirect
local-data: "23.218.212.69 A 127.0.0.1"
local-zone: "134.170.30.202" redirect
local-data: "134.170.30.202 A 127.0.0.1"
local-zone: "137.116.81.24" redirect
local-data: "137.116.81.24 A 127.0.0.1"
local-zone: "diagnostics.support.microsoft.com" redirect
local-data: "diagnostics.support.microsoft.com A 127.0.0.1"
local-zone: "corp.sts.microsoft.com" redirect
local-data: "corp.sts.microsoft.com A 127.0.0.1"
local-zone: "statsfe1.ws.microsoft.com" redirect
local-data: "statsfe1.ws.microsoft.com A 127.0.0.1"
local-zone: "pre.footprintpredict.com" redirect
local-data: "pre.footprintpredict.com A 127.0.0.1"
local-zone: "204.79.197.200" redirect
local-data: "204.79.197.200 A 127.0.0.1"
local-zone: "23.218.212.69" redirect
local-data: "23.218.212.69 A 127.0.0.1"
local-zone: "i1.services.social.microsoft.com" redirect
local-data: "i1.services.social.microsoft.com A 127.0.0.1"
local-zone: "i1.services.social.microsoft.com.nsatc.net" redirect
local-data: "i1.services.social.microsoft.com.nsatc.net A 127.0.0.1"
local-zone: "feedback.windows.com" redirect
local-data: "feedback.windows.com A 127.0.0.1"
local-zone: "feedback.microsoft-hohm.com" redirect
local-data: "feedback.microsoft-hohm.com A 127.0.0.1"
local-zone: "feedback.search.microsoft.com" redirect
local-data: "feedback.search.microsoft.com A 127.0.0.1"

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?

WBR, Yuri

2

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi there,

does anybody know, is Unbound has local zone limit?

Question:

If I include this file or add lines to unbound.conf:

local-zone: "vortex.data.microsoft.com" redirect
local-data: "vortex.data.microsoft.com A 127.0.0.1"
local-zone: "vortex-win.data.microsoft.com" redirect
local-data: "vortex-win.data.microsoft.com A 127.0.0.1"
local-zone: "telecommand.telemetry.microsoft.com" redirect
local-data: "telecommand.telemetry.microsoft.com A 127.0.0.1"
local-zone: "telecommand.telemetry.microsoft.com.nsatc.net" redirect
local-data: "telecommand.telemetry.microsoft.com.nsatc.net A 127.0.0.1"
local-zone: "oca.telemetry.microsoft.com" redirect
local-data: "oca.telemetry.microsoft.com A 127.0.0.1"
local-zone: "oca.telemetry.microsoft.com.nsatc.net" redirect
local-data: "oca.telemetry.microsoft.com.nsatc.net A 127.0.0.1"
local-zone: "sqm.telemetry.microsoft.com" redirect
local-data: "sqm.telemetry.microsoft.com A 127.0.0.1"
local-zone: "sqm.telemetry.microsoft.com.nsatc.net" redirect
local-data: "sqm.telemetry.microsoft.com.nsatc.net A 127.0.0.1"
local-zone: "watson.telemetry.microsoft.com" redirect
local-data: "watson.telemetry.microsoft.com A 127.0.0.1"
local-zone: "watson.telemetry.microsoft.com.nsatc.net" redirect
local-data: "watson.telemetry.microsoft.com.nsatc.net A 127.0.0.1"
local-zone: "redir.metaservices.microsoft.com" redirect
local-data: "redir.metaservices.microsoft.com A 127.0.0.1"
local-zone: "choice.microsoft.com" redirect
local-data: "choice.microsoft.com A 127.0.0.1"
local-zone: "choice.microsoft.com.nsatc.net" redirect
local-data: "choice.microsoft.com.nsatc.net A 127.0.0.1"
local-zone: "df.telemetry.microsoft.com" redirect
local-data: "df.telemetry.microsoft.com A 127.0.0.1"
local-zone: "reports.wes.df.telemetry.microsoft.com" redirect
local-data: "reports.wes.df.telemetry.microsoft.com A 127.0.0.1"
local-zone: "wes.df.telemetry.microsoft.com" redirect
local-data: "wes.df.telemetry.microsoft.com A 127.0.0.1"
local-zone: "services.wes.df.telemetry.microsoft.com" redirect
local-data: "services.wes.df.telemetry.microsoft.com A 127.0.0.1"
local-zone: "sqm.df.telemetry.microsoft.com" redirect
local-data: "sqm.df.telemetry.microsoft.com A 127.0.0.1"
local-zone: "telemetry.microsoft.com" redirect
local-data: "telemetry.microsoft.com A 127.0.0.1"
local-zone: "watson.ppe.telemetry.microsoft.com" redirect
local-data: "watson.ppe.telemetry.microsoft.com A 127.0.0.1"
local-zone: "telemetry.appex.bing.net" redirect
local-data: "telemetry.appex.bing.net A 127.0.0.1"
local-zone: "telemetry.urs.microsoft.com" redirect
local-data: "telemetry.urs.microsoft.com A 127.0.0.1"
local-zone: "telemetry.appex.bing.net:443" redirect
local-data: "telemetry.appex.bing.net:443 A 127.0.0.1"
local-zone: "settings-sandbox.data.microsoft.com" redirect
local-data: "settings-sandbox.data.microsoft.com A 127.0.0.1"
local-zone: "vortex-sandbox.data.microsoft.com" redirect
local-data: "vortex-sandbox.data.microsoft.com A 127.0.0.1"
local-zone: "survey.watson.microsoft.com" redirect
local-data: "survey.watson.microsoft.com A 127.0.0.1"
local-zone: "watson.live.com" redirect
local-data: "watson.live.com A 127.0.0.1"
local-zone: "watson.microsoft.com" redirect
local-data: "watson.microsoft.com A 127.0.0.1"
local-zone: "statsfe2.ws.microsoft.com" redirect
local-data: "statsfe2.ws.microsoft.com A 127.0.0.1"
local-zone: "corpext.msitadfs.glbdns2.microsoft.com" redirect
local-data: "corpext.msitadfs.glbdns2.microsoft.com A 127.0.0.1"
local-zone: "compatexchange.cloudapp.net" redirect
local-data: "compatexchange.cloudapp.net A 127.0.0.1"
local-zone: "cs1.wpc.v0cdn.net" redirect
local-data: "cs1.wpc.v0cdn.net A 127.0.0.1"
local-zone: "a-0001.a-msedge.net" redirect
local-data: "a-0001.a-msedge.net A 127.0.0.1"
local-zone: "statsfe2.update.microsoft.com.akadns.net" redirect
local-data: "statsfe2.update.microsoft.com.akadns.net A 127.0.0.1"
local-zone: "sls.update.microsoft.com.akadns.net" redirect
local-data: "sls.update.microsoft.com.akadns.net A 127.0.0.1"
local-zone: "fe2.update.microsoft.com.akadns.net" redirect
local-data: "fe2.update.microsoft.com.akadns.net A 127.0.0.1"
local-zone: "65.55.108.23" redirect
local-data: "65.55.108.23 A 127.0.0.1"
local-zone: "65.39.117.230" redirect
local-data: "65.39.117.230 A 127.0.0.1"
local-zone: "23.218.212.69" redirect
local-data: "23.218.212.69 A 127.0.0.1"
local-zone: "134.170.30.202" redirect
local-data: "134.170.30.202 A 127.0.0.1"
local-zone: "137.116.81.24" redirect
local-data: "137.116.81.24 A 127.0.0.1"
local-zone: "diagnostics.support.microsoft.com" redirect
local-data: "diagnostics.support.microsoft.com A 127.0.0.1"
local-zone: "corp.sts.microsoft.com" redirect
local-data: "corp.sts.microsoft.com A 127.0.0.1"
local-zone: "statsfe1.ws.microsoft.com" redirect
local-data: "statsfe1.ws.microsoft.com A 127.0.0.1"
local-zone: "pre.footprintpredict.com" redirect
local-data: "pre.footprintpredict.com A 127.0.0.1"
local-zone: "204.79.197.200" redirect
local-data: "204.79.197.200 A 127.0.0.1"
local-zone: "23.218.212.69" redirect
local-data: "23.218.212.69 A 127.0.0.1"
local-zone: "i1.services.social.microsoft.com" redirect
local-data: "i1.services.social.microsoft.com A 127.0.0.1"
local-zone: "i1.services.social.microsoft.com.nsatc.net" redirect
local-data: "i1.services.social.microsoft.com.nsatc.net A 127.0.0.1"
local-zone: "feedback.windows.com" redirect
local-data: "feedback.windows.com A 127.0.0.1"
local-zone: "feedback.microsoft-hohm.com" redirect
local-data: "feedback.microsoft-hohm.com A 127.0.0.1"
local-zone: "feedback.search.microsoft.com" redirect
local-data: "feedback.search.microsoft.com A 127.0.0.1"

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?

WBR, Yuri

3

Hi Yuri,

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

4

OMG. My mistake :slight_smile:

Thank you, Wouter!

03.10.15 16:00, unbound-users-request@unbound.net пишет: