Issues with NIC registering in DNS when it shouldnt

Discussion in 'Server Networking' started by Chris Lehr, Apr 30, 2007.

  1. Chris Lehr

    Chris Lehr Guest

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

    This article states the basic problem:

    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 Lehr, Apr 30, 2007
    1. Advertisements

  2. Chris Lehr

    Chris Lehr Guest

    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

    Thanks for reading/replying, even if just to laugh at me. :)
    Chris Lehr, Apr 30, 2007
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.