Shortening the leases was one of the other ideas that we had tossed
around. Right now we are using the defualt 8 days. The reason
that I hadn't changed this was becasue of something I had read in the resource
kit.
Chapter 6 Windows 2000 DNS.... "By
default, the dynamic update client dynamically registers its A resource records
and possibly all of its PTR resource records every 24 hours or whenever any of
the following events occur:
- The TCP/IP config. is changed.
- The DHCP address is renewed or a new lease is obtained
- A Plug and Play event occurs
- An IP address is added or removed from the computer when the user changes or adds and IP address for a static adapter.
After I read this I assumed that the client would update itself within a
day anyway (although I haven't tested and verified this yet) and I thought
all my problems would be solved. When I continued to ponder this, the
only heartburn that I had with waiting the 24 hours, was the fact that all
1200 of my new clients would be coming onto the network within a few hours of
one another so waiting a day or even a few hours for the 1/2 the DHCP lease time
seemed like it wouldn't help much.
Since our network folks were not able
to offer much (err.. any) help. We have decided to take the ipconfig
/registerdns route in our logon script, which from our preliminary testing seems
to do the trick...
Thanks for all the good
ideas..
-Tim
From: Roger Seielstad [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 15, 2003 12:40 PM
To: '[EMAIL PROTECTED]'
One of many reasons our default DHCP lease time is 4
hours.
--------------------------------------------------------------
Roger D. Seielstad -
MTS MCSE MS-MVP
Sr. Systems Administrator
Inovis Inc.
-----Original Message-----
From: Carr, Jonathan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 15, 2003 12:36 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] AD DNS/DHCP issue/questionW2k and xp update their own dns records but only when they renew their leases or get a different lease. Here is a different way of doing it. Shorten your leases to a couple of hours. The clients will update at the 50% time mark and register their new name. Tell me if it works-----Original Message-----
From: Wright, T. MR NSSB [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 15, 2003 11:08 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] AD DNS/DHCP issue/questionI'm pretty sure that will work... that was one of the aforementioned 'work arounds'. I was just curious why it wasn't updating itself as it does when I sit on the same network. Thanks for the ideas...-Tim
From: Carr, Jonathan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 15, 2003 10:08 AM
To: [EMAIL PROTECTED]You might want to run a post setup job to run ipconfig /registerdns-----Original Message-----
From: Wright, T. MR NSSB [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 15, 2003 8:46 AM
To: '[EMAIL PROTECTED]'
Subject: [ActiveDir] AD DNS/DHCP issue/questionGonna try and keep this short and sweetI have 1200 clients that I am adding to the network. They get their new machine with our ghost image called 'image' they plug it into the network, when they bring it up they are asked a few questions (name, username etc.) this info is passed into the answer file for sysprep. The machine reboots, sysprep runs, it changes the name to meet our naming convention, adds it to the domain etc. then the user logs in for the first time and the logon scripts take care of the rest.My issue is when they first plug the machine in, the lease in DHCP server shows up as 'image' and once the machine is renamed and added to the domain, for some reason it doesn't update itself in DHCP which in turn doesn't update the DNS PTR record. I'm concerned that having 1200 machines called 'image' on the network is not going to be a good thing. This is all happening in another building on campus (through a few routers/switches)When I do the same test on the SAME network as the DHCP/DNS servers it works like a charm, the name is updated before the user logon box even appears. It seems as if there is some sort of broadcast traffic that is not getting to where it needs to get, although I was under the belief that once the client knows it's DHCP server it will automagically try to go back to the same machine first. I have asked the network guys to take a look, and as usualy they say theres nothing wrong with their network;-)I am using the default settings for the DHCP scope, and all the clients are WinXP pro SP1. I have a few ideas for a workaround but I would like to see it work as intended. Any ideas?Thanks,-Tim
