On 11/6/22 6:39 AM, Matus UHLAR - fantomas wrote:
3. allow your servers to to fetch 66.136.193.in-addr.arpa.
On 06.11.22 20:05, Grant Taylor via bind-users wrote:
Is this 3rd step documented somewhere?
I searched for it in RFC 2317 but didn't find it. Maybe I over looked it.
This step is not necessary for classless reverse DNS delegation.
This step is however necessary for OP's DNS server being able to reverse
resolve its own IP range, when its connectivity is down (this the OP's
question), because OP's clients will try to resolve names in
66.136.193.in-addr.arpa.
alternatively they can choose to 0/28.66.136.193.in-addr.arpa. or
0-15.66.136.193.in-addr.arpa. instead of
0-28.66.136.193.in-addr.arpa.
N.B. I've had some problems with the forward slash character "/" in
domain names multiple times in the past. I'd stick with the hyphen
"-" for compatibility.
I've had no problem with that one in the past.
TMTOWTDI
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
If Barbie is so popular, why do you have to buy her friends?
--
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
