Topics

My Unbound DNS service crashes when my virtual box lan is started when I'm connected to this specific network on my laptop.

10.0.100.1 ---OpnSense with Unbound --- 192.168.1.1

The 10.0.100.0 network is able to resolve the internet when I'm connected to other lans, but there is something odd about this one.  Where should I look?
Thx

Date    Message
May 19 11:54:31    unbound: [35284:0] info: mesh has 0 recursion states (0 with reply, 0 detached), 0 waiting replies, 0 recursion replies sent, 0 replies dropped, 0 states jostled out
May 19 11:54:31    unbound: [35284:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0
May 19 11:54:31    unbound: [35284:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting
May 19 11:54:31    unbound: [35284:0] info: service stopped (unbound 1.9.1).
May 19 11:54:31    unbound: [35284:0] info: resolving . DNSKEY IN
May 19 11:54:31    unbound: [35284:0] info: start of service (unbound 1.9.1).
May 19 11:54:31    unbound: [35284:0] notice: init module 1: iterator
May 19 11:54:31    unbound: [35284:0] notice: init module 0: validator
May 19 11:54:31    unbound: [35284:0] notice: Restart of unbound 1.9.1.
May 19 11:54:31    unbound: [35284:0] info: mesh has 1 recursion states (1 with reply, 0 detached), 2 waiting replies, 0 recursion replies sent, 0 replies dropped, 0 states jostled out
May 19 11:54:31    unbound: [35284:0] info: server stats for thread 0: requestlist max 1 avg 1 exceeded 0 jostled 0
May 19 11:54:31    unbound: [35284:0] info: server stats for thread 0: 2 queries, 0 answers from cache, 2 recursions, 0 prefetch, 0 rejected by ip ratelimiting
May 19 11:54:31    unbound: [35284:0] info: service stopped (unbound 1.9.1).
May 19 11:54:15    unbound: [35284:0] info: resolving 0.opnsense.pool.ntp.org. AAAA IN
May 19 11:54:02    unbound: [35284:0] info: control cmd: list_local_data
May 19 11:54:02    unbound: [35284:0] info: resolving . DNSKEY IN
May 19 11:54:02    unbound: [35284:0] info: start of service (unbound 1.9.1).

Hi. I have a small lab setup on a laptop.  I have OPNsense 19.1 as my router/firewall in a Virtual Box VM running Unbound.  There are multiple VMs running behind it.  When I'm on my work wifi or my phone's hotspot I can browse the web from inside the LAN.  Everything works as expected.

When I connect to my home wifi, I get a WAN IP, but I'm not able to resolve any exterior addresses.  It is a Spectrum ISP.  I don't see any firewall setting blocking 53 in the home router.  Any suggestions on what I should look for?

Thanks!

Hi. I'm running the following versions: OPNsense 18.7.1_3-amd64; FreeBSD 11.1-RELEASE-p12; OpenSSL 1.0.2o 27 Mar 2018

I trying to set up a VirtualBox environment on a laptop with OPNsense and Unbound as my router and dns to provide internet access to the lan.  The VirtualBox lan-side server hosts have static ips and the VirtualBox lan-side desktops have dhcp configs.  I'm not able to reference one host from another using their hostnames.  I'm trying to avoid adding each hostname to a local /etc/hosts file. 

The hosts that use dhcp can be referenced by hostname.  The ones with static ips can not.

I tried adding the static ip hosts in /var/unbound/unbound.conf and /var/unbound/host_entries.conf in separate attempts to enable the lan hosts to resolve each other by name.  Both times, the entries were removed on reboot.  The OPNsense host data and ptr records are retained in unbound.conf.

I'm missing something.  How do I set up the configuration to operate properly?

Thanks!