Re: [dns-operations] Current thinking on internal corporate/campus domain names
Summary: Thank you all very much. There were seven respondents. Here are the key points. * There is a fourth option for internal DNS, that being use of a subdomain of the corporate domain, e.g., int.mycorp.com. * Several reiterated that use of a fantasy TLD could collide with current or future TLDs. * One respondent made several great points that I would summarize as, ³Plan ahead. Factor Internet connectivity into the plan.² * .local is no longer viable, Microsoft no longer recommends it. * I received this specific, interesting suggestion: Register a domain, but delegate it to DNS servers that are not in your network and always contains a null-zone. * It is not possible to obtain SSL certs (from commercial CAs) unless the internal domain is registered. This makes .corp potentially unusable. * Most respondents agreed that a registered domain for internal DNS was the way to go. As a result of your input and related research, I¹ll be recommending the use of a registered domain for internal DNS for the project I¹m working on. Cheers, 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 dns-operations@lists.dns-oarc.net https://lists.dns-oarc.net/mailman/listinfo/dns-operations dns-jobs mailing list https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
[dns-operations] Current thinking on internal corporate/campus domain names
What is current thinking/accepted practice for internal domain names? * Registered domain name (e.g., somecompany.com) * Fantasy tld (e.g., .mycorp) * .local (collides zeroconf/mDNS) This is for use within a corporate/campus setting. In times past, I have taken the fantasy approach. However, colleagues have pointed out that the growing list of new gTLDs and branded TLDs could collide with a fantasy TLD. RFC 2606 seems to suggest using a registered domain. That¹s great except that split-brain inevitably creeps into the equation. Is this a case of choosing the ³least worst² option? 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 dns-operations@lists.dns-oarc.net https://lists.dns-oarc.net/mailman/listinfo/dns-operations dns-jobs mailing list https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
[dns-operations] Sprint DNS contact
I am a Sprint customer but I am having problems finding someone at Sprint who speaks DNS. Sprint has an SOA record in place for one of my domains that was moved to other NS long ago. If someone has a contact or if Sprint monitors this list, please get in touch. thanks, Kelly -- Kelly Setzer kelly.set...@wnco.com W:214-792-7256 C:214-287-3464 Southwest Airlines Technology Engineering *** 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 dns-operations@lists.dns-oarc.net https://lists.dns-oarc.net/mailman/listinfo/dns-operations dns-jobs mailing list https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
