|
|
Hi,
I have a Windows 2003 Active Directory domain, with DDNS and DHCP, with
a mix of Windows and Linux boxes all connected to the domain (linux
boxes connected with Winbind and Samba).
My problem is that the linux boxes, which get their IP addresses from
the AD DHCP, and appear in the DNS (after adding
DHCP_HOSTNAME=computer.domain.local to the ifcfg-eth0), seem to get
scavenged, and disappear from the DNS, even though they are on 24 hours
a day and connected to the network all the time. This is true for
computers with and without DHCP reservations.
Can anyone give me a clue:
1. why these computers are disappearing
2. what should proper scavenging settings be?
Thanks,
Max
|
|
Hello atomax[ at ]gmail.com,
How is you scavenging configured?
Do you use secure dynamic updates?
With a MS DHCP server you can also follow this one:
http://technet.microsoft.com/en-us/library/cc787034.aspx
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
[Quoted Text] > Hi,
> I have a Windows 2003 Active Directory domain, with DDNS and DHCP,
> with
> a mix of Windows and Linux boxes all connected to the domain (linux
> boxes connected with Winbind and Samba).
> My problem is that the linux boxes, which get their IP addresses from
> the AD DHCP, and appear in the DNS (after adding
> DHCP_HOSTNAME=computer.domain.local to the ifcfg-eth0), seem to get
> scavenged, and disappear from the DNS, even though they are on 24
> hours
> a day and connected to the network all the time. This is true for
> computers with and without DHCP reservations.
> Can anyone give me a clue:
> 1. why these computers are disappearing
> 2. what should proper scavenging settings be?
> Thanks,
> Max
|
|
I have it configured for secure and non-secure dynamic updates
Scavenging is set for 7 days.
All records are set to dynamically update the DNS always.
Also, I have credentials configured on the DHCP service.
I've looked at the Technet article you referenced. It has lots of useful
information, but doesn't seem to address my issue, which is that
computers whose leases should not be expiring are being removed from the
DNS. I've now removed the checkmark, so records will not be removed when
a lease expires, but now I expect my DNS to be littered with useless
entries.
I appreciate the help.
Max
Meinolf Weber [MVP-DS] wrote:
[Quoted Text] > Hello atomax[ at ]gmail.com, > > How is you scavenging configured? > > Do you use secure dynamic updates? > > With a MS DHCP server you can also follow this one: > http://technet.microsoft.com/en-us/library/cc787034.aspx> > Best regards > > Meinolf Weber > Disclaimer: This posting is provided "AS IS" with no warranties, and > confers no rights. > ** Please do NOT email, only reply to Newsgroups > ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm> >> Hi, >> I have a Windows 2003 Active Directory domain, with DDNS and DHCP, >> with >> a mix of Windows and Linux boxes all connected to the domain (linux >> boxes connected with Winbind and Samba). >> My problem is that the linux boxes, which get their IP addresses from >> the AD DHCP, and appear in the DNS (after adding >> DHCP_HOSTNAME=computer.domain.local to the ifcfg-eth0), seem to get >> scavenged, and disappear from the DNS, even though they are on 24 >> hours >> a day and connected to the network all the time. This is true for >> computers with and without DHCP reservations. >> Can anyone give me a clue: >> 1. why these computers are disappearing >> 2. what should proper scavenging settings be? >> Thanks, >> Max > > |
|
Read inline please.
In news:O4%23oSJDZJHA.556[ at ]TK2MSFTNGP06.phx.gbl,
atomax[ at ]nospam.nospam <atomax[ at ]gmail.com> wrote:
[Quoted Text] > I have it configured for secure and non-secure dynamic updates
>
> Scavenging is set for 7 days.
>
> All records are set to dynamically update the DNS always.
>
> Also, I have credentials configured on the DHCP service.
>
> I've looked at the Technet article you referenced. It has lots of
> useful information, but doesn't seem to address my issue, which is
> that computers whose leases should not be expiring are being removed
> from the DNS. I've now removed the checkmark, so records will not be
> removed when a lease expires, but now I expect my DNS to be littered
> with useless entries.
Scavenging is not based on when the lease expires, it is based on the
timestamp of when the record was last refreshed. If the Lease is set to
never expire, the record will be scavenged and not reregistered because
registration takes place when the lease is renewed.
What is the DHCP lease time?
--
Best regards,
Kevin D. 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/
http://support.wftx.us/
http://message.wftx.us/
===================================
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
===================================
|
|
I have two subnets: for one, the lease is 24 hours, on the second, it is
30 days. I've lost records on both subnets.
How can I make sure that the record refresh themselves regularly?
Remember, these are linux boxes that are affected.
Max
Kevin D. Goodknecht Sr. [MVP] wrote:
[Quoted Text] > Read inline please. > > In news:O4%23oSJDZJHA.556[ at ]TK2MSFTNGP06.phx.gbl, > atomax[ at ]nospam.nospam <atomax[ at ]gmail.com> wrote: >> I have it configured for secure and non-secure dynamic updates >> >> Scavenging is set for 7 days. >> >> All records are set to dynamically update the DNS always. >> >> Also, I have credentials configured on the DHCP service. >> >> I've looked at the Technet article you referenced. It has lots of >> useful information, but doesn't seem to address my issue, which is >> that computers whose leases should not be expiring are being removed >> from the DNS. I've now removed the checkmark, so records will not be >> removed when a lease expires, but now I expect my DNS to be littered >> with useless entries. > > > Scavenging is not based on when the lease expires, it is based on the > timestamp of when the record was last refreshed. If the Lease is set to > never expire, the record will be scavenged and not reregistered because > registration takes place when the lease is renewed. > What is the DHCP lease time? > > > > |
|
In news:umMcTBlZJHA.1268[ at ]TK2MSFTNGP04.phx.gbl,
atomax[ at ]nospam.nospam <atomax[ at ]gmail.com> requesting assistance, typed the
following:
[Quoted Text] > I have two subnets: for one, the lease is 24 hours, on the second, it
> is 30 days. I've lost records on both subnets.
> How can I make sure that the record refresh themselves regularly?
> Remember, these are linux boxes that are affected.
>
> Max
>
I'm surprised it's not affecting all machines. The lease time is too short
based on the scavenging time. Keep in mind, the refresh period for a lease
of 24 hours is 12 hours (50% of the elast time). Although not directly
related to the least time, as Kevin pointed out, however the lease time
cannot be shorter than the scavenge time based on the refresh period based
on the way scavenging works. A DHCP client will get it's record refresh at
time of lease refresh, which in your case is 12 hours with a 24 hour lease
setting.
Look at this link. Use the search feature in the browser to search for the
section on "scavenging" to better understand the relationship between DNS
scavenging and DHCP lease time lengths. This assumes you understand how DHCP
lease renewal works (the 50% of lease time renewal and the 87.5% of lease
time renewal if it didn't get it renewed at the 50% mark):
http://technet.microsoft.com/en-us/library/bb742582.aspx
My bet is if the lease time was set to the default 8 days, or rather both
the scavenge time and lease times were set to default, you would not be
seeing this behavior.
Look at this link. Scroll down to the chart showing the relationship between
the scavenge period, the no-refresh, and the refresh period
http://blogs.technet.com/networking/archive/2008/03/19/don-t-be-afraid-of-dns-scavenging-just-be-patient.aspx
If you set the lease time for 24 hours to accomodate laptop renewals, I can
understand why you would think this would work. However there are
complications with scavenging, as well as with WINS, especially if there are
WINS partners. WINS in a larger environment, depending on the WINS
partnership setup, with using shorter DHCP lease times, can cause problems
and may not reflect the latest record registration. Basically it just can't
keep up if partnerships and lease times are not configured properly.
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT
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.
|
|
|