Hi,
Can you explain a bit more what you mean by external DNS?
If you mean that it is exposed to the internet -- I would advise you not to
do that. It will give out too much information about your internal network.
If you mean it is hosted on another location -- again I would advice you
against it since this will add quit a lot of additional traffic to your
network (beside your AD and Exchange talking to DNS server there will also
be all AD clients requesting data from it. If for some reason clients can't
query DNS -- they will fail to find Active Directory server)...
You should have Active Directory DNS as close to domain controller as
possible. If you don't have good, "healthy", reliable, . DNS you will have
hard time with your Active Directory and if you have problems with AD you
will have a lot of problems with Exchange that is integrated into AD.
My best advice I can give you, set up DNS on same server that your AD server
runs on.
--
Mike
Microsoft MVP - Windows Security
"UTN" <(E-Mail Removed)> wrote in message
news:Oaqff.524711$oW2.479001@pd7tw1no...
> Hi,
> Here's my dilemma,
> I have a dedicated server being hosting by a hosting company. I've just
> install Active Directory and Exchange Server. (windows 2003 + exchange
> 2003).
> Now, because of this, the DNS entries on the DNS server (which is
> external) need to be updated. Since this extrenal DNS server does not
> allow automatic updates, I need to tell the guy who runs the DNS the
> entries I'd like to go in there... But according to him, I'm missing the
> what's inside.
>
>
> For example:
> missing entry: _ldap._tcp.domain1.domain0.com
> Heck, I thought that was the whole entry...
> What I am missing to make this entry a full one, which includes the
> "what's inside"?
>
> Am I missing the A or SVR or what hosts it goes to?
>
> Any help would be greatly appreciated.
> Thank you
> UTN
>
|