"
Hi @Aergernis,
Were you able to solve this? I seem to have the exact same problem. My problem is lookop of alpinelinux.org, but that also seems to be linodes servers for lookup. I can also confirm I have the same problem as you with marlinfw.org also.
My setup is OPNsense 24.7.6 with Unbound - no piHole.
My workaround for now is to add a Custom Query forwarding to 8.8.8.8 for the domains in question. I could of course forward all queries to 8.8.8.8, but that defeats the purpose of using OPNsense / Unbound in the first place
Were you able to solve this? I seem to have the exact same problem. My problem is lookop of alpinelinux.org, but that also seems to be linodes servers for lookup. I can also confirm I have the same problem as you with marlinfw.org also.
Code Select
unbound-control -c unbound.conf lookup alpinelinux.org
The following name servers are used for lookup of alpinelinux.org.
;rrset 2039 5 0 2 0
alpinelinux.org. 2039 IN NS ns2.linode.com.
alpinelinux.org. 2039 IN NS ns1.linode.com.
alpinelinux.org. 2039 IN NS ns4.linode.com.
alpinelinux.org. 2039 IN NS ns3.linode.com.
alpinelinux.org. 2039 IN NS ns5.linode.com.My setup is OPNsense 24.7.6 with Unbound - no piHole.
My workaround for now is to add a Custom Query forwarding to 8.8.8.8 for the domains in question. I could of course forward all queries to 8.8.8.8, but that defeats the purpose of using OPNsense / Unbound in the first place
