Computers not refresh DNS entry right away when IP changes

we have computers that are built on a lab subnet, then put into
production when it is finished. we've found that when we move the
computers from one subnet to another, they do not register their -new-
IP address for a few days (there are no problems with the initial
registration, and that is the entry that remains when it is moved)

I'm thinking this might have something to do with the 2003 refresh
interval settings and if so, why not make these values minimal?

what else might i check if not for these settings?

thanks!

- j

"JayDee" <dopamine@mail.com> wrote in message
news:0218dad7-3642-4962-8533-7773ea2224ad@d9g2000prh.googlegroups.com...
> we have computers that are built on a lab subnet, then put into
> production when it is finished. we've found that when we move the
> computers from one subnet to another, they do not register their -new-
> IP address for a few days (there are no problems with the initial
> registration, and that is the entry that remains when it is moved)
>
> I'm thinking this might have something to do with the 2003 refresh
> interval settings and if so, why not make these values minimal?
>
> what else might i check if not for these settings?
>
> thanks!
>
> - j

By default, it should register within 15 minutes. If you are looking at a
DNS server in a different Site, then it will take longer, depending on your
Site replication schedule. If it is not registering until 3 days later, than
something has been changed or altered from the defaults, or the client
machine (if it is a client machine), is not configured properly, such as
using an ISP's DNS, Primary DNS suffix doesn't match, etc.

Are the machines DHCP or static configurations?
When you run an ipconfig /registerdns, does it register within 15 minutes?

Please provide an ipconfig /all from the client machine so we can get a
better idea and evaluate the config.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

Are you just restting via a vLAN change? What happens when you do the
command below from a command prompt?

ipconfig /registerdns

Is the client registering the ip address at the same dns server you are
looking at when you do your nslookup?

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.

"JayDee" <dopamine@mail.com> wrote in message
news:0218dad7-3642-4962-8533-7773ea2224ad@d9g2000prh.googlegroups.com...
> we have computers that are built on a lab subnet, then put into
> production when it is finished. we've found that when we move the
> computers from one subnet to another, they do not register their -new-
> IP address for a few days (there are no problems with the initial
> registration, and that is the entry that remains when it is moved)
>
> I'm thinking this might have something to do with the 2003 refresh
> interval settings and if so, why not make these values minimal?
>
> what else might i check if not for these settings?
>
> thanks!
>
> - j
>
>
>

On Nov 27, 5:23*am, "Paul Bergson [MVP-DS]" <pbbergs@no_spammsn.com>
wrote:
> Are you just restting via a vLAN change? *What happens when you do the
> command below from a command prompt?
>
> ipconfig /registerdns
>
> Is the client registering the ip address at the same dns server you are
> looking at when you do your nslookup?
>
> --
> Paul Bergson
> MVP - Directory Services
> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
> 2008, 2003, 2000 (Early Achiever), NT4
> Microsoft's Thrive IT Pro of the Month - June 2009
>
> http://www.pbbergs.com
>
> Please no e-mails, any questions should be posted in the NewsGroup This
> posting is provided "AS IS" with no warranties, and confers no rights.
>
> "JayDee" <dopam...@mail.com> wrote in message
>
> news:0218dad7-3642-4962-8533-7773ea2224ad@d9g2000prh.googlegroups.com...
>
>
>
> > we have computers that are built on a lab subnet, then put into
> > production when it is finished. we've found that when we move the
> > computers from one subnet to another, they do not register their -new-
> > IP address for a few days (there are no problems with the initial
> > registration, and that is the entry that remains when it is moved)
>
> > I'm thinking this might have something to do with the 2003 refresh
> > interval settings and if so, why not make these values minimal?
>
> > what else might i check if not for these settings?
>
> > thanks!
>
> > - j- Hide quoted text -
>
> - Show quoted text -


we found that if the "old IP" entry is manually removed from DNS, the
server/workstation will then automatically register its new IP
address. But if the old IP entry exists, the machine will not register
automatically and the few times I tested, did not register with /
registerdns either. We've seen this when machines have hardcoded IPs
and DHCP assigned (if the address changes). It has also occured if the
computer is assigned a different IP on the same subnet.
* all workstations always register automatically and correctly if an
existing, inaccurate entry does not exist. since this is the case, i
don't think an ipconfig /all would provide any help.

