FreeBSD 14.0 headache -- I am a noob

[Chris]

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 at 853   #Cloudflare
     forward-addr: 1.0.0.2 at 853   #Cloudflare
__

I am now running Forked operation, you see that in the netstat.. IE 
./configure --without-pthreads --without-solaris-threads  But I tried 
unforked and forked and they both did the same thing..

root at xymox:~ # netstat -na | grep ^udp | grep \.53
udp4       0      0 10.1.10.3.53           *.*
udp4       0      0 10.1.10.2.53           *.*
udp4       0      0 10.1.10.1.53           *.*
udp4       0      0 10.1.10.3.53           *.*
udp4       0      0 10.1.10.2.53           *.*
udp4       0      0 10.1.10.1.53           *.*
udp4       0      0 10.1.10.3.53           *.*
udp4       0      0 10.1.10.2.53           *.*
udp4       0      0 10.1.10.1.53           *.*
udp4       0      0 10.1.10.3.53           *.*
udp4       0      0 10.1.10.2.53           *.*
udp4       0      0 10.1.10.1.53           *.*
udp4       0      0 10.1.10.3.53           *.*
udp4       0      0 10.1.10.2.53           *.*
udp4       0      0 10.1.10.1.53           *.*
udp4       0      0 10.1.10.3.53           *.*
udp4       0      0 10.1.10.2.53           *.*
udp4       0      0 10.1.10.1.53           *.*

ifconfig_em0="inet 10.1.10.1 netmask 255.0.0.0"
ifconfig_em1="inet 10.1.10.2 netmask 255.0.0.0"
ifconfig_em2="inet 10.1.10.3 netmask 255.0.0.0"
ifconfig_em3="inet 10.1.10.4 netmask 255.0.0.0"
ifconfig_em4="inet 10.1.1.7 netmask 255.0.0.0"
ifconfig_em5="inet 10.1.10.5 netmask 255.0.0.0"
ifconfig_em6="inet 10.1.10.6 netmask 255.0.0.0"


VERY weird... The bottom port on each NIC would not respond to DNS query 
even tho they would show up in a netstat like above. This affected the 
outgoing-interface and interface. I moved the IPs around on the NICs via 
rc.conf and the bottom port was always dead. VERY odd.. I could always 
pull web pages via apache, ftp via proftpd and ping the ports that were 
dead for Unbound. This behavior seems impossible to me. Unbound does not 
get that deep into the devices I dont think. So this still seems 
impossible to me. Yet fresh loading 13.3 VS a fresh load 14.0,, 13.3 
worked fine and 14.0 did not using the same config files.

Don't spend any mental time on this. It pretty much fried my brain 
figuring out it was the OS upgrade. It was SO unlikely to be the OS 
upgrade as the ports worked for everything else, I did not initially 
consider it. I should know better then to use any software that has a .0 
version. Always wait for at least .1 hahaha..

Unless someone else sees something like this, I would ignore my issue. 
It was just so weird I decided to post.

On 5/16/2024 10:42 AM, Cristiano Deana via Unbound-users wrote:
> 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
>
> Il 16/05/2024 16:06, Chris via Unbound-users ha scritto:
>> 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..
>