DNS Dynamic Update with Windows DNS 2003, clients cannot register their name

Hi all,

I have setup a network that contains a domain controller and some clients, all of them run Windows Server 2003 Enterprise Edition.

On DC, I setup a AD-Integrated DNS server; my domain is nwtraders.msft. Then, I join all client into domain. I use static IP address for all computers. Now, all clients seem to register their name successfully.

For testing purpose, I setup another DNS server on a member server named Santiago (of course, this server has joined domain). On AD-integrated DNS server, I delegate a zone called test.nwtraders.msft to Santiago DNS server. Beside, I create a zone name myzone on Santiago DNS server. I'm sure that I have right DNS configuration: all zones allow clients to dynamic update (none-secure and secure update); up and running.
Next, I configure some clients to register their name to new DNS server (clients' name are  lima and santiago).

1. On Connection properties, on TCP/IP properties, I type Ip address of Santiago in "Primary DNS server". I choose Advanced button, and on tab DNS, I type "lima.myzone" on DNS suffix for this connection, and check  two check boxes bellow. Click Ok and Close to all properties pages. Then, I issue "ipconfig /registerdns" command, but I cannot see any name like lima on Santiago "myzone" zone. When looking at nwtraders.msft DNS server, I find lima in it (I'm sure that I have deleted this record before). What's wrong? I don't know!


2. Now, I try another way. I type "myzone" in "append these DNS suffixes (in order)" list box, still let all settings that 've been setup on part 1 remain. I issue "ipconfig /registerdns" again. The result is as the fisrt one. I try this test on some member servers, all of them CAN NOT register their name on Santiago DNS server's zone. Could you tell me why? And how to correct this?

Thank you in advance!

At last, I'm sorry about my English. :-)
cuongndAsked:
Who is Participating?
 
jhautaniConnect With a Mentor Commented:
About 1.:
> I type "lima.myzone" on DNS suffix for this connection, and check  two check boxes bellow
When you specify the DNS suffix for the connection do not include the client's name, only the zone. The client's name comes from computer properties. Now your client tries to register name lima.lima.myzone in zone lima.myzone.
> When looking at nwtraders.msft DNS server, I find lima in it
Full computer name as specidied in Computer Properties is always registered if the "Register this connection's addresses in DNS" is checked. The connection specific suffix is an additional DNS registration.

About 2.
The 'append these DNS suffixes' has nothing to do with the client's DNS registration. It lists the suffixes which will be appended to unqualified DNS queries. For example: list contains suffix 'myzone.local' Then you issue command 'ping server'. The computer will ping server.myzone.local

hope this helps
0
 
cuongndAuthor Commented:
Thank jhautani for you reply!

1. That's right as your suggestion that I should type "myzone" instead of "lima.myzone". But, you know, even when I have corrected this mistake, the problem still remains. Here is my configuration:

On DC & AD-integrated DNS:
DNS suffix (domain name): nwtraders.msft
IP: 172.16.2.200/255.255.255.0
Gateway: 172.16.2.200
DNS: 172.16.2.200

On Santiago (domain member) & another DNS server:
DNS suffix (domain name): nwtraders.msft
Connection-specific DNS : myzone
IP: 172.16.6.22/255.255.255.0
Gateway: 172.16.2.200
DNS: 172.16.6.22

On Lima (domain member):
DNS suffix (domain name): nwtraders.msft
Connection-specific DNS : myzone
IP: 172.16.6.212/255.255.255.0
Gateway: 172.16.2.200
DNS: 172.16.6.22


Other settings are as my first post. I think this configuration is fine, and it MUST work. But, It does not. Can you solve that? I try it many times and still fail.

2. You're right! I've checked my books and found your answer. Thank you!
0
 
cuongndAuthor Commented:
For more information, the configuration above is used to test dynamic DNS update. I want my client register with my own DNS server - my own zone. So I add another DNS and new  "myzone" zone. This is for testing purpose only :-)
0
 
cuongndAuthor Commented:
Hi all,

I have found the truth! :-)

In fact, I make an incorrect configuration. That is I use "myzone" for zone's name. Because a custom DNS server is intended only for third-level domain and higher, I cannot make dynamic DNS update to a top-level zone (which is "myzone" zone).

Now, I create another zone named "myzone.com", and reset my configuration as above, everything seems to run correctly.

La la la, now, I can call that a day!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.