I have run Unbound for rDNS use on a older server for a long time. I recently went from FreeBSD 13.3 to FreeBSD 14.0. The server has 3 Intel NIC cards with 2 ports each. 3 outgoing-interface, 3 interface. While all 6 ports worked in every way I could test, they did not work correctly on Unbound. Only 1 port on each card was working for DNS.
I am not savvy enough to really drill into what was going on fully.
This was true with a fresh install of FreeBSD 14.0 and a default config of Unbound.
Moving back to FreeBSD 13.3 resolved the issue.
Hard for me to understand how the dual NICs worked ok for everything except Unbound. I tested Apache thru them, FTP, SSH and ping. These all worked fine. Unbound, not so much. VERY odd.. Maybe its just my old server hardware and something in NIC drivers..
Hi,
just to understand your problem:
do you have 6 different IPs? is unbound listening on every IP?
netstat -na | grep ^udp | grep \.53
Thank you
I am moved back to 13.3 now. This was with Unbound 1.20 and 1.19. I tried both. 1.19 was pkg install and 1.20 was compiled.
But same config.
interface: 10\.1\.10\.1
interface: 10\.1\.10\.2
interface: 10\.1\.10\.3
outgoing\-interface: 10\.1\.10\.4
outgoing\-interface: 10\.1\.10\.5
outgoing\-interface: 10\.1\.10\.6
private\-address: 10\.0\.0\.0/8
forward\-tls\-upstream: yes
forward\-addr: 1\.1\.1\.2@853 \#Cloudflare
forward\-addr: 1\.0\.0\.2@853 \#Cloudflare
Again, Unless someone else sees something like this, I would ignore my issue. It was just so weird I decided to post.
I am moving on as FreeBSD 13.3 is working perfectly.. This is just a post in case someone else sees something odd running Unbound on FreeBSD 14.0..
I am not looking for possible fixes as I would have to move back to a fresh copy of 14.0 and take the server offline to test things. Once FreeBSD 13.x is EoL then I will go to 14.x..
Lots more detail below for hardware and software config.