On Jun 12, 2012, at 7:40 AM, Warren Kumari wrote: > Hi there all, > > So, back in (AFAIR) Taipei I proposed making AS112 instances simply be > authoritative for *everything*, and then simply delegating and undelegating > things to it as appropriate (this would make things much simpler as there > would be very little coordination needed). At the time I realized that this > would require synthesizing answers (always a bit of a controversial topic), > but it turns out that there are a number of other things that may be equally > contentious, such as (thanks to Joe for this partial list):
To be honest, it seems like almost a no-brainer good idea to me. And whats wrong about synthesizing answers? The only question I have is DNSSEC. I take it since the model is this is all bogus traffic, just have an NSEC above it saying "No DNSSEC information", but I just want to be sure that doesn't change. Stupid question on the SOA record however: why not dynamically generate an exact match SOA? So if the query is, say 121.14.34.10.in-addr.arpa. IN PTR Instead of returning 10.in-addr.arpa. 300 IN SOA prisoner.iana.org. hostmaster.root-servers.org. 2002040800 1800 900 604800 604800 (current) or . 300 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2012061200 1800 900 604800 86400 (omniscient) Why not return 121.14.34.10.in-addr.arpa. 300 IN SOA prisoner.iana.org. hostmaster.root-servers.org. 2002040800 1800 900 604800 604800 as the SOA? _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
