Hey all,
I've built three 2k3 domain controllers (one Active Directory-Integrated Primary and two Secondary) to replace my 2k DCs (two for this site and one for a remote site). All of my 2k3 DCs are running fine and DNS is running without any errors . I just stopped the DNS Server service on my last 2k DC and now I'm testing DNS from workstations using NSLOOKUP. I can resolve my DCs and about 10 of my workstations by name and address but nothing else. I can successfully PING everything on my network by name. I looked in DNS (all three DCs) and they only have the 10 workstations listed in in their Forward Lookup Zones. How long does it usually take for an AD-IP DNS server to find out the names on the machines on the network? I have a small network of about 60 workstations. Is there a way to have my Primary actively go out and pull in names and addresses? Then I could transfer the data to the two other servers.
Thanks,
Joe B
I've built three 2k3 domain controllers (one Active Directory-Integrated Primary and two Secondary) to replace my 2k DCs (two for this site and one for a remote site). All of my 2k3 DCs are running fine and DNS is running without any errors . I just stopped the DNS Server service on my last 2k DC and now I'm testing DNS from workstations using NSLOOKUP. I can resolve my DCs and about 10 of my workstations by name and address but nothing else. I can successfully PING everything on my network by name. I looked in DNS (all three DCs) and they only have the 10 workstations listed in in their Forward Lookup Zones. How long does it usually take for an AD-IP DNS server to find out the names on the machines on the network? I have a small network of about 60 workstations. Is there a way to have my Primary actively go out and pull in names and addresses? Then I could transfer the data to the two other servers.
Thanks,
Joe B