Archived from groups: microsoft.public.win2000.dns (
More info?)
Dear Kevin,
thanks a lot for mercy ;-).
What I understood is that you suggest to
- scavenge a Reverse zone every day
- - what exactly should I set for "No-refresh interval" and "Refresh interval"
- - - in the server properties
- - - in the reverse zone properties
What I read in other posts is to create a reverse zone (to prevent internet
name resolution (forwarding) because of a "not hosted" zone), but don't allow
updates.
Is that your opion too ?
What about Option 002 ?
"002 Time Offset Time offset (in seconds) from Universal Time Coordinated
(UTC), aka Greenwich Mean Time "
What should that do in this case ?
Thanks a lot for your help in advance
Juergen
"Kevin D. Goodknecht Sr. [MVP]" schrieb:
> In news:976D6A63-21C0-4939-A7AB-861EF5ACA429@microsoft.com,
> Juergen <Juergen@discussions.microsoft.com> posted this:
> > Come on ..... please
> >
> > "Juergen" schrieb:
> >
> >> Can any of the experts give advise what would be a "Best practise",
> >> please.
> >>
> >> "Juergen" schrieb:
> >>
> >>> Dear all,
> >>>
> >>> we've problems with our Reverse Lookup Zone, many IP numbers have
> >>> multiple PTR records but each IP should only have one PTR record.
> >>> The lease time for DHCP clients is 4 days - and that should not be
> >>> changed. Seems that a lot of people experience this problem.
> >>>
> >>> Can anyone tell us what to do best:
> >>> 1. What to set on the DHCP server
> >>> 2. What to set on W2K- and XP-Clients (that do DNS-registration
> >>> themselves)
> >>> 3. How to set the Aging/Scaveging properties in dependency of the
> >>> DHCP-lease time. (Refresh and No-refresh) ?
> >>> 4. Other ...
>
> This is generally caused by clients not releasing the IP address at
> shutdown, improper shutdowns, or clients (usually laptops) disconnecting the
> network cable without releasing the IP lease.
> I have found that adding option 002 will help with clients not releasing the
> address at shutdown. As for the laptops there isn't much you can do since
> you can't prevent users from disconnecting the cable. Reducing the lease
> time can help DHCP keep the zones clean but I would not lease for less than
> one day.
> This can also be an ownership problem on the reverse zones. This is not a
> problem for forward zones because the host name should only be registered by
> one owner because the name does not change. For reverse zones it is
> different, the PTR name is the IP number so a PTR register under one name
> can only be removed by the owner of the record. You can have one IP owned by
> several clients in the reverse zone, if the client does not remove its PTR,
> the next client that registers the PTR cannot update or remove the previous
> owner's PTR record.
> Reverse zones are not required for proper AD function, if you want you can
> have the reverse zone scavenged daily. But I'd create a static record for
> DNS servers so you don't get the old nslookup "can't find servername for
> address <ipaddress>" message.
>
>
>
> --Â?
> Best regards,
> Kevin D4 Dad Goodknecht Sr. [MVP]
> Hope This Helps
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
>
http://www.oehelp.com/OEBackup/Default.aspx
> ===================================
>
>
>
Facebook
Twitter
Instagram