Dynamic DNS updates not happening

[Brian]

Hi all,

I'm running two DCs, currently with Win2K Server with
about 25 workstations all running win2k at one location.
I am upgrading to Win2003 server. Upon trying to run AMDT
computer account migration, I found that I was having
problems with my existing dns. It wasn't dynamically
updating! I went back and checked EVERYTHING! DHCP and
DNS are both set up for dynamic updates as far as I can
tell (according to my Mastering Win2K server book by
Minasi, and according to all of the KB articles I have
read and re-read this weekend).

Here is the real weird thing, if I look in my reverse
lookup zone, the PTR records ARE getting updated. But the
A records in the forward lookup zone(s) AREN'T!!!

My current, and soon to be retired domain
is "peridianweb", and the new domain that I set up on my
2003 server is "peridiangroup". I set up the DNS zone to
be the same as my AD domain name. I can't get dynamic
updates to run on either my old win2000 server, nor on my
new win2003 server. What gives?

PS If I manually add an A record for a workstation,
everything (nslookup, ping, ADTM) works fine. But that
won't work too good with DHCP now will it!?

Thanks!

[Roger Abell]

There are a few possibilities here, but what seems
most likely is that when you said the old and new
domains are "peridianweb" and "peridiangroup"
you actually did mean that the downlevel/NetBIOS
names and the DNS names are the same.
If so, this is your issue, as after prior service pack
machines will not register names in single-label
DNS domain without making a registry settings.
So, you would need to start over on the new domain
using a domain name at includes an internal "." (at
least one), like peridian.net or peridian.group and
you would need to follow
Clients cannot dynamically register DNS records in a
single-label forward lookup zone
http://support.microsoft.com/?id=826743
for any machine where it is critical that it have A records.

If the above assumption is incorrect, then either the clients
or DHCP, or both (an erroneous config) is configured to
register the A records, or neither are. You seem to indicate
DHCP is and you have confirmed this. If so, try allowing
a client to do so and see if it works - in order to narrow
down where the misconfig is. If a machine that needs to do
registrations is not using a DNS server (in its Tcp/Ip config)
that allows it to locate the SOA for the DNS domain where
a registration should be done, then there will be no registration.
--
Roger Abell
Microsoft MVP (Windows Server System: Security)
MCSE (W2k3,W2k,Nt4) MCDBA
"Brian" <bjahelka...@peridiangroup.com> wrote in message
news:a9cc01c4363a$af72dcc0$a001...@phx.gbl...

[Brian]

Roger thanks for your insight. I actually found that
article (after I posted this) about Win2K workstations not
updating single-name domains after SP4, which I recently
installed, and explains why my dynamic dns updates weren't
happening. I guess I'll dcpromo my win2003 DC back down
and change the domain name over to something with a dot in
it... And run ADMT again... Hope I don't have any
problems cleaning up stuff left over from TWO domains!

Again, THANKS very much for taking the time to reply! I
was banging my head against the monitor for a good 20
hours trying everything I could think of to troubleshoot
before I posted up here. Maybe I should have posted a
little earlier. =)

>.
>

[Roger Abell]

Yea, no problem. That single label issue is a little
hidden to search stings one might at first be trying.

--
Roger
"Brian" <anon...@discussions.microsoft.com> wrote in message
news:acc701c43697$ed2b3550$a101...@phx.gbl...