Failure using an address in unbound.conf

Unbound
1

Hi

We are using virtual/logical IPs (anycast model - multiple sites across
the country using the same logical IP) that the clients use to resolve
regardless of which site they are in (same virtual/logical IP)

When running Bind on the server, this works.

When stripping Bind off of the server (there is no iptables) and
specifying the IP in the unbound.conf I get

"Starting Unbound DNS resolver: [1282148605] unbound[13241:0] error:
can't bind socket: Cannot assign requested address

[1282148605] unbound[13241:0] fatal error: could not open ports"

When removing the Virtual from the unbound.conf and using 0.0.0.0, it
works against the physical (but does not resolve against the
logical/virtuals)

Ideas?

Bruce

Bruce Hayward, MTS Allstream Inc., (c) 204-792-9174 (p) 204-958-1983 (e)
bruce.hayward@mtsallstream.com <mailto:bruce.hayward@mtsallstream.com>

(attachments)

homecoming_with_no_top_100_email_signature.gif

2

Regressed to 1.4.5 - same thing

Bruce

Bruce Hayward, MTS Allstream Inc., (c) 204-792-9174 (p) 204-958-1983 (e)
bruce.hayward@mtsallstream.com <mailto:bruce.hayward@mtsallstream.com>

(attachments)

homecoming_with_no_top_100_email_signature.gif

3

Hi Bruce, Haw,

I do not know if this helps for you, but there is an interface option
specifically made for anycast;

interface-automatic: yes

That acts like '0.0.0.0' (and ::0) but uses (weird) socket options.
This makes it pick up new interfaces when they are created (without need
for config edits and restart) or deleted. (This option is portable to
FreeBSD, Solaris, Linux, but probably won't work on other OSes).

Best regards,
   Wouter

4

Just what the doctor order - one step closer - Thanks

Bruce

Bruce Hayward, MTS Allstream Inc., (c) 204-792-9174 (p) 204-958-1983 (e)
bruce.hayward@mtsallstream.com