Re: Namespace
From: Kevin D. Goodknecht Sr. [MVP] (admin_at_nospam.WFTX.US)
Date: 07/19/04
- Next message: Jeff Westhead [MSFT]: "Re: Load zone data from Registry"
- Previous message: Omer maydan: "Re: Namespace"
- In reply to: Clark: "Namespace"
- Next in thread: anonymous_at_discussions.microsoft.com: "Re: Namespace"
- Reply: anonymous_at_discussions.microsoft.com: "Re: Namespace"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 19 Jul 2004 13:20:06 -0500
In news:3023201c46db4$cba3d870$a301280a@phx.gbl,
Clark <anonymous@discussions.microsoft.com> posted a question
Then Kevin replied below:
> What are the pros and con with selcting a dot local
> internal name space as oposed to a FQDN starting with a
> registered name?
There are not really any pros for naming the internal AD name the same as
your registered public name.
There are many cons, having the two domains the same name will cause a
conflict in resolving names in one domain that are not in the other domain.
This rears its ugly head especially when connecting by VPN, VPN clients will
see both namespaces when they are connected, and having both using the same
name will cause resolution issues.
You don't have to use company.local, you can create the internal domain as a
subdomain like corp.company.com, but in this case you would be best to
create a delegation in the company.com public zone named corp and point the
delegation to the internal name and IP of the internal DNS. Without the
delegation it could cause resolution issues for the VPN clients when
connected, this is why many will recommend using .local, by using the .local
TLD, it confuses the external DNS long enough to allow the internal DNS to
respond.
>
> Our vendor has suggested using dot local. However my
> studies indicate to always start with a registered name.
> Our network connects to the internet via firewalls. I am
> concern about a xxxx.local internal namespace and its
> implications with AD and MS Exchange 2003. Currently we
> use Exchange 5.5.
Using .local does not cause any implications with either Exchange or AD.
-- Best regards, Kevin D4 Dad Goodknecht Sr. [MVP] Hope This Helps ============================ -- When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. To respond directly to me remove the nospam. from my email. ========================================== http://www.lonestaramerica.com/ ========================================== Use Outlook Express?... Get OE_Quotefix: It will strip signature out and more http://home.in.tum.de/~jain/software/oe-quotefix/ ========================================== Keep a back up of your OE settings and folders with OEBackup: http://www.oehelp.com/OEBackup/Default.aspx ==========================================
- Next message: Jeff Westhead [MSFT]: "Re: Load zone data from Registry"
- Previous message: Omer maydan: "Re: Namespace"
- In reply to: Clark: "Namespace"
- Next in thread: anonymous_at_discussions.microsoft.com: "Re: Namespace"
- Reply: anonymous_at_discussions.microsoft.com: "Re: Namespace"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
