In the past, lots of people chose to use a dummy, unofficial TLD (top-level-domain) for their internal network, like domain.lan, domain.local of domain.internal (and also domain.internalhost)
But this can get you in serious trouble. Because these names are not supported by internet standards, the most important RFC on this is: RFC 2606 (http://tools.ietf.org/html/rfc2606 ) This RFC standard is very explicit on choosing domain names for private testing and documentation
- Option 1: Use a valid TLD (Top Level Domain, also known as routable domain) registered to your company. Some examples of this are company.ca or company.com;
- Option 2: Use a subdomain of a valid TLD that is registered to your company
- Option 3: Use non-TLD name (or non-routable domain). (But not an RFC reserved name!)
On 3 Mar 2019, at 19:08, Vivek Aggarwal via FreeIPA-users <freeipa-users@lists.fedorahosted.org> wrote:Thanks John,
It would be nice if you can elaborate bit more & share your advise on:-
i) Whats wrong in the current hostname convention as still i dont have clear understanding what is that which is causing a problem in the current setup? .. any links/thoughts which can explain this will be of great help .
ii) Is ".local" is a problem or can i use any other TLD like ".int" ?
iii) Thirdly what is the recommendation for naming Hostname FQDN , does it shouldnot have multiple sub domains ??
Please bear with my questions in case these look bit naive. Thanks a lot for sparing time in answering my concerns.
_______________________________________________
FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org
To unsubscribe send an email to freeipa-users-leave@lists.fedorahosted.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedorahosted.org/archives/list/freeipa-users@lists.fedorahosted.org