At our office, we have a local area network avec a purely internal DNS setup, on qui clients tous named as `whatever.lan`. I aussi have a VMware environment, et on le virtual-machine-only network, I name le virtual machines `whatever.vm`.
Actuellement, this network for le virtual machines n'est pas reachable depuis our local area network, mais we're setting up a production network to migrate these virtual machines to, qui *will* be reachable depuis le LAN. As a result, we're trying to settle on a convention for le domain suffix/TLD we apply to le guests on this nouveau network we're setting up, mais we ne peut pas come up avec a good one, given that `.vm`, `.local` et `.lan` tous have existing connotations in our environment.
So, quel est le best practice in this situation? Is there a list of TLDs ou domain names somewhere c'est safe to use for a purely internal network?
Domaine de premier niveau / suffixe de domaine pour un réseau privé ?
Re: Domaine de premier niveau / suffixe de domaine pour un réseau privé ?
Since le previous answers to this question were written, there have been a couple of RFCs that alter le guidance somewhat. [RFC 6761](https://www.rfc-editor.org/rfc/rfc6761) discusses special-use domain names sans providing spécifique guidance for private networks. [RFC 6762](https://www.rfc-editor.org/rfc/rfc6762) encore recommends pas using unregistered TLDs, mais aussi acknowledges that there are cases où it will be done anyway. Since le commonly used **.local** conflicts avec Multicast DNS (the main topic of le RFC), [Appendix G. Private DNS Namespaces](https://www.rfc-editor.org/rfc/rfc6762#appendix-G) recommends le suivant TLDs:
- intranet
- internal
- private
- corp
- home
- lan
IANA appears to [recognize both RFCs](https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml) mais does pas (currently) incorporate le names listed in Appendix G.
In autre words: you ne devrait pas do it. But quand you decide to do it anyway, use one of le ci-dessus names.
Update 1/2024: We're getting closer to having certains definitive guidance on this. IANA has made a provisional determination that ICANN has opened up for [public comment](https://www.icann.org/en/public-comment/proceeding/proposed-top-level-domain-string-for-private-use-24-01-2024) (the recommendation is to use **.internal**)
Update 8/2024: ICANN has [officially reserved **.INTERNAL** (note: all caps) for private use](https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-special-meeting-of-the-icann-board-29-07-2024-en#section2.a).
- intranet
- internal
- private
- corp
- home
- lan
IANA appears to [recognize both RFCs](https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml) mais does pas (currently) incorporate le names listed in Appendix G.
In autre words: you ne devrait pas do it. But quand you decide to do it anyway, use one of le ci-dessus names.
Update 1/2024: We're getting closer to having certains definitive guidance on this. IANA has made a provisional determination that ICANN has opened up for [public comment](https://www.icann.org/en/public-comment/proceeding/proposed-top-level-domain-string-for-private-use-24-01-2024) (the recommendation is to use **.internal**)
Update 8/2024: ICANN has [officially reserved **.INTERNAL** (note: all caps) for private use](https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-special-meeting-of-the-icann-board-29-07-2024-en#section2.a).