Re: Multiple NIC's in DNS server causes invalid IP in DomainDNSZones
- From: "WorkingHard" <WorkingHard@xxxxxxxxxxxxxx>
- Date: Thu, 29 Dec 2005 22:48:32 +0100
http://support.microsoft.com/?id=246804
Now beware ... you'll need to manage the valid registrations manually if you
start with this (do a google for possible WINS and DHCP services issues when
running them on multihomed servers ...
It takes some configuring and experimenting but you can get dual homes
servers DC etc ... to work, but it wil not allways be easy and /or but it
depends on what you are trying to achieve ...
"Matt Nowell" <mdnowell@xxxxxxxxxxxxxxxxxxx> wrote in message
news:%23tg46xLDGHA.2320@xxxxxxxxxxxxxxxxxxxxxxx
> 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
>
.
- References:
- Multiple NIC's in DNS server causes invalid IP in DomainDNSZones
- From: Matt Nowell
- Multiple NIC's in DNS server causes invalid IP in DomainDNSZones
- Prev by Date: Multiple NIC's in DNS server causes invalid IP in DomainDNSZones
- Next by Date: Re: Multiple NIC's in DNS server causes invalid IP in DomainDNSZones
- Previous by thread: Multiple NIC's in DNS server causes invalid IP in DomainDNSZones
- Next by thread: Re: Multiple NIC's in DNS server causes invalid IP in DomainDNSZones
- Index(es):
Relevant Pages
|