I was looking for a little more specific information than that [Smile]

If you are using a modern BIND implementation with a modern DHCP server you should configure the DHCP server to update your DNS records by using DDNS (nsupdate) updates whenever an IP address is leased or released. If your clients are Win2K they can also be configured to register their names when they get a lease.

If the laptop PC is going to participate in WINS/NetBios and your DNS service is provided by NT you can configure it to use a sort of WINS passthrough, where the DNS service will use WINS for name resolution. Clunky and a bit crap but it works.

If the laptop is not going to register it's name in WINS or respond to NETBios broadcasts you are a bit stuffed.

If your DHCP servers are NT4.0 you can switch on logging. This will create log files in \winnt\system32\dhcp which record lease renewals ans assignments. You will need to parse this file looking for the relevant entries - here is a sample of the file:
code:
10,02/21/03,12:55:07,Assign,10.17.16.46,SGB-5938,0080640C96BC
11,02/21/03,12:56:53,Renew,10.17.20.21,SGB-07772,0000397100B9
As you can see, two machines (SGB-07772 and SGB-5938) have leased IP addresses, one a renewal and the other an assign.

There is also a DHCP query tool available in the NT resource kit which will dump the database.

If your DHCP servers are Cisco routers or Access serves or similar, you're on your own [Eek!]