It appears that Wessels, Duane <[email protected]> said: >In order to make progress on the glue-is-not-optional draft, we need the >working group to reach consensus on the requirement level >for sibling glue (MUST, SHOULD, or MAY). > >The only situation in which a failure to include sibling glue leads to a >resolution failure is when there is a sibling glue cyclic >dependency. e.g.: > > bar.test. 86400 IN NS ns1.foo.test. > bar.test. 86400 IN NS ns2.foo.test. > > foo.test. 86400 IN NS ns1.bar.test. > foo.test. 86400 IN NS ns2.bar.test. > >A few months back I analyzed the zone files available to me via CZDS for >sibling glue. Out of some 209,000,000 total delegations, >222 of them had only sibling NS records in a cyclic dependency as above. The >domains ADOBE.NET and OMTRDC.NET is one real-world >example.
Looks to me like they're just broken: $ dig @a.gtld-servers.net. adobe.net ns ;; QUESTION SECTION: ;adobe.net. IN NS ;; AUTHORITY SECTION: adobe.net. 172800 IN NS ns1.omtrdc.net. adobe.net. 172800 IN NS ns2.omtrdc.net. ;; ADDITIONAL SECTION: ns1.omtrdc.net. 172800 IN A 66.235.157.6 ns2.omtrdc.net. 172800 IN A 66.235.157.7 $ dig @ns1.omtrdc.net. adobe.net. ns ;; QUESTION SECTION: ;adobe.net. IN NS ;; ANSWER SECTION: adobe.net. 900 IN NS ns-1.adobe.net. adobe.net. 900 IN NS ns-2.adobe.net. ;; ADDITIONAL SECTION: ns-1.adobe.net. 900 IN A 66.235.157.6 ns-2.adobe.net. 900 IN A 66.235.157.7 (Note that they're the same servers with different names.) I'm not sure how you'd do this, but do you have any idea how many domains have NS cycles across parallel zones that don't work, e.g.: foo.tld1. IN NS ns1.bar.tld2 bar.tld2. IN NS ns2.foo.tld1. R's, John PS: My preference is still "don't do that." -- Regards, John Levine, [email protected], Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
