I have absolutely no friggin idea how to do this. I realize DNS is needed for
AD and exchange server and it has to be up and running. But how?

I have randomly poked around in the DNS console and I have managed to make
the server able to resolve adresses buy inserting some actual DNS server IP
adresses into something called "route tips" or "routing tips". And suddenly
it started working.

I have a bunch of zones I have created under "Zones for normal search", but
I have no idea which does what, which are working and which I can delete. The
network I am setting up consist of a single server and five clients or so.
Why should there be more than one zone?

There was a default zone entry called "msdcs.[domain name].local", why
local? Should I rename it to "localhost". Do I even need this zone and what
does it do? What would happend if I deleted it?

Is there some way of just resetting ALL DNS settings to factory default and
then start over? If someone here will provide me with some pointers on how to
do it, that would seem like the best option.

I know how a DNS works and Ive taken courses on the subject, I am familiar
with BIND servers which I believe are all nice and fluffy. Setting it up in
windows however is a complete djungle of strangness and odd dialouges I just
dont understand. Since there is no easy to understand guide or wizard for
configuring DNS in Windows Server I would be incredibly happy and greatful if
someone could me piece together this mess.

Please, I am desperate!

Thanks in advance.

See:
Setting Up the Domain Name System for Active Directory

http://support.microsoft.com/default...b;en-us;237675

Best Practices for DNS Client settings in Windows 2000 server and in Windows
Server 2003

http://support.microsoft.com/default...b;en-us;825036



How to configure DNS for Internet access in Windows Server 2003

http://support.microsoft.com/default...b;en-us;323380



Basic AD DNS setup is install DNS on the DC, point the DNS server to itself
for DNS in the properties of TCP/IP (use the actual IP address NOT
127.0.0.1), all AD clients should point to the DNS server setup for the AD
domain ONLY. For Internet access either setup the AD DNS server to forward
requests and list your ISP's DNS server as the forwarder OR use root hints.
The only place on an AD domain where your ISP's DNS server(s) should be
listed is as forwarders.





hth

DDS


"it-support" <itsupport@discussions.microsoft.com> wrote in message
news:8A30CBB2-C9AE-4102-81CE-C8A505D79718@microsoft.com...
>I have absolutely no friggin idea how to do this. I realize DNS is needed
>for
> AD and exchange server and it has to be up and running. But how?
>
> I have randomly poked around in the DNS console and I have managed to make
> the server able to resolve adresses buy inserting some actual DNS server
> IP
> adresses into something called "route tips" or "routing tips". And
> suddenly
> it started working.
>
> I have a bunch of zones I have created under "Zones for normal search",
> but
> I have no idea which does what, which are working and which I can delete.
> The
> network I am setting up consist of a single server and five clients or so.
> Why should there be more than one zone?
>
> There was a default zone entry called "msdcs.[domain name].local", why
> local? Should I rename it to "localhost". Do I even need this zone and
> what
> does it do? What would happend if I deleted it?
>
> Is there some way of just resetting ALL DNS settings to factory default
> and
> then start over? If someone here will provide me with some pointers on how
> to
> do it, that would seem like the best option.
>
> I know how a DNS works and Ive taken courses on the subject, I am familiar
> with BIND servers which I believe are all nice and fluffy. Setting it up
> in
> windows however is a complete djungle of strangness and odd dialouges I
> just
> dont understand. Since there is no easy to understand guide or wizard for
> configuring DNS in Windows Server I would be incredibly happy and greatful
> if
> someone could me piece together this mess.
>
> Please, I am desperate!
>
> Thanks in advance.
>

Thanks! This clears things up for me, I am very greatful.


"Danny Sanders" wrote:

> See:
> Setting Up the Domain Name System for Active Directory
>
> http://support.microsoft.com/default...b;en-us;237675
>
> Best Practices for DNS Client settings in Windows 2000 server and in Windows
> Server 2003
>
> http://support.microsoft.com/default...b;en-us;825036
>
>
>
> How to configure DNS for Internet access in Windows Server 2003
>
> http://support.microsoft.com/default...b;en-us;323380
>
>
>
> Basic AD DNS setup is install DNS on the DC, point the DNS server to itself
> for DNS in the properties of TCP/IP (use the actual IP address NOT
> 127.0.0.1), all AD clients should point to the DNS server setup for the AD
> domain ONLY. For Internet access either setup the AD DNS server to forward
> requests and list your ISP's DNS server as the forwarder OR use root hints.
> The only place on an AD domain where your ISP's DNS server(s) should be
> listed is as forwarders.
>
>
>
>
>
> hth
>
> DDS
>
>
> "it-support" <itsupport@discussions.microsoft.com> wrote in message
> news:8A30CBB2-C9AE-4102-81CE-C8A505D79718@microsoft.com...
> >I have absolutely no friggin idea how to do this. I realize DNS is needed
> >for
> > AD and exchange server and it has to be up and running. But how?
> >
> > I have randomly poked around in the DNS console and I have managed to make
> > the server able to resolve adresses buy inserting some actual DNS server
> > IP
> > adresses into something called "route tips" or "routing tips". And
> > suddenly
> > it started working.
> >
> > I have a bunch of zones I have created under "Zones for normal search",
> > but
> > I have no idea which does what, which are working and which I can delete.
> > The
> > network I am setting up consist of a single server and five clients or so.
> > Why should there be more than one zone?
> >
> > There was a default zone entry called "msdcs.[domain name].local", why
> > local? Should I rename it to "localhost". Do I even need this zone and
> > what
> > does it do? What would happend if I deleted it?
> >
> > Is there some way of just resetting ALL DNS settings to factory default
> > and
> > then start over? If someone here will provide me with some pointers on how
> > to
> > do it, that would seem like the best option.
> >
> > I know how a DNS works and Ive taken courses on the subject, I am familiar
> > with BIND servers which I believe are all nice and fluffy. Setting it up
> > in
> > windows however is a complete djungle of strangness and odd dialouges I
> > just
> > dont understand. Since there is no easy to understand guide or wizard for
> > configuring DNS in Windows Server I would be incredibly happy and greatful
> > if
> > someone could me piece together this mess.
> >
> > Please, I am desperate!
> >
> > Thanks in advance.
> >
>
>
>