[nsd-users] NSD Problems (Reverse Direction)

[Otto Moerbeek]

On Thu, Jul 09, 2020 at 01:19:47AM +0000, Ken.Hendrickson at L3Harris.com wrote:

> What am I doing wrong???  I'm using nsd on OpenBSD.
> 
> 
> 
> 
> 
> nsd works only in the forward direction: from a name to an IP address.
> I'm using my named zone files from way back.
> nsd-checkzone says that the zone files are good.
> Here are the startup logs for nsd:
> ----------------------------------------------------------------------
> Jul  8 20:30:20 Soekris2 nsd[85856]: nsd starting (NSD 4.2.4)
> Jul  8 20:30:21 Soekris2 nsd[78426]: zone 10.24.172.in-addr.arpa read with success
> Jul  8 20:30:21 Soekris2 nsd[78426]: zone 20.24.172.in-addr.arpa read with success
> Jul  8 20:30:21 Soekris2 nsd[78426]: zone 30.24.172.in-addr.arpa read with success
> Jul  8 20:30:21 Soekris2 nsd[78426]: zone 2.168.192.in-addr.arpa read with success
> Jul  8 20:30:21 Soekris2 nsd[78426]: zone Foo.Bar read with success
> Jul  8 20:30:21 Soekris2 nsd[78426]: nsd started (NSD 4.2.4), pid 71631
> ----------------------------------------------------------------------
> 
> 
> 
> 
> 
> nsd works in the forward direction (not shown).
> nsd fails in the reverse direction:
> ----------------------------------------------------------------------
> 117 Soekris2# nslookup
> > server 127.0.0.1 
> Default server: 127.0.0.1
> Address: 127.0.0.1#53
> > set port 53053
             ^^^^^
> > 172.24.20.1
> Server:		127.0.0.1
> Address:	127.0.0.1#53
                          ^^
You're not asking the server you expect.

Dunno why, never use it. Maybe has to do with the recent cleanup os
nslookup and friends. I prefer dig.

	-Otto

> 
> ** server can't find 1.20.24.172.in-addr.arpa: NXDOMAIN
> ----------------------------------------------------------------------
> 
> 
> 
> 
> 
> Here is an example reverse-direction file: db.20.24.172.in-addr.arpa
> ----------------------------------------------------------------------
> ;
> ; BIND reverse data file for 20.24.172.in-arpa.arpa.
> ;
> ; Origin added to names not ending in a dot:    20.24.172.in-addr.arpa.
> 
> $TTL    3h
> 
> @ IN SOA Soekris1.Foo.Bar. root.Soekris1.Foo.Bar. (
>                      2020070501         ; Serial
>                           10800         ; Refresh               3 hours
>                            3600         ; Retry                 1 hour
>                          604800         ; Expire                1 week
>                            3600 )       ; Negative Caching      1 hour
> 
> ; Name Servers
> 
>         ;IN     NS      Cherub.Foo.Bar.
>         ;IN     NS      Tux.Foo.Bar.
>         IN      NS      Soekris1.Foo.Bar.
>         IN      NS      Soekris2.Foo.Bar.
>         IN      NS      PcEngines1.Foo.Bar.
>         IN      NS      PcEngines2.Foo.Bar.
> 
> ; Network Name
> 0       IN      PTR     Wired.20.
> 
> 1       IN      PTR     WirelessAccess.Foo.Bar.
> 2       IN      PTR     WirelessRouter.Foo.Bar.
> ----------------------------------------------------------------------
> 
> 
> 
> 
> 
> Any ideas?
> 
> Why would nsd work in the forward direction,
> but not in the reverse direction,
> if all of the zone files are good?
> 
> What is different between nsd and named?
> 
> 
>   
> 
> CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient and may contain material that is proprietary, confidential, privileged or otherwise legally protected or restricted under applicable government laws. Any review, disclosure, distributing or other use without expressed permission of the sender is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies without reading, printing, or saving.
>