Re: DNS PROBLEMS !

I'm having the same problem with stale records even when they are set to
delete. After reading the KB's from the provided links, I expect the problem
to be caused by DHCP on my DC.

I have 2 server 2003 DC's running AD integrated, and 99% 2k/XP clients. One
DC is also my DHCP server. My DHCP server is configred to update DNS.
Instead of moving my DHCP server to a non DC, is there any reason not to
stop DHCP from doing DNS updates.

Can this solution be considered a good alternative?



"Ace Fekay [MVP]"
<PleaseSubstituteMyActualFirstName&LastNameHere@xxxxxxxxxxx> wrote in
message news:uyONpSg9FHA.132@xxxxxxxxxxxxxxxxxxxxxxx
> In news:0EB71F7F-65B6-4156-872B-C1D8C99554EA@xxxxxxxxxxxxx,
> Johan <johan@xxxxxxx> made this post, which I then commented about below:
>> Hi Ace,
>>
>> Yes, these two servers are DC's and Win servers as well, they are
>> within a AD Intergrated zone. In the IP properties only these two
>> servers IP addresses appear.
>> I notice that in the Reverse Lookup zones there appears to be lots of
>> stale records, and often a PC will be registered in the Reverse
>> Lookup zone, but will not appear in the Forward Lookup zone.
>> These two servers were installed about 4 years ago and have been
>> working fine till about a month ago, and I have made no changes.
>> I am presently upgarding all my desktop PC's to XP Pro, and these
>> upgraded PC's seem to be the main culprits, after trying to figure
>> out what the problem was I discovered that my DNS zones were not
>> updating.
>>
>> Johan
>
> Hi John,
>
> I see, so they are not Primary and Secondary zones, but rather the zone is
> configured as AD Integrated and DNS is installed on both DCs, and the zone
> exists on both of these DC/DNS srvers. AD integrated zones are not Primary
> or Secondary zones. AD Integrated zones *just* means the zone data is
> stored in the physical AD database and not in a text file. They can act as
> a Primary to a secondary zone, if you like, but if it';s AD Integrated,
> you can';t make a secondary copy of it on another DC, but rather on a
> member server or BIND, or some other server. I just wanted to get the
> terminology straight.
>
> As far as updates and stale records, I would institute scavenging. If the
> stale records are the XP machines (or 2000 for that matter), when they get
> an IP from DHCP, they will register into the zone. If the machine gets
> unplugged, and plugged in again and gets another different IP, it may not
> overwrite it. DHCP needs to own the records to be able to update the
> records. To insure that happens, besides using scavenging, I would force
> DHCP to own the records so it can update them itself and force DHCP to
> register all records so it itself can overwrite the records.
>
> Take a look at this article to show you how to use the DNSUpdateProxy
> group to allow DHCP to own the records.
>
> 317590 - HOW TO Configure DNS Dynamic Update in Windows 2000 and
> DNSUpdateProxy Group:
> http://support.microsoft.com/?id=317590
>
> This may be of use too:
> 306780 - DHCP Does Not Delete DDNS PTR Record for Expired Leases:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;306780&Product=win2000
>
> This shows how to enable scavenging:
> How to use DNS aging and scavenging:
> http://www.microsoft.com/windows2000/en/advanced/help/default.asp?url=/windows2000/en/advanced/help/sag_DNS_pro_ConfigAgingScavengingNode.htm
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> If this post is viewed at a non-Microsoft community website, and you were
> to respond to it through that community's website, I may not see your
> reply unless that website posts replies back to the original Microsoft
> forum. Therefore, please direct all replies ONLY to the Microsoft public
> newsgroup this thread originated in so all can benefit or ensure the web
> community posts it back to the original forum.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft MVP - Windows Server Directory Services
> Microsoft Certified Trainer
> Infinite Diversities in Infinite Combinations.
> =================================
>
>


.

Relevant Pages

  • Re: DDNS from NW6.5 to W2K
    ... > Option 15 doesn't appear to exist on the NetWare DHCP server. ... >>> DNS server. ... Each zone has ...
    (microsoft.public.windows.server.dns)
  • Re: Maintaining AD-Integrated Reverse Zone With No DHCP Server on Domain Controller
    ... DHCP server runs on a member server. ... No. AD Integrated zones are only available on DCs that are DNS servers. ... DC I'm having to use a secondary zone grabbed from the Windows 2003 ...
    (microsoft.public.windows.server.dns)
  • Re: Moving DNS to New Server
    ... DHCP already migrated. ... Paul recommends installing DNS before promoting the DC. ... but I'm still seeing my Zone. ... I've set up a new server as a DC. ...
    (microsoft.public.win2000.dns)
  • Re: DNS issue - clients not registering
    ... We run Server ... Consolidate DNS by removing DNS services from all servers except for our ... which is the zone based on our webserver. ... I've looked at my DHCP, which is running at each site individually, since ...
    (microsoft.public.windows.server.active_directory)
  • Re: Scavenge Stale Resource Records
    ... > We have a lot of stale records and scavenging was never enabled on the ... We just went into DNS and at the server level, ... the command to immediately start scavening just triggers scavening but if this ... is not configured at server and zone level there are no records which are aged. ...
    (microsoft.public.windows.server.dns)