Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Wendo

#2
That appears to have solved it thanks!

Can you outline why this fixed it? Is radvd detecting that unbound isn't running on port 53 and so giving out system DNS servers to clients thinking there is no DNS server running on opnsense?

That's the only thing I can think of I just didn't think it was _that_ smart :)

Thanks
#3
Hi

I've got Track Interface on for my WAN interface and IPv6 has been working fine for years. After upgrading to 23.1.7 I noticed that radvd (at least I think it it's radvd doing it) appears to be advertising Cloudflare and Google IPv6 DNS servers to the LAN clients, as well as the opnsense server itself. However after rolling back it's happening on my previous version of 21.1.3 as well so it's probably been going on for a while and I've just never noticed.

What this means is my internal DNS resolution isn't working anymore. I've also got AdGuardHome installed and running on port 53 but forwarding local queries to Unbound on 5353. AdGuardHome's DHCP is disabled so I don't _believe_ that's involved.

Logs don't appear to show much but then radvd is seemingly "Automatic" and so doesn't have any exposed config options but it's config file doesn't have these DNS servers in it. They are however specified under System -> Settings -> General -> DNS Servers.

How do I stop external DNS server being advertised to my LAN clients?

Thanks

#4
Ok, so no idea what was going on. I poked around with a couple of things (one of which was I was using the wrong config file when running it from command line. Then started getting can't bind, port in use even though it wasn't running (and neither was dnsmasq) and just said screw it and restarted (I'd done that before).

Anyway, after the restart it came up just fine *shrug*
#5
I just upgraded to 21.7.1 and Unbound now won't start from the GUI. However, going to the shell and running

unbound -c /var/unbound/unbound.conf

make it start no problem. There is nothing in the logs indicating any sort of issue on both the failed starts and the starts from the command line.

Can anyone point me in the right direction here? Even putting a -d on the command line doesn't show me any errors on start (probably because it starts successfully).

What command line does opnsense actually use to start Unbound?

Thanks