Reverse lookups not working when Internet connection failed.
Cuttler, Brian R (HEALTH)
brian.cuttler at health.ny.gov
Fri Nov 4 18:09:07 UTC 2022
My pointer zones are more like
Zone "28.66.136.193.in-addr.arpa.", I've never had that leading "0-"
Is that typical? What does it do?
-----Original Message-----
From: bind-users <bind-users-bounces at lists.isc.org> On Behalf Of Grant Taylor via bind-users
Sent: Friday, November 4, 2022 1:07 PM
To: bind-users at lists.isc.org
Subject: Re: Reverse lookups not working when Internet connection failed.
ATTENTION: This email came from an external source. Do not open attachments or click on links from unknown senders or unexpected emails.
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
More information about the bind-users
mailing list