dns/dhcp odd issue with 2003 server.. dns entry not being updated

I have 2 DHCP servers.. each with the same address scope, but exclusions set
on each one to make them seperate... I also have 3 DNS servers as of now
(soon to become 1)..

In DHCP I have the DNS servers ip addresses set in the scope so end users
get dns working ok...

i've also set the option in dhcp under the main server properties..
Advanced.. "Dns dynamic updates registration credentials" button..

To a "domain user" (non admin) in the domain.. (is this correct to do)?

Here is the problem..

DNS wise.. i have a machine that when you ping it.. shows up with the wrong
ip address (192.168.100.112) and obviously doesnt ping.. (the correct ip
should be xxx.24)...

In DHCP serverA.. i see an entry for this workstation (wkst50)..
192.168.100.189 .. this is the ip is wrong obviously
In DHCP serverB.. I see an entry for this workstation (wrkst50)..
192.168.100.24 .. this is the CORRECT ip address..

So it would seem it has 2 different entries in DHCP.. not sure if this part
is an issue or not..

But then in the dns tree.. for A records.. it of course has the entry of
192.168.100.112..

I'm not sure why this isnt updating in DNS from that workstation.. is it the
DHCP user account for credentials i've set (not enough rights)?

I also looked in reverse lookup domain.. i see 4 entries for this same
workstation (.24, .37, .115, .189), not sure if this matters either..

Thanks for any help..

My friend, it sounds like you have a bit of a mess. Im curious what prompted
the setup you have, rather than creating a single range, or creating two
seperate scopes. In my opinion, that is what you should do. Would you mind
sharing the reasoning behind that set up? Im very curious! Thanks!

Sammy

"markm75" wrote:

> I have 2 DHCP servers.. each with the same address scope, but exclusions set
> on each one to make them seperate... I also have 3 DNS servers as of now
> (soon to become 1)..
>
> In DHCP I have the DNS servers ip addresses set in the scope so end users
> get dns working ok...
>
> i've also set the option in dhcp under the main server properties..
> Advanced.. "Dns dynamic updates registration credentials" button..
>
> To a "domain user" (non admin) in the domain.. (is this correct to do)?
>
> Here is the problem..
>
> DNS wise.. i have a machine that when you ping it.. shows up with the wrong
> ip address (192.168.100.112) and obviously doesnt ping.. (the correct ip
> should be xxx.24)...
>
> In DHCP serverA.. i see an entry for this workstation (wkst50)..
> 192.168.100.189 .. this is the ip is wrong obviously
> In DHCP serverB.. I see an entry for this workstation (wrkst50)..
> 192.168.100.24 .. this is the CORRECT ip address..
>
> So it would seem it has 2 different entries in DHCP.. not sure if this part
> is an issue or not..
>
> But then in the dns tree.. for A records.. it of course has the entry of
> 192.168.100.112..
>
> I'm not sure why this isnt updating in DNS from that workstation.. is it the
> DHCP user account for credentials i've set (not enough rights)?
>
> I also looked in reverse lookup domain.. i see 4 entries for this same
> workstation (.24, .37, .115, .189), not sure if this matters either..
>
> Thanks for any help..
>
>

"SeriousSam" wrote:

> My friend, it sounds like you have a bit of a mess. Im curious what prompted
> the setup you have, rather than creating a single range, or creating two
> seperate scopes. In my opinion, that is what you should do. Would you mind
> sharing the reasoning behind that set up? Im very curious! Thanks!
>


According to what i have read, unless i've read incorrectly.. the correct
way to setup DHCP, is to use an 80/20 rule or a 50/50, if using two servers..
to set a scope on each server with the same range, however, you setup
exclusions which essentially create two different ranges on each server,
preventing any issues..

I believe the issue i had was simply a dns hiccup, or lack of scavenging of
stale records (i had never turned on)..

I had the affected workstation issue the /flushdns and then /registerdns,
after i deleted the errant A record and everything was fine.