Re: DHCP/DNS questions.. couple weeks before going live and want to clear up a few concerns..
- From: "infinitiguy" <derek@xxxxxxxx>
- Date: Wed, 7 May 2008 23:30:42 -0400
Ace,
Thx for the article. I think I may have read part of this(or bits of the same info in other articles, because much of it was familiar). There were a few things that helped, but still have a few things unanswered.
re: the first question about DHCP. Completely understand. I wasn't going to increase the scope to span subnets(and therefore needing to change the subnet mask). So I should be good there. Ultimately what I'm going to do is create a new VLAN for my engineers DHCP clients and keep the existing VLAN(10.65.4.x) as a static only subnet for all their servers... but that will be a phase two of this project.
Back to the other good stuff...
re: the leasing times... with the other discussion above.. I think an 8 day lease will work... because any client that re-visits will retain their lease.. and if they visit mutliple subnets.. then they will just have multiple leases.. but only an A/PTR record on the current active lease(since the new re-registration will overwrite the existing entry..) so I think I'm ok there... so I'll have a 7/7 no-refresh/refresh.. with an 8 day DHCP lease.. and scavenging happening every 7 days.. all the defaults.. can't go wrong there, or so I've heard ;)
However, regarding the DNS registrations via DHCP.. the article didn't really touch on the option of "Discard A and PTR records when lease is deleted" This, combined with something I read about static entries not being effected by scavenging because they don't have an age, unless manually set(which makes sense... if it's static, you'd expect it to be there forever..).. I guess I'm still confused as to what the "Discard A and PTR records when lease is deleted" option, when aging and scavenging is meant to do that.. by aging the records and then checking the registrations.. if the lease is deleted.. and the client isn't registering anymore.. it'd be removed on the next scavenge cycle.. no?
The other question that the article did bring to mind is..
"You can use the DHCP server to register and update the PTR and A resource records on behalf of the server's DHCP-enabled clients. When you do this, you must use an additional DHCP option, the Client FQDN option (option 81). This option lets the client send its FQDN to the DHCP server in the DHCPREQUEST packet. This enables the client to notify the DHCP server as to the service level it requires."
I can't find an option 81..? unless option 81 means the "Use this connections DNS suffix in DNS registration" on the clients themselves.. if it is.. then no confusion there.
When I actually switch our zones live... one thing I'm going to need to do is add in hundreds of A records into our current forward DNS zone.. and I'll be creating a bunch of reverse DNS zones that I'll be populating with the corresponding static entries.. all the DHCP clients are not being migrated over, and will just re-register themselves through the means of a reboot, or during the next natural registration. What I'm planning on doing is taking the current primary zone(ionaglobal.com) and on the primary DC(i'll call it the primary DC because it'll be the only dc I have set for scavenging..) I'm going to remove the zone from being active directory integrated.. this should then allow me to edit the zone file directly.. and paste in all my records(that I'll have prepared ahead of time).. while I do this.. the zone should end up being removed from all other DC's in my domain.. I was then going to make ionaglobal an ADI zone again.. and let the new fully populated zone replicate back out. Is there any pitfall in this plan? I am planning for downtime, so services that will depend on DNS I will inform the business will be "down" during the transition... so I'm not concerned about that. Should I wait for the zones to be fully removed from all DC's before making it ADI again? I just performed this now in my test domain(istest.com) and the zone was removed from all DC's within about 5 minutes or less(2 DC's here in Boston and 2 in Dublin..). Do you see any fault in the above plan? All of the reverse zones that I'll be creating don't exist.. so I'll have to create those and load the data in/make those ADI as well.
Lot's of questions. Tell you what, read the followin article. It may answer all of your DNS registration and how DHCP/DNS interaction questions. Pay close attention to the DnsProxyUpdate group and how to use it so DHCP owns the record and will update it instead of creating additional A records, of course this works in conjunction with scavenging.
How to configure DNS dynamic updates in Windows Server 2003http://support.microsoft.com/kb/816592
As for DHCP, once you create a scope, you can't change the subnet and would need to recreate it. They recommend not to change the scope adresses because it may interfere with current leases.
--
Regards,
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer
For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Infinite Diversities in Infinite Combinations
.
- Follow-Ups:
- References:
- Prev by Date: Re: DHCP/DNS questions.. couple weeks before going live and want to clear up a few concerns..
- Next by Date: Re: DHCP/DNS questions.. couple weeks before going live and want to clear up a few concerns..
- Previous by thread: Re: DHCP/DNS questions.. couple weeks before going live and want to clear up a few concerns..
- Next by thread: Re: DHCP/DNS questions.. couple weeks before going live and want to clear up a few concerns..
- Index(es):
Relevant Pages
|
Loading
