[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dns-operations
Subject:    Re: [dns-operations] Additional information about the RIPE NCC reverse DNS issue
From:       Tony Finch <dot () dotat ! at>
Date:       2017-03-20 14:04:48
Message-ID: alpine.DEB.2.11.1703201355140.26686 () grey ! csi ! cam ! ac ! uk
[Download RAW message or body]

Shane Kerr <shane@time-travellers.org> wrote:
>
> DNAME could be used, but it would involve an extra lookup for
> resolvers, right?

Yes, and it would also require a change of name for the delegated zones
which I suspect would be a bigger problem in practice :-)

There's some discussion and examples of using DNAME for reverse DNS in
https://tools.ietf.org/html/draft-ietf-dnsop-rfc2317bis
(which expired mainly because I wasn't sure how to resolve the open
questions, and I lacked feedback)

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
Thames, Dover, Wight, Portland, Plymouth: West or southwest 5 to 7,
occasionally gale 8 at first. Moderate or rough. Rain at first, then showers.
Moderate or good, occasionally poor at first.
_______________________________________________
dns-operations mailing list
dns-operations@lists.dns-oarc.net
https://lists.dns-oarc.net/mailman/listinfo/dns-operations
dns-operations mailing list
https://lists.dns-oarc.net/mailman/listinfo/dns-operations
[prev in list] [next in list] [prev in thread] [next in thread]