Re: Any benefits of use a .local for internal vs. your external .com?
From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 12/22/04
- Next message: K_R: "Re: Error "the remote computer is not available" accessing worksta"
- Previous message: Roger Abell: "Re: Cached Logon"
- In reply to: Jeremy Stevens: "Any benefits of use a .local for internal vs. your external .com?"
- Next in thread: Phillip Windell: "Re: Any benefits of use a .local for internal vs. your external .com?"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 22 Dec 2004 09:24:27 -0500
Jeremy Stevens wrote:
> I am setting up a new windows domain and we have several registered
> names. Is there any benefit of using the .local for this? I am new to
> this one and we like to know any input.
>
> Thank you.
>
> Jeremy
You can use only one name internally anyway, and .local or .lan is one
option to ensure that your internal DNS never has any issues when clients
want to see resources on the real domain.com domain. If you have any Macs,
use .lan instead of .local. You can also set up your AD domain as
internal.realdomain.com as long as that doesn't exist on the Internet....
- Next message: K_R: "Re: Error "the remote computer is not available" accessing worksta"
- Previous message: Roger Abell: "Re: Cached Logon"
- In reply to: Jeremy Stevens: "Any benefits of use a .local for internal vs. your external .com?"
- Next in thread: Phillip Windell: "Re: Any benefits of use a .local for internal vs. your external .com?"
- Messages sorted by: [ date ] [ thread ]