Multiple NIC's in DNS server causes invalid IP in DomainDNSZones

Good morning,

We're having an interesting problem with Weblogic interaction with Active
Directory. I think it's a DNS issue, however please redirect me to other
groups if need be. I'm not cross posting, since that's just plain rude!

Active Directory Description: We have 3 sites, with one domain controller
in each site. We are a single domain structure.

DC description: Each domain controller is running Windows 2003, and they
were all UPGRADED from Windows 2000. Each DC also serves as a DNS server.
We have not created a directory partition for DomainDNSZones or
ForestDNSZones. No DC is at SP1.

Problem: Weblogic is using Active Directory as the LDAP structure for
authentication. We're having a problem in that queries for groups is taking
a painfully long time. After some network sniffing, we've found that
Weblogic performs a lookup on DomainDNSZones.domain.com to find an LDAP
server to talk to. When we do a DNS lookup on DomainDNSZones.domain.com,
the backup NIC for one of our domain controllers shows in the list. Since
there is no gateway for that NIC, and the segment is nonroutable, the LDAP
queries fail when that IP (10.1.99.*) comes up first in the list. This
causes Weblogic to spin for some time before failing to the next server in
the list. Since the other three servers in the list are valid, it works
after that.

The workaround for now is to disable the secondary NIC in the problem child
DC. However, we'd like to keep that NIC active for backup purposes, but not
have it tied into the DomainDNSZones. Is there a way to do that?

If I've left any information out, or any further information would help,
please let me know.

Thanks in advance,

Matt Nowell


.

Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... One thought, when you introduced the Windows Server 2008 and before making them DC's, did you extend the schema on the SBS 2003 server? ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: Big trouble with DC in China
    ... > Since then, this server has so may errors in the event logs (KCC, ... > DNS, FRS) that I wouldnt know where to start. ... > Source domain controller address: ...
    (microsoft.public.windows.server.active_directory)