RE: [ActiveDir] AD DNS/DHCP issue/question

[Rick Kingslan]

Title: Message

It has to have a kerberos ticket in Secured Updates, IIRC.   Rick Kingslan  MCSE, MCSA, MCT Microsoft MVP - Active Directory Associate Expert Expert Zone - www.microsoft.com/windowsxp/expertzone   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Salandra, Justin A. Sent: Wednesday, July 16, 2003 1:10 PM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] AD DNS/DHCP issue/question What won’t get registered in DNS if the zone is set to Secured Updates Only?  Anything that does not have a object in the directory?   -----Original Message----- From: Roger Seielstad [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 15, 2003 3:09 PM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] AD DNS/DHCP issue/question   That sounds like its properly configured, although I strongly suggest setting DNS for secured updates only.   Routers won't cache DHCP info, either - they just forward it. You might want to look at the active leases to see what's happening. -------------------------------------------------------------- Roger D. Seielstad - MTS MCSE MS-MVP Sr. Systems Administrator Inovis Inc. -----Original Message----- From: Wright, T. MR NSSB [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 15, 2003 12:38 PM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] AD DNS/DHCP issue/question I can't speak for the network...  I asked our network guy to change the IP-Helper address to point to the new DHCP server.  He did that and I get my lease...  Is there something else that I should ask him to look at?     One thing I thought of is that it may be possible that there is a router that is doing caching in there somewhere...  again I'm not sure.     The DHCP server is set to 'update DNS only if DHCP client requests' and DNS is not set for secure updates only.     One other thing the DHCP server is a seperate machine from DNS so any broadcasts that were intended for DNS(none that I am aware of) would fall on deaf ears becasue the helper address that is configured would send them to the DHCP server.   Thanks,   -Tim   From: Roger Seielstad [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 15, 2003 9:35 AM To: '[EMAIL PROTECTED]' I assume that all necessary routers are configured to use bootp forwarding from the client networks to the DHCP servers? It sounds like they might not be properly configured.   Also, what are the DNS update settings for the DHCP servers? Are they set to update on behalf of the clients? Is DNS set for Secure Updates only?   Roger -------------------------------------------------------------- Roger D. Seielstad - MTS MCSE MS-MVP Sr. Systems Administrator Inovis Inc. -----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/question Gonna try and keep this short and sweet   I 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