BIND won't start, "creating IPv4 interface" failure.

[senseivita]

I use BIND as some sort of DNS router between AD domain controllers and in-box Unbound, both listen on :53. The firewall has two interfaces; Unbound works exclusively on one of them, BIND doesn't have the option to choose interface but it set to use the addresses from the other. It had been working great for a long time until I had to change the IPv6 prefix.

That is the only thing different since it stopped working, at least. No other changes have been made. The logs are very... not really useful. The addresses are available, one of each family to each resolver/nameserver, and they are all responding, I'm testing from another subnet; ruling out gateway issues in the process. The "firewall" is not really a firewall, it's in router-only mode, filtering+NAT off.

I composed a little screenshot collage to best illustrate things — you might need to pan around on a laptop display.

Here's the link in case there are issues showing it: https://i.imgur.com/jcyCsUv.png


Any ideas what's wrong?

[senseivita]

I found it!

I SSHed in the router and looked for the BIND configuration files. When I found it, right after I opened it I noticed the error; the IPv6 query source still had the old prefix so naturally it didn't match. The logs specifically mention IPv4 addressing so it kind of threw me off. After I changed it, it immediately came back online!

Thanks anyway.