automatic reverse and forwarding zones

[Mark Andrews]

I tried back in 2013 to get the IETF to standardise delegating the reverse
tree when prefix delegations happen.

https://www.ietf.org/archive/id/draft-andrews-dnsop-pd-reverse-02.txt

named already supports updating PTR records based on the IP address of the
TCP connection making the UPDATE request.  SLACC hosts can update their own
PTR records if you configure the nameserver to allow it.  See update-policy
tcp-self.

Mark

> On 28 Oct 2022, at 14:42, Paul Ebersman <list-bind-users at dragon.net> wrote:
> 
> grant> I'd be interested in learning what other things /require/ or are
> grant> at least predicated on having PTR records for IPs.
> 
> Been a few years since I last delved but was appalled at some of the
> pointless uses of rev-ptrs. NYT used to require it to let you connect to
> their website, as one such totally pointless use.
> 
> Reality is that the only way to find out is see if users scream or do
> PTRs for all your addrs. For v6, on the fly generation is less broken
> than trying to depend on DHCPv6 server dynamic DNS updates (doesn't help
> for SLAAC). Someone has already mentioned that knot supports this.
> 
> On the plus side, most idiots checking for rev-ptr only care if they get
> an answer. Unlike SMTP, where MTAs might check if forward and reverse
> match, as long as they get an answer, they go away fat, dumb and happy.
> -- 
> 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 at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka at isc.org