Windows 2003 DC & DNS - Active Directory

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

Hello All;

I need some information on setting up DNS on our 2003 DC.
For Active Directory Support.
I followed the information here:
http://www.petri.co.il/install_and_configure_w2k_dns_server.htm
And the information here
http://support.microsoft.com/?kbid=237675

But it is all for windows 2000 DNS.
Though it is different in 2003, I still was able to set up my DNS in 2003.

This is the main question here:

In the [Forward lookup zone]
It has an "A" Record already for the [2003 DC]
Do I need to add an "A" Record for each of the other Servers and Machines
In the Network?

-------------------
These are the problems that I am having:

Our other 2003 Domain Member Server.
When making shares, it is not giving us the [Locations] Domain-Name.
It only shows the -2003 Server.. And no Domain?

-------------------
Another problem that we are experiencing:

When browsing the network on the 2000 Pro Domain Members.
Sometimes that get the Warning:
[Their correctly are no Domain Controllers to service the request.]


-------------------
Any idea's on this will be extremely helpful.

Thank You
Wayne

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

Yes, that should occur automatically assuming the zone is configured to
permit dynamic update and the members/DCs DNS resolver is pointed toward
this DNS server.

--
Dean Wells [MVP / Directory Services]
MSEtechnology
[[ Please respond to the Newsgroup only regarding posts ]]
R e m o v e t h e m a s k t o s e n d e m a i l

Wayne & Carr wrote:
> Hello All;
>
> I need some information on setting up DNS on our 2003 DC.
> For Active Directory Support.
> I followed the information here:
> http://www.petri.co.il/install_and_configure_w2k_dns_server.htm
> And the information here
> http://support.microsoft.com/?kbid=237675
>
> But it is all for windows 2000 DNS.
> Though it is different in 2003, I still was able to set up my DNS in
> 2003.
>
> This is the main question here:
>
> In the [Forward lookup zone]
> It has an "A" Record already for the [2003 DC]
> Do I need to add an "A" Record for each of the other Servers and
> Machines In the Network?
>
> -------------------
> These are the problems that I am having:
>
> Our other 2003 Domain Member Server.
> When making shares, it is not giving us the [Locations] Domain-Name.
> It only shows the -2003 Server.. And no Domain?
>
> -------------------
> Another problem that we are experiencing:
>
> When browsing the network on the 2000 Pro Domain Members.
> Sometimes that get the Warning:
> [Their correctly are no Domain Controllers to service the request.]
>
>
> -------------------
> Any idea's on this will be extremely helpful.
>
> Thank You
> Wayne

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:eLtbwj0GFHA.2156@TK2MSFTNGP09.phx.gbl,
Wayne & Carr <spam@spam.net> commented
Then Kevin replied below:
> Hello All;
>
> I need some information on setting up DNS on our 2003
> DC.
> For Active Directory Support.
> I followed the information here:
> http://www.petri.co.il/install_and_configure_w2k_dns_server.htm
> And the information here
> http://support.microsoft.com/?kbid=237675
>
> But it is all for windows 2000 DNS.
> Though it is different in 2003, I still was able to set
> up my DNS in 2003.
>
> This is the main question here:
>
> In the [Forward lookup zone]
> It has an "A" Record already for the [2003 DC]
> Do I need to add an "A" Record for each of the other
> Servers and Machines In the Network?
>
> -------------------
> These are the problems that I am having:
>
> Our other 2003 Domain Member Server.
> When making shares, it is not giving us the [Locations]
> Domain-Name.
> It only shows the -2003 Server.. And no Domain?
>
> -------------------
> Another problem that we are experiencing:
>
> When browsing the network on the 2000 Pro Domain Members.
> Sometimes that get the Warning:
> [Their correctly are no Domain Controllers to service the
> request.]

First rule in Active Directory, make sure all DCs and member clients use the
DC's address for DNS, only!
Clients are not required to register in DNS, but file servers should. Make
sure the file servers and clients you want registered in DNS have the
correct primary DNS suffix.



--
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 address.
===================================
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
===================================

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

"Kevin D. Goodknecht Sr. [MVP]" >
> First rule in Active Directory, make sure all DCs and member clients use
the
> DC's address for DNS, only!
> Clients are not required to register in DNS, but file servers should. Make
> sure the file servers and clients you want registered in DNS have the
> correct primary DNS suffix.


Thank you, Thank you, Thank you, Thank you
Did I forget to say Thank You?

That was it, just needed to remove all the other DNS Entries in the 2003
Server
And the other machines, Reboot and it works like a charm.

The 2003 Domain Member now sees the Domain

Thank you once again

Some to add to our KB.

Wayne