DNS trouble

[leobis]

Hi all,

a couple of days ago I made I clean installation in my server (W2k Ad. Server); while installing the Active Directory I opted for the DNS automatic installation.
Given that it's an environmental test network I only linked my laptop (windows 2000 Pro) to the above mentioned Domain Controller (in the domain controller I also installed the DHCP service); everything seems to be working, the laptop obtain the IP address from the DHCP server and the ping command can resolve the hostnames of the computers (before using the ping command I cancelled the netbios cache with "nbtstat -R" and as I said no problem in resolving the hostnames and their related IP addresses).

But on looking at the Forward Lookup Zone of the Dns server the Host name (the A entry) of my laptop computer is NOT listed at all.
Below you can find the DNS tree that was created during the installation of AD

ServerNAME
.
.
-Forward Lookup Zones
. .
. .
. - .(the root zone)
. . .
. . .
. . -it
. . .
. . .
. . -Tuscany (the colour of this folder is grey)
. .
. .
. -Tuscany.it
. .
. . + _msdcs
. .
. . + _sites
. .
. . + _tcp
. .
. . + _udp
.
.
.
+ Reverse Lookup Zones

As I mentioned, the above zones where created automatically during the installation of AD, and the all the zones type are Active Directory Integrated (the dynamic updates is "only secure updates).
In this regard, what should I check and fix so as to have the hostname (type A and PTR) listed in their respective zones?

To sum up the Dc as well as the AD service acts as:

DNS SETTINGS
- DNS server (the zones are active directory integrated); the Ip address of the DNS server was set on "preferred DNS server" window of client computer
- in the DNS Advanced tab the settings are as follows:

- Append primary connection specific DNS suffixes: (option checked)
- Append parent suffixes of the primary DNS suffix (option checked)

- Register this connection's addresses in DNS (option checked)

DHCP SETTINGS

- Dhcp Server is running and release the ip address according to the scope instruction
the scope option for the scope are:

OPTION NAME vALUE

005 none
006 none
015 (empty)
045 none
046 0x0
044 none

the server option values have the same values as the ones of the scope options.

in the Dns tab of the DHCP windows the are the following settings:

-Automacally update DHCP client information in DNS (option checked)
+ Update DNS only if DHCP client request (option checked)
-Discard forward (name-to-address) lookup when lease expires (option checked)

I hope that the above explanation may the situation clear for troubleshooting ... anyway I will be at your disposal for further information

Thanks in advance for your help.

Leonardo

 

[Odissey]

1. DNS server->Forward Lookup Zone-> <zone name> -> Properties->general-> Allow Dynamic Updates = YES
2. Laptop: Network Identification-> Properties-> More-> type your zone

 

[leobis]

Thanks Odissey for your reply, but now I think that the cause of the above problem should, and I repeat should, be to ascribe to the scope option settings; as I mentioned in my previous message those settings where no specified but few hours ago I filled those tabs with the missing parameters (actually the DHCP Server IP address) and now everything seems to work (in the DNS forward and reverse lookup zones are listed all the entries, either the A and the PTR types);
I had already checked the primay DNS suffix of my laptop and it matched the one of the Forwad lookup zone;
as for the dynamic updates, since these zone are configured as Active directory integrated, uptadates are carried out by the AD dinamically, so probably the cause of the problem might be traced to the option scope settings. Do you think that this solution may be the right one?

Anyway thanks again for your help. (if you wish I will keep you informed about the &quot;behaviour&quot; of the server)

Leonardo

 

[GiaBetiu]

Let me clarify a little how the things are going.
On the client side (for win2k systems) you have in TCP/IP / Properties / Advanced / DNS few options. One of them is &quot;register this connection adddress in DNS&quot;. That one has to be checked.
If the client is win9x, NT, then you don't have any setting, because it doesn't know to register itself in DNS. It needs DHCP.
What you have to know is that just in the forward lookup zone the clients are updating. Not in the reverse. In reverse just DHCP has this right.
Speaking about rights, DHCP server also has to be part of the DNSproxy group. Otherwise will not have rights to write in the DNS (if secure updates is on).
On the server side. Indeed the settings are the ones that you mentioned before.
These beeing the theory about, try to follow and you should find the error.
If you have questions, just ask me.
Success! Gia Betiu
giabetiu@chello.nl
Computer Eng. CNE 4, CNE 5, soon MCSE2k