Reverse lookups not working when Internet connection failed.

[Grant Taylor]

On 11/4/22 10:54 AM, David Carvalho via bind-users wrote:
> Thanks for the replies.

You're welcome.

> My reverse zone in named.conf. My secondary dns gets it automatically 
> daily, along with the "di.ubi.pt.".

ACK

> zone "0-28.66.136.193.in-addr.arpa." IN {
>          allow-query { any; };
>          type master;
>          file "rev0.hosts";
> };

That confirms that the origin is in fact "0-28.66.136.193.in-addr.arpa." 
  (Save for any typo that I may have introduced.)

> I'll have to study more about some things you guys wrote. This is 
> getting complicated 😉

So when your system(s) try to do a reverse DNS (PTR) lookup for 
193.136.66.1, it will actually do a PTR lookup for 
1.66.136.193.in-addr.arpa. and fail because you don't have a copy of the 
66.136.193.in-addr.arpa. zone file locally.

At least my understanding is that you have a copy of your forward zone, 
and your 0-28.66.136.193.in-addr.arpa. zone.  But you don't have a copy 
of, nor access to, the intermediate 66.136.193.in-addr.arpa. zone that 
references the 0-28.66.136.193.in-addr.arpa. zone.

Does that help?

Please feel free to ask additional questions.



-- 
Grant. . . .
unix || die

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4017 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20221104/8a32cc29/attachment.bin>