Re: Namespace

Tech-Archive recommends: Speed Up your PC by fixing your registry

anonymous_at_discussions.microsoft.com
Date: 07/19/04 

Date: Mon, 19 Jul 2004 16:23:22 -0700

Thanks for the quick response. This is useful information.

>-----Original Message-----
>hi. there are dew pros and cons. as a start, it is
always a good practice to
>set up two different dns zones, one public and one
internal. the reason is
>to mask all of your internal address i order to prevent
their exposure.
>(expose only what you want, +, you do not need to use
real names) also, it
>will not cause confusion, causing you to put the wrong
records on the wrong
>dns servers. thired, with one namespace you cannot use
foworders between the
>two servers. foworders prevent your private dns server
searching for
>Internet Names by himself(which you don't want). and the
last thing, is you
>get much more secure enviornmet, with much lesser
chances to get hit by an
>Dns Attack like Chace poisioning or somthing simielr on
your private
>namespace. the only disadvantage of this topology, is a
little extra
>overhead in defining the dns zones, and, you will have
to add an extra email
>address to each user (this can be done simply by use of
an exchange
>recipient policy...). but this is really small money
compared to the clear
>advantages of a private and a public zone.
>
>Omer maydan
>MCSE,Security+
>
>"Clark" <anonymous@discussions.microsoft.com> wrote in
message
>news:3023201c46db4$cba3d870$a301280a@phx.gbl...
>> What are the pros and con with selcting a dot local
>> internal name space as oposed to a FQDN starting with a
>> registered name?
>>
>> 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.
>>
>> This is a reshearch issue and we are investigating all
>> resources, Microsoft, vendors and IT community.
>>
>> Any suggestion or thoughts would be GREATLY
appreciated!
>>
>> Thanks,
>>
>> Clark
>
>
>.
>

Relevant Pages

  • Re: Namespace
    ... there are dew pros and cons. ... set up two different dns zones, ... Internet Names by himself. ...
    (microsoft.public.windows.server.dns)
  • Re: Urgent! New router and big disaster
    ... Both NICs should point to his internal IP for DNS. ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... Both NICs should point to his internal IP for DNS. ... You should give your SBS a fixed external address so you can forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: How do my server 2003 (DNS) know the Internet?
    ... The Multihomed function is not for Internet access. ... has an ip of 156.40.10.10 for that network. ... It is due to a number of reasons, mainly DNS registration of both NICs, whereas you do not want that. ... It's highly recommended to single home all DCs and use a non-DC for the multihoming purposes. ...
    (microsoft.public.windows.server.dns)
  • Re: Non-domain connection problem
    ... For some reason the DNS is persistent. ... connect new PC to the internet from the non-domain network: ... In server 2000 gpoedit.msc showed them but in SBS it is different. ...
    (microsoft.public.windows.server.sbs)