Use these directives also in unbound (see the pattern and choose what you
need, like 24.172.IN-ADDR.ARPA, to cover your 172.24.* reverse.
local-zone: "168.192.IN-ADDR.ARPA" nodefault
local-zone: "16.172.IN-ADDR.ARPA" nodefault
local-zone: "17.172.IN-ADDR.ARPA" nodefault
local-zone:
Hi,
On 09/07/2020 20:44, ken.hendrick...@l3harris.com wrote:
> stub-zone:
> name: 30.24.172.in-addr.arpa.
good
> stub-addr: 127.0.0.1@53053
> stub-zone:
> name: 2.168.192.in-arpa.arpa.
I appreciate your help!
Either you solved the previous problem telling me to put $ORIGIN in my BIND
zone files,
or I had made a mistake with the 'set port=number' command in nslookup.
In either case NSD is now working properly in both directions.
But Unbound is only working correctly in the
Nope. I still don't have it working.
NSD is working in both directions.
Unbound is only working in the forward direction.
Here is proof that both Unbound and NSD are working in the forward direction:
7 Soekris2#
please disregard this. as expected, if one mentions 'typo' it is
inevitable that one will embarrass themselves profoundly. as it happens
i read the config too quickly and entirely wrongly.
On Thu, 9 Jul 2020 15:21:27 -0400, Amelia A Lewis wrote:
> On Thu, 9 Jul 2020 17:44:48 +,
On Thu, 9 Jul 2020 17:44:48 +, ken.hendrick...@l3harris.com wrote:
> name: 2.168.192.in-arpa.arpa.
^
It's a mystery, as well, why you would set up nsd (an authoritative
sever) if you're not delegating to it in the recursive/caching server.
But if
6 matches
Mail list logo
