Greetings,

Roughly three weeks ago we have had printers in our environment
configured with hostnames set to DHCP dropping out of DNS. We can
still ping the printers as the IP address still resides in WINS, but
they no longer reside in DNS at all. If we power cycle the printer/jet
direct and/or change the hostname slightly it will reregister in DNS.
We are running Windows 2003 servers which are set to dynamically update
IP addresses within our environment. We are not having this issue with
our PC's at all just our printers. With the majority of our printers
being HP, I called HP to see if there is a setting on the printer that
could changed the way it's hostname and IP are registered in DNS.
According to HP, there isn't. This makes sense as we haven't made any
changes to our printers system wide so this wouldn't explain why it
just started happening all at once. If anyone has any thoughts on this
matter, please let me know.

Just a thought... any chance someone changed the "Aging" setting to Scavenge
Stale Resource Records?

-Frank

<joshanderson40@gmail.com> wrote in message
news:1157391950.874106.59890@m73g2000cwd.googlegro ups.com...
> Greetings,
>
> Roughly three weeks ago we have had printers in our environment
> configured with hostnames set to DHCP dropping out of DNS. We can
> still ping the printers as the IP address still resides in WINS, but
> they no longer reside in DNS at all. If we power cycle the printer/jet
> direct and/or change the hostname slightly it will reregister in DNS.
> We are running Windows 2003 servers which are set to dynamically update
> IP addresses within our environment. We are not having this issue with
> our PC's at all just our printers. With the majority of our printers
> being HP, I called HP to see if there is a setting on the printer that
> could changed the way it's hostname and IP are registered in DNS.
> According to HP, there isn't. This makes sense as we haven't made any
> changes to our printers system wide so this wouldn't explain why it
> just started happening all at once. If anyone has any thoughts on this
> matter, please let me know.
>

I would guess that the entries were generated when the printers were first
turned on, and three weeks ago, someone enabled scavenging on your DNS zones
which removed old entries that hadn't been updated in a while.

There are several DNS-related options for your DHCP server. In your DHCP
console, right-click the server / Properties / DNS. The third check-box
probably needs enabled, "Dynamically update DNS A and PTR records for DHCP
clients that do not request updates"

Regards,
Jeremy Carter



<joshanderson40@gmail.com> wrote in message
news:1157391950.874106.59890@m73g2000cwd.googlegro ups.com...
> Greetings,
>
> Roughly three weeks ago we have had printers in our environment
> configured with hostnames set to DHCP dropping out of DNS. We can
> still ping the printers as the IP address still resides in WINS, but
> they no longer reside in DNS at all. If we power cycle the printer/jet
> direct and/or change the hostname slightly it will reregister in DNS.
> We are running Windows 2003 servers which are set to dynamically update
> IP addresses within our environment. We are not having this issue with
> our PC's at all just our printers. With the majority of our printers
> being HP, I called HP to see if there is a setting on the printer that
> could changed the way it's hostname and IP are registered in DNS.
> According to HP, there isn't. This makes sense as we haven't made any
> changes to our printers system wide so this wouldn't explain why it
> just started happening all at once. If anyone has any thoughts on this
> matter, please let me know.
>

Thanks for the reply Frank. No, the "aging" setting has not been
changed in over a year.


Frankster wrote:
> Just a thought... any chance someone changed the "Aging" setting to Scavenge
> Stale Resource Records?
>
> -Frank
>
> <joshanderson40@gmail.com> wrote in message
> news:1157391950.874106.59890@m73g2000cwd.googlegro ups.com...
> > Greetings,
> >
> > Roughly three weeks ago we have had printers in our environment
> > configured with hostnames set to DHCP dropping out of DNS. We can
> > still ping the printers as the IP address still resides in WINS, but
> > they no longer reside in DNS at all. If we power cycle the printer/jet
> > direct and/or change the hostname slightly it will reregister in DNS.
> > We are running Windows 2003 servers which are set to dynamically update
> > IP addresses within our environment. We are not having this issue with
> > our PC's at all just our printers. With the majority of our printers
> > being HP, I called HP to see if there is a setting on the printer that
> > could changed the way it's hostname and IP are registered in DNS.
> > According to HP, there isn't. This makes sense as we haven't made any
> > changes to our printers system wide so this wouldn't explain why it
> > just started happening all at once. If anyone has any thoughts on this
> > matter, please let me know.
> >

Thanks for the reply Jeremy. As I stated to Frank the scavenging
setting has not been changed in over a year. We do have the
"dynamically update" setting checked already and it is still happening.


