Dunno what Unbound's problem is, I have a fairly straightforward setup
In Services > Unbound > Query Forwarding, I have 192.168.1.24 port 5353 enabled which is my DNS resolver.
Randomly today I could not get onto aliexpress.com, my browser said it couldn't resolve the address. I opened my terminal, and 'nslookup' also failed with SERVFAIL. However I then typed dig address.com @192.168.1.24 -p5353 and it worked INSTANTLY.
Tried dig @192.168.1.1 and it failed.
Where is the massive desynchronization going on here? Why is OPNsense and Unbound reporting SERVFAIL when it very clearly is working just fine via dig?
Unrelated to this error please use port 53053 instead of 5353 as it is the registered mdns port.
53053 is free to use.
Quote from: frozen on July 08, 2025, 04:14:36 PMDunno what Unbound's problem is, I have a fairly straightforward setup
In Services > Unbound > Query Forwarding, I have 192.168.1.24 port 5353 enabled which is my DNS resolver.
Randomly today I could not get onto aliexpress.com, my browser said it couldn't resolve the address. I opened my terminal, and 'nslookup' also failed with SERVFAIL. However I then typed dig address.com @192.168.1.24 -p5353 and it worked INSTANTLY.
Tried dig @192.168.1.1 and it failed.
Where is the massive desynchronization going on here? Why is OPNsense and Unbound reporting SERVFAIL when it very clearly is working just fine via dig?
Which OPNsense or Unbound version are you running?
I think I've run into the same problem on OPNsense 25.1.7
https://forum.opnsense.org/index.php?topic=47965.0