Question : Dynamic DNS for Windows XP clients to a Linux Bind9 server

I've got a Linux Bind9 DNS server configured to the point that I can use it with both Windows and Linux clients and am able to nslookup any static entry set in the zone files. What I want to do now is have Windows XP clients connect dynamically but something is missing, I've followed various tutorials that describe creating keys using dnssec-keygen and then using nsupdate on the client to delete/recreate the A record but after I do that I'm still not able to lookup the client by name or IP. Instead I get:

C:\>nslookup
Default Server: ns1.domain.ca
Address: 10.0.0.2

> ns1
Server: ns1.domain.ca
Address: 10.0.0.2

Name: ns1.domain.ca
Address: 10.0.0.2

> cl1
Server: ns1.domain.ca
Address: 10.0.0.2

*** ns1.domain.ca can't find cl1: Non-existent domain

> cl1.domain.ca
Server: ns1.domain.ca
Address: 10.0.0.2

*** ns1.domain.ca can't find cl1.domain.ca: Non-existent domain

---

It looks to me like static entries are working as expected but not dynamic ones, which might make perfect sense considering no initial record was ever made for them on the name server. But doing that would defeat the purpose of a dynamic setup... wouldn't it?

A couple of questions:
1. To have dynamic clients does the DNS server also need to act as a DHCP that creates the initial A records?
2. Is it actually possible to get a Windows Bind9 client to dynamically create and update its name record?
3. If so, how and where can I find a howto/reference?

Thanks in advance for any help.

Answer : Dynamic DNS for Windows XP clients to a Linux Bind9 server

To have dynamic clients, you need to define the zone as dynamic so that it could be updated.
This would apply to both forward and reverse zones.
The TCP/IP settings under advanced have the register with DNS setting.

Note that you would use the same mechanism to add entries to the zone even if they are static.  The problem is how you get rid of stale records. i.e. cl1 registers with IP 10.0.0.5 the following day it registers with IP 10.0.0.6.  Not sure whether the system on cl1 will issue a delete when you order the system to shutdown or whether you would need a script to validate whether cl1 is still on IP 10.0.0.5 and if it is not, issue a delete update for both forward and reverse records.