Jeremy Carter wrote:
> I would guess that the entries were generated when the printers were first
> turned on, and three weeks ago, someone enabled scavenging on your DNS zones
> which removed old entries that hadn't been updated in a while.
>
> There are several DNS-related options for your DHCP server. In your DHCP
> console, right-click the server / Properties / DNS. The third check-box
> probably needs enabled, "Dynamically update DNS A and PTR records for DHCP
> clients that do not request updates"
>
> Regards,
> Jeremy Carter
>
>
>
> <joshanderson40@gmail.com> wrote in message
> news:1157391950.874106.59890@m73g2000cwd.googlegro ups.com...
> > Greetings,
> >
> > Roughly three weeks ago we have had printers in our environment
> > configured with hostnames set to DHCP dropping out of DNS. We can
> > still ping the printers as the IP address still resides in WINS, but
> > they no longer reside in DNS at all. If we power cycle the printer/jet
> > direct and/or change the hostname slightly it will reregister in DNS.
> > We are running Windows 2003 servers which are set to dynamically update
> > IP addresses within our environment. We are not having this issue with
> > our PC's at all just our printers. With the majority of our printers
> > being HP, I called HP to see if there is a setting on the printer that
> > could changed the way it's hostname and IP are registered in DNS.
> > According to HP, there isn't. This makes sense as we haven't made any
> > changes to our printers system wide so this wouldn't explain why it
> > just started happening all at once. If anyone has any thoughts on this
> > matter, please let me know.
> >

Well shux, the easy answer wasn't right.
Just to be thorough, is your environment big enough that someone at another
site could have enabled scavenging on a different server?
Other thoughts -- Did your dhcp server have any authentication problems 3
weeks ago? Maybe the server couldn't contact a DC for some period to
authenticate in order to make updates. Is the DHCP lease duration
exceptionally long? There's always the human factor too. Did someone
fat-finger the delete key?
Jeremy

"Josh" <joshanderson40@gmail.com> wrote in message
news:1157470366.455484.34540@i42g2000cwa.googlegro ups.com...
> Thanks for the reply Jeremy. As I stated to Frank the scavenging
> setting has not been changed in over a year. We do have the
> "dynamically update" setting checked already and it is still happening.

No, our environment isn't so big where someone else could have enabled
scavenging. According to the event logs there weren't any
authentication issues. Our DHCP lease time is 8 days. This has been
happening to multiple printers, across multiple subnets, over the
course of three weeks so I don't think it is the human factor.


Jeremy Carter wrote:
> Well shux, the easy answer wasn't right.
> Just to be thorough, is your environment big enough that someone at another
> site could have enabled scavenging on a different server?
> Other thoughts -- Did your dhcp server have any authentication problems 3
> weeks ago? Maybe the server couldn't contact a DC for some period to
> authenticate in order to make updates. Is the DHCP lease duration
> exceptionally long? There's always the human factor too. Did someone
> fat-finger the delete key?
> Jeremy
>
> "Josh" <joshanderson40@gmail.com> wrote in message
> news:1157470366.455484.34540@i42g2000cwa.googlegro ups.com...
> > Thanks for the reply Jeremy. As I stated to Frank the scavenging
> > setting has not been changed in over a year. We do have the
> > "dynamically update" setting checked already and it is still happening.

Any other suggestions at all?


Josh wrote:
> No, our environment isn't so big where someone else could have enabled
> scavenging. According to the event logs there weren't any
> authentication issues. Our DHCP lease time is 8 days. This has been
> happening to multiple printers, across multiple subnets, over the
> course of three weeks so I don't think it is the human factor.
>
>
> Jeremy Carter wrote:
> > Well shux, the easy answer wasn't right.
> > Just to be thorough, is your environment big enough that someone at another
> > site could have enabled scavenging on a different server?
> > Other thoughts -- Did your dhcp server have any authentication problems 3
> > weeks ago? Maybe the server couldn't contact a DC for some period to
> > authenticate in order to make updates. Is the DHCP lease duration
> > exceptionally long? There's always the human factor too. Did someone
> > fat-finger the delete key?
> > Jeremy
> >
> > "Josh" <joshanderson40@gmail.com> wrote in message
> > news:1157470366.455484.34540@i42g2000cwa.googlegro ups.com...
> > > Thanks for the reply Jeremy. As I stated to Frank the scavenging
> > > setting has not been changed in over a year. We do have the
> > > "dynamically update" setting checked already and it is still happening.