On 6/23/14, 4:37 PM, "Phil Regnauld" <[email protected]> wrote:
>Doug Barton (dougb) writes: >> > >> >* Registered domain name (e.g., somecompany.com) >> >* Fantasy tld (e.g., .mycorp) >> >* .local (collides zeroconf/mDNS) >> >> You missed a fourth option, which is generally my preference. Use a >> subdomain of an existing registered domain. I generally like >> is.example.com, where "IS" stands for Internal Systems, but feel >> free to be creative there. Generally a good idea to keep it short >> though. > > +1. Microsoft has made this their recommended way as well (after > years of getting lambasted for suggesting .local and .corp). > > For Jim suggesting split DNS: please, no. It's troubleshooting > hell trying to figure out what the user on the phone is seeing, > etc. This has been my experience as well. We see support issues from across our organization because of split DNS. Even senior technical folks get confused occasionally. With the blurring of network perimeters, it is becoming increasingly difficult to know what view end users have of the namespace. To all, thank you for the numerous thoughtful responses. I will post a summary to the list tomorrow (Tuesday). Thanks, Kelly ******* CONFIDENTIALITY NOTICE ******* This e-mail message and all attachments transmitted with it may contain legally privileged and confidential information intended solely for the use of the addressee. If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message from your system. Thank you. _______________________________________________ dns-operations mailing list [email protected] https://lists.dns-oarc.net/mailman/listinfo/dns-operations dns-jobs mailing list https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
