In your letter dated 23 Nov 2016 11:49:28 -0500 you wrote: >> What if localhost is just inserted in the root as the equivalent of >> localhost. IN A 127.0.0.1 >> localhost. IN AAAA ::1 > >Most systems I know special case a plain localhost name in the resolver or >cache. The more interesting bits are <blah>.localhost which some of us >resolve to other addresses in 127/8.
I'm not sure how having something like 'localhost. IN AAAA ::1' has any effect on resolving <blah>localhost I.e., today if you ask the root for <blah>.localhost you get something like: loans. 86400 IN NSEC locker. NS DS RRSIG NSEC loans. 86400 IN RRSIG NSEC 8 1 86400 [...] proving that localhost doesn't exist. You can add a localhost zone to your resolver, but that works only if all stub resolvers use your resolver and you can avoid client side validation. After adding localhost to the root zone, the only thing that would change is that asking the root zone for <blah>.localhost now results in localhost. 86400 IN NSEC locker. A AAAA localhost. 86400 IN RRSIG NSEC 8 1 86400 [...] Which still proves that <blah>.localhost doesn't exist. I'd say, no difference for that use case. >Putting A and AAAA records in the root is another thing that is >technically simple but would require a rule change at IANA, and I don't >think it's worth the hassle. Does the MoU between the IETF and ICANN really say no A records in the root zone? Or is there another policy document between IETF and IANA? _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
