Re: unbound resolving 10.in-addr.arpa

2023-12-14 Thread John Clendenen
Without seeing your unbound.conf, any of the following configurations may be relevant. I use nodefault in conjunction with a stub zone, but per Todd's reply, transparent may be appropriate depending on your configuration: local-zone: "10.in-addr.arpa." nodefault If DNSSEC is not configured on yo

Re: unbound resolving 10.in-addr.arpa

2023-12-14 Thread Lyndon Nerenberg (VE7TFX/VE6BBM)
Todd C. Miller writes: > local-zone: "1.1.10.in-addr.arpa." transparent That (well, a variant) was the answer. I was having a real problem wrapping my head around what 'transparent' did, so I was applying it incorrectly. Thanks for prodding me to revisit it! --lyndon

Re: unbound resolving 10.in-addr.arpa

2023-12-14 Thread Todd C . Miller
On Thu, 14 Dec 2023 12:05:24 -0800, "Lyndon Nerenberg (VE7TFX/VE6BBM)" wrote: > I am trying to get unbound to serve up reverse DNS for our internal > 1918 address space. I have been going hammer and tongs at unbound.conf > to try to make it forward requests for '*.10.in-addr.arpa.' to our > two i

unbound resolving 10.in-addr.arpa

2023-12-14 Thread Lyndon Nerenberg (VE7TFX/VE6BBM)
I am at Witt's End. I am trying to get unbound to serve up reverse DNS for our internal 1918 address space. I have been going hammer and tongs at unbound.conf to try to make it forward requests for '*.10.in-addr.arpa.' to our two internal nameservers that are authoritative for the 10.in-addr.arpa