-1

I know using example.com would cause a conflict, but what about ad.example.com, corp.example.com or internal.example.com? I have a web .com domain. Will need to remote in and/or VPN etc.

I am being told that ONLY .local should be used and nothing else. I am not so certain about that.

Something about self-signed certificates? And when the server is accessed from the public it will fail? I don't know much about certificates and need to read up on it.

Rex
  • 7,815
  • 3
  • 28
  • 44
timd1971
  • 287
  • 1
  • 5
  • 15
  • 1
    Whomever is advising you is wrong. Use an unused subdomain of your public domain. Don't use any made up TLD. Don't use .local. Don't use a subdomain of a domain that you do not own. `ad.domain.com`, where `domain.com` is your public domain name, is perfectly acceptable – joeqwerty Jul 24 '15 at 18:05
  • From your experience and great posts here, I think I am going to follow your advice and not the "other"s advice I been given after I already ahd my mind set on no .local. I do own my .com that I want to use and will use what you suggest, ad.domain.com. I cannot check this comment as an ANSWER, but both yours and Rex's I consider good answers. Thank you Joe & Rex. – timd1971 Jul 24 '15 at 18:18

1 Answers1

2

.local should definitely NOT be used anymore. Specifically regarding certificates, the public Cert Authorities will no longer renew or issue new certs for .local domains after Nov 1, 2015.

Rex
  • 7,815
  • 3
  • 28
  • 44