On Tue, Apr 15, 2025 at 10:38:42AM +0200, Benno Overeinder wrote: > All, > > At IETF 122, there appeared to be some agreement to adopt this work within > DNSOP. >
I support adoption of this on the basis that I think that guidance is needed for (at least) operators. .internal isn't special in most ways; ICANN have reserved it for private/internal use much like RFC1918 address space is reserved for private/internal use. .internal should not get any special processing by DNS servers any more than 10.0.0.0/8 gets any special handling by routers or firewalls. I wouldn't want to find that, for example, records within it are not cached or some other unexpected handling by auth or recursive resolvers. I'd want to be able to create a zone for it and/or delegate from it within a private network of DNS servers, and have all the usual recursion and/or forwards and/or caching work. Some guidance to operators that says "suggested practice for use of this TLD within your network is A, B and C, noting that this TLD will not work on the internet". Best wishes, Karl -- Karl Dyson _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
