DNS configuration

[mudcow007]

Hello guys/ gals

we currently run a 2000 domain with xp clients, dns has been installed on the schema server but without any reverse lookup zones

when i went to add a zone i chose AD integrated, then its askign for either "network id" or "zone name" we use the 192.168.0 range of address but we also have remote sites that connect in via VPN on different addresses, so i thought i will have to use "Zone Name" does this name matter what it is?

is the name the same as the domain? so if the domain was called "POP" the zone name would be "POP.ds"?

thanks all

 

[mudcow007]

sorry i forgot to mention, the reason i dont think DNS is configured correctly is that if you run "nslookup" you receive the message

"Cant find server name for address *********: non existant domain"

 

[ITPangaeaArchitect]

you should have DNS installed on all DCs.

from there, the PDCe should face itself and itself only for DNS.
all replica DCs in the same site as the PDCe should face the PDCe for preferred DNS, and themselves as alternate DNS.
One DC in remote sites should point to the PDCe as the preferred DNS server and itself as alternate, then all others in that site should face the DC in their site pointing to the PDCe for preferred as their preferred, and themselves as alternates.
This will both serve to standardize your name resolution topology as well as your replication topology.

You need to create a reverse lookup zone for all subnets that connect to your domain, not to mention subnet objects that are attached to the appropriate sites in AD Sites and Services.

- Brandon Wilson
MCSE:Security00/03; MCSA:Security03
MCSA:Messaging00; MCP; A+
IT Pangaea (

http://it-pangaea.com)

 

[TechyMcSe2k]

Troubleshooting Windows 2000 Server DNS

http://technet.microsoft.com/en-us/library/bb726934.aspx

_______________________________________
Great knowledge can be obtained by mastering the Google algorithm.