On Mon, Jun 15, 2020 at 12:59 PM Tim Wicinski <tjw.i...@gmail.com> wrote:
> On Mon, Jun 15, 2020 at 1:48 PM John Levine <jo...@taugh.com> wrote: > >> In article < >> cah1iciouffmryorewhhtbqfnnserw3rvups8pzc8cvnehys...@mail.gmail.com> you >> write: >> >E.g. use an FQDN belonging to you (or your company), so the namespace >> would >> >be example.com.zz under which your private names are instantiated. >> >> The obvious question is if an organization is willing to use >> example.com.zz, why wouldn't they use zz.example.com with split >> horizon DNS to keep that subtree on their local network? >> >> > or since domains are cheap, why not buy a new domain, and use that for the > namespace? > A wise person liked to remind me "Namespaces are architecture decisions". > tim > > Or use a combination of both approaches (separate second level domain and distinct subdomains in a shared public/private domain tree) if that fits your needs. The different aspects are for distinct needs. At work, for instance, we use a completely separate second level domain tree for many of our primary Active Directory forests and their constituent domains. We use private subdomain trees under our public second level domain for many other things. The appropriate internal/external boundaries require some thought and ongoing management, but it's not especially difficult. Scott
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
