Open yordis opened 1 year ago
Best practice is to get a registered domain and then use a subdomain for AD. You can get some very cheap domain names for something like $8 a year.
The AD domain should then look like:
ad.domain.com or internal.domain.com
Using .local has been discouraged since Server 2003 (with the exception of Small Business Server).
Having a registered domain name guarantees unique names.
.local can interfere with apple services like Bonjour which uses .local on a local subnet without DNS lookup.
I also have read that it can interfere with autodiscovery in AD.
Sure, you can probably get by using .local... But if you want to do it right, .local is a bad idea.
Use .localhost for TLD in local developmen
Context
Bikeshedding about TLD for local development
Resolution
.localhost
for local development DNS resolutionLinks