• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 295
  • Last Modified:

Dynamical DNS for DHCP on win2k

I have a DHCP, DNS installed on a win2k DC. I want to use the dynamical dns features of the win2k domain. It does work properly of the win2k pro, but when I let an NT4.0 sever use DHCP, it does not appear in the DNS manager. The NT server has already joined the win2k domain. And, as Microsoft said, I did check the option "Enable Updates For DNS Clients That Do Not Support Dynamic Update." in the DHCP manager.
The result is also failed when I use a windows98 client to do this test.
I don't know which step I missed.

This is the additional info after I posted this question:
Well, I made a mistake that I didn't create the reverse zone x.x.in-addr.arpa. When the reverse zone was created, I can see the PTR record of the NT server is there, with the host name "ts-nt". Since it didn't show the FQDN like the win2k pro clients, I doubt that client didn't send its FQDN to the DHCP server.
Could anyone explain it and give me a solution?
0
myself7
Asked:
myself7
  • 8
  • 3
  • 3
  • +1
1 Solution
 
Ben_LCommented:
what you need to do is the add to your DHCP option to add all the client SUUFIX (ex: x.com)
that will add record to your win9x+nt4 to your dns..
u can add the suffix manualy on the win9x and on the nt4 tcp-ip as well.
Hope This Will Help You.
0
 
ymashCommented:
Also, in the DNS manager, go to the properties for teh domain and make sure that allow dynamic updates is set to "yes".
0
 
myself7Author Commented:
Well, I did add the suffix manually on the win9x and nt clients. But it doesn't work.
ymash, I did allow the dynamic updates in the DNS manager.
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
matt023Commented:
you'll have to add the suffix from the DHCP server side.  The DHCP server will take what the client returns as a hostname/FQDN to find an appropriate zone and register it.  Make sure the domain suffix that you add does exist as a zone in your DNS server.  
BTW, it is not recommended to have DHCP running on a DC.  It is a security risk due to the nature of dynamic update which can be exploited to alter your DC RR's.
 
0
 
myself7Author Commented:
Yes, matt023, it's only a test for me. To be convenient, I installed the DHCP on an DC. I will notice the security issues when I apply the DCs in the running env.
Well, the suffix which I add on the NT client is the same as the win2k domain name. For example, the win2k domain is mydomain.com, and I did add the suffix of the NT client as mydomain.com. Because the suffix of the NT client and the win2k domain are the same, and I do have the mydomain.com zone in the DNS manager, so it should be ok. But actually, i cannot see the NT client in the zone mydomain.com.
0
 
ymashCommented:
I know this is a step back to the past, but you might want to consider a WINS server since you have Win98 and NT machines.
0
 
myself7Author Commented:
Yes, ymash. I know I can use WINS for the winnt and win9x clients. But I just want to test the DDNS features of win2k.
0
 
matt023Commented:
is the "Always update DNS" option selected?  DHCP server will not register A records if this option is not selected unless the client requests that it does so - as for Win2k clients.  I know it seems contradicting, but I've seen this behavior before - with NT and Unix clients.  May be it's a bug and might be fixed in the next SP.
0
 
myself7Author Commented:
Yes, ymash. I know I can use WINS for the winnt and win9x clients. But I just want to test the DDNS features of win2k.
0
 
myself7Author Commented:
Yes, matt023. The option "Always update DNS" was selected.
0
 
matt023Commented:
Just to make sure, you added the domain suffix option in the DHCP scope and not on the client itself - correct?

your previous comment sounds like you still have the domain suffix on the client.
0
 
myself7Author Commented:
No. I added the domain suffix on the client itself. I don't know how to ass the domain suffix option in the DHCP scope. Could you type the steps in detail?
0
 
myself7Author Commented:
No. I added the domain suffix on the client itself. I don't know how to add the domain suffix option
in the DHCP scope. Could you type the steps in detail?
0
 
ymashCommented:
you need to add scope option 015 DNS domain name.
0
 
myself7Author Commented:
Great! ymash. It's the definite reason that I got this problem. After I add the scope option 015 DNS domain name, I got the NT/98 clients appeared in my DNS server with both A record and PTR record.
And, I'd like to say, the suffix configuration of the clients doesn't afftect the DNS entry. Whether I set the suffix on clients or not, the DHCP server always send the update information to the DNS and the DNS always get them appear with the suffix you set in the 015 DNS domain name.

Thanks, ymash, matt023, and Ben.
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.

Join & Write a Comment

Featured Post

Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

  • 8
  • 3
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now