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
smime.p7s
Description: S/MIME Cryptographic Signature
-- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
