Hi Mark, > On Dec 13, 2017, at 17:09, Mark Andrews <[email protected]> wrote: > > Section 7 says:
Yes, I know. I read it. > RFC 6303 has similar requirements and IANA was able to co-ordinate those > delegation. Apart from the zones originally delegated to the AS112 project, I couldn't find a zone specified in 6303 that is delegated at all, actually. Admittedly I didn't check all of them (I got bored after 0.in-addr.arpa, 127.in-addr.arpa, 2.0.192.in-addr.arpa and d.f.ip6.arpa). Here's an example: monster:~]% dig @b.in-addr-servers.arpa 0.in-addr.arpa soa +norec +dnssec ; <<>> DiG 9.11.2 <<>> @b.in-addr-servers.arpa 0.in-addr.arpa soa +norec +dnssec ; (2 servers found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 64980 ;; flags: qr aa; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags: do; udp: 4096 ;; QUESTION SECTION: ;0.in-addr.arpa. IN SOA ;; AUTHORITY SECTION: in-addr.arpa. 3600 IN NSEC 1.in-addr.arpa. NS SOA RRSIG NSEC DNSKEY in-addr.arpa. 3600 IN RRSIG NSEC 8 2 3600 20171228213500 20171208080001 51846 in-addr.arpa. D167CxX3WV8Cygq3JHJ8Ik4VUo5qGbEqxGq68vyil2QMhf9O7DjyU3sn q3S9kR+TJ7yQJPsfzy6Qqygft2Jnr0pujDspruYyKcFfx5WbO2X7pTxQ zFSjjHspZPCJ5ZVNoML/3aFYcqvBeYZWViZB8zCuyYZWF6YXtDppXukz 3GQ= in-addr.arpa. 3600 IN SOA b.in-addr-servers.arpa. nstld.iana.org. 2017102477 1800 900 604800 3600 in-addr.arpa. 3600 IN RRSIG SOA 8 2 3600 20171231104329 20171210060001 51846 in-addr.arpa. a7/wJ7RcUM9MOV3M0+0i9MUgOF4Yw6VqUIuR7ItN70CuM8qoCYGi+0/F bRiiHPeRFgFD92Shgb7pwRsM2lYh53jheWAZSOg8wOdNMaF+eiEolErv wpBuDoZM/m1mlAZ26BiN2BKDDh22AXj/76KA+pgIa+J3y2kQHYsNKEmB pvg= ;; Query time: 22 msec ;; SERVER: 2001:500:87::87#53(2001:500:87::87) ;; WHEN: Thu Dec 14 00:39:19 UTC 2017 ;; MSG SIZE rcvd: 492 [monster:~]% Joe _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
