DNS forward lookup zone

[laopang]

Dear Expert:

I have a active directory intrgrated DNS server, I
configured my dns forward lookup zone as named "hq2.emis-
inc.com" which is also my domain name. the DNS can pass
the simple query.

However in the DNS forward lookup zone, it didn't show up
all the hosts records and none of the subfolders are
show up. I use DHCP to point all clients to my DNS server.
I can not figure out what is the problem.
The server is windows 2000 advanced server.

thanks a lot.

laopang

 

[Herb Martin]

Dear Expert:

I have a active directory intrgrated DNS server, I
configured my dns forward lookup zone as named "hq2.emis-
inc.com" which is also my domain name. the DNS can pass
the simple query.

Ok, the zone and domain are hq2.emisinc.com and you have
machines with names like, machine.hq2.emisinc.com, right?

However in the DNS forward lookup zone, it didn't show up
all the hosts records and none of the subfolders are
show up.

All "what" records? For a Win2000 domain? Did you make the
zone Dynamic? Did you point the DC's own CLIENT properties
to this DNS only (NIC\IP\DNS Server)?

(If you correct either of these then restart NetLogon service to
register the missing records.)

I use DHCP to point all clients to my DNS server.
I can not figure out what is the problem.
The server is windows 2000 advanced server.

Common is to forget to point the DC/DNS server itself to the
internal dynamic DNS. (Or to include this DNS AND another
external DNS -- use internal only.)

If you need to resolve Internet names, then you should setup your
DNS SERVER properties to use a "forwarder" at your ISP (in
most cases.)

 

[stevta [MSFT]]

Is your DC only pointed to itself for DNS?
Under TCP properties under advanced and the DNS tab is
register this connection in DNS checked?
Properties for MY COmputer should show the FQDN for your
dc to be DC.HQ2.EMISINC.COM is this what it shows or
something else?
These are the three common causes for DNS registration
failures.
Netdiag /V and Dcdiag /V may help too.