here are the zone aging/scavenging settings - please tell me if these
settings might have anything to do with these observations and if so,
what other implications would changing their values have.

No refresh Interval: 2 days
Refresh Interval: 8 days

thank you!
- jason

> On Nov 27, 5:23*am, "Paul Bergson [MVP-DS]" <pbbergs@no_spammsn.com>
> wrote:
>> Are you just restting via a vLAN change? *What happens when you do the
>> command below from a command prompt?
>>
>> ipconfig /registerdns
>>
>> Is the client registering the ip address at the same dns server you are
>> looking at when you do your nslookup?
>>
>> --
>> Paul Bergson
>> MVP - Directory Services
>> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
>> 2008, 2003, 2000 (Early Achiever), NT4
>> Microsoft's Thrive IT Pro of the Month - June 2009
>>
>> http://www.pbbergs.com
>>
>> Please no e-mails, any questions should be posted in the NewsGroup This
>> posting is provided "AS IS" with no warranties, and confers no rights.
>>
>> "JayDee" <dopam...@mail.com> wrote in message
>>
>> news:0218dad7-3642-4962-8533-7773ea2224ad@d9g2000prh.googlegroups.com...
>>
>>
>>
>>> we have computers that are built on a lab subnet, then put into
>>> production when it is finished. we've found that when we move the
>>> computers from one subnet to another, they do not register their -new-
>>> IP address for a few days (there are no problems with the initial
>>> registration, and that is the entry that remains when it is moved)
>>> I'm thinking this might have something to do with the 2003 refresh
>>> interval settings and if so, why not make these values minimal?
>>> what else might i check if not for these settings?
>>> thanks!
>>
>>> - j- Hide quoted text -
>>
>> - Show quoted text -
>
>
> we found that if the "old IP" entry is manually removed from DNS, the
> server/workstation will then automatically register its new IP
> address. But if the old IP entry exists, the machine will not register
> automatically and the few times I tested, did not register with /
> registerdns either. We've seen this when machines have hardcoded IPs
> and DHCP assigned (if the address changes). It has also occured if the
> computer is assigned a different IP on the same subnet.
> * all workstations always register automatically and correctly if an
> existing, inaccurate entry does not exist. since this is the case, i
> don't think an ipconfig /all would provide any help.
>
> here are the zone aging/scavenging settings - please tell me if these
> settings might have anything to do with these observations and if so,
> what other implications would changing their values have.
>
> No refresh Interval: 2 days
> Refresh Interval: 8 days
>
> thank you!
> - jason

Actually the ipconfig /all helps. There's more info in the results than
you are aware of. What do we look for with an ipconfig /all?

1. Primary DNS Suffix. Does it match the zone name in DNS?
2. Search Suffix. Should match the Primary DNS Suffix.
3. DNS entries. Do those DNS servers exist, and if they do, do they
host the zone (that matches the Primary DNS SUffix) or have a reference
to it (secondaries or stubs)?
4. IP Routing configured?
5. WINS proxy?
6. If a DC, we look at all the above, plus if there are multiple NICs
and/or IP addresses.

All this and we assume the zone allows updates.

What else we ask for is how the DNS infrastructure is setup, if the DNS
addresses on a client (whether DHCP or static) are using a DNS server
in its own site or another site, or mixed.

So there's a lot of info that needs to be evaluated to determine why a
machine is not registering into DNS.

You can obsfucate your domain name for security, but I assume you are
using private IPs, so there's no reason to hide that part.

I see you moved away from the scavenging defaults. Any reason why? They
should be even, and should be one day + over the DHCP lease period.
What's your lease period? If you put them back to default, does it
work?

Have you configured DHCP to own records it has registered? This action
allows a DHCP server to update a record, as long as DHCP is configured
to force update of clients, whether they are able to do it on their own
or not. This way all records will be updated. If you are toggling it
back and forth between static and DHCP to test it, and this is setup or
not setup, will taint your results.

I can understand being prudent and security conscientious. I hope the
info I provided helps you to determine where the problem lies.


Ace

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit
among responding engineers, and to help others benefit from your
resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.