Issues with NIC registering in DNS when it shouldnt

Windows 2003 R2 SP2 Enterprise edition, Domain controller, GC/DNS all FSMO
roles.

This article states the basic problem:
http://support.microsoft.com/kb/832478/en-us

My DLL's are 5.2.3790.3959 for netlogon.dll and dnsapi.dll

Have a Dell 1950 with 4 NIC's
- two broadcom II's teamed as the LAN on a 10.0.x.x segment
- two Intels teamed as iSCSI on a 172.16.x.x segment

All four plugged to same Cisco switch, but separated via VLANs.

There is an additional domain controller on the 10.0.x.x segment, but it
does not have any NIC's on the 172.16.x.x segment, so I do not think that it
could be involved.

On the iSCSI team, register this connection with DNS is unchecked.

Things I have tried:
- manual add a DNS suffix that doesn't match the AD
- manually remove the rougue DNS entry and increment the SOA (comes back in
a few minutes)
- Called MS with the KB article above, they confirmed that the hotfix
mentioned was rolled into SP2.
- I have turned on DNS debugging, and do not seem to see an event
registering the 172 address in DNS.
- netlogon.dns does NOT have any references to 172.16.x.x segment

Any help?

Chris





Chris Lehr

Not 5 minutes after I posted - I realized that DNS on this server was
listening on both IP's.

Bound to only one now, but I think typing this all out forced me to think it
through.

Thanks for reading/replying, even if just to laugh at me.


"Chris Lehr" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Windows 2003 R2 SP2 Enterprise edition, Domain controller, GC/DNS all FSMO
> roles.
>
> This article states the basic problem:
> http://support.microsoft.com/kb/832478/en-us
>
> My DLL's are 5.2.3790.3959 for netlogon.dll and dnsapi.dll
>
> Have a Dell 1950 with 4 NIC's
> - two broadcom II's teamed as the LAN on a 10.0.x.x segment
> - two Intels teamed as iSCSI on a 172.16.x.x segment
>
> All four plugged to same Cisco switch, but separated via VLANs.
>
> There is an additional domain controller on the 10.0.x.x segment, but it
> does not have any NIC's on the 172.16.x.x segment, so I do not think that
> it could be involved.
>
> On the iSCSI team, register this connection with DNS is unchecked.
>
> Things I have tried:
> - manual add a DNS suffix that doesn't match the AD
> - manually remove the rougue DNS entry and increment the SOA (comes back
> in a few minutes)
> - Called MS with the KB article above, they confirmed that the hotfix
> mentioned was rolled into SP2.
> - I have turned on DNS debugging, and do not seem to see an event
> registering the 172 address in DNS.
> - netlogon.dns does NOT have any references to 172.16.x.x segment
>
> Any help?
>
> Chris
>
>
>

On Apr 30, 11:56 am, "Chris Lehr" <chris.l...@gmail.com> wrote:
> Not 5 minutes after I posted - I realized that DNS on this server was
> listening on both IP's.
>
> Bound to only one now, but I think typing this all out forced me to think it
> through.
>
> Thanks for reading/replying, even if just to laugh at me.
>
> "Chris Lehr" <chris.l...@gmail.com> wrote in message
>
> news:(E-Mail Removed)...
>
>
>
> > Windows 2003 R2 SP2 Enterprise edition, Domain controller, GC/DNS all FSMO
> > roles.
>
> > This article states the basic problem:
> >http://support.microsoft.com/kb/832478/en-us
>
> > My DLL's are 5.2.3790.3959 for netlogon.dll and dnsapi.dll
>
> > Have a Dell 1950 with 4 NIC's
> > - two broadcom II's teamed as the LAN on a 10.0.x.x segment
> > - two Intels teamed as iSCSI on a 172.16.x.x segment
>
> > All four plugged to same Cisco switch, but separated via VLANs.
>
> > There is an additional domain controller on the 10.0.x.x segment, but it
> > does not have any NIC's on the 172.16.x.x segment, so I do not think that
> > it could be involved.
>
> > On the iSCSI team, register this connection with DNS is unchecked.
>
> > Things I have tried:
> > - manual add a DNS suffix that doesn't match the AD
> > - manually remove the rougue DNS entry and increment the SOA (comes back
> > in a few minutes)
> > - Called MS with the KB article above, they confirmed that the hotfix
> > mentioned was rolled into SP2.
> > - I have turned on DNS debugging, and do not seem to see an event
> > registering the 172 address in DNS.
> > - netlogon.dns does NOT have any references to 172.16.x.x segment
>
> > Any help?
>
> > Chris- Hide quoted text -
>
> - Show quoted text -

ROFL.. You suck.