DNS Multihomed timeout

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a very weird problem
I have 2 NIC. One for our Lan: 192.168.100.x an
one for our Internet Connection: 192.168.1.
We are running AD. WIth the INet connection turn off, DNS runs just fine. It forwards all requests not for the local network to the ISP DNS server.
With the connection turned on our DNS times out when looking for a address outside of our network
I can see that the request are going to both network cards. I have set DNS to only listen on the 100.x address
Disabled the external card from registering into DNS, though it still does this
NSlookup times out as well unless I use the parameter -timeout=10. Anything shorter won't work
Binding is set for Internal then External
Any help will be much appreciated
 
In
Dan Grover said:
I have a very weird problem.
I have 2 NIC. One for our Lan: 192.168.100.x and
one for our Internet Connection: 192.168.1.x
We are running AD. WIth the INet connection turn off, DNS runs just
fine. It forwards all requests not for the local network to the ISP
DNS server. With the connection turned on our DNS times out when
looking for a address outside of our network.
I can see that the request are going to both network cards. I have
set DNS to only listen on the 100.x address.
Disabled the external card from registering into DNS, though it still
does this.
NSlookup times out as well unless I use the parameter -timeout=10.
Anything shorter won't work.
Binding is set for Internal then External.
Any help will be much appreciated.
Click to expand...


Problem is DNS will always reg itself to identify itself if it's a DNS
server on all interfaces. Hopefully this machine is NOT a domain controller.
If so, there are other registry entries to muck with.

Carefully select the interface in the reg and disable that interface and
follow the article below.

275554 - The Host's A Record Is Registered in DNS After You Choose Not to
Register the Connection's Address [Because it's a DNS server]:
http://support.microsoft.com/?id=275554

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
Unfortunately it is a DC. I have no fear of editing the registry
Any additional help will be appreciated

----- Ace Fekay [MVP] wrote: ----

In
Dan Grover said:
I have a very weird problem
I have 2 NIC. One for our Lan: 192.168.100.x an
one for our Internet Connection: 192.168.1.
We are running AD. WIth the INet connection turn off, DNS runs jus
fine. It forwards all requests not for the local network to the IS
DNS server. With the connection turned on our DNS times out whe
looking for a address outside of our network
I can see that the request are going to both network cards. I hav
set DNS to only listen on the 100.x address
Disabled the external card from registering into DNS, though it stil
does this
NSlookup times out as well unless I use the parameter -timeout=10
Anything shorter won't work
Binding is set for Internal then External
Any help will be much appreciated
Click to expand...


Problem is DNS will always reg itself to identify itself if it's a DN
server on all interfaces. Hopefully this machine is NOT a domain controller
If so, there are other registry entries to muck with

Carefully select the interface in the reg and disable that interface an
follow the article below

275554 - The Host's A Record Is Registered in DNS After You Choose Not t
Register the Connection's Address [Because it's a DNS server]
http://support.microsoft.com/?id=27555

--
Regards
Ac

Please direct all replies to the newsgroup so all can benefit
This posting is provided "AS-IS" with no warranties and confers n
rights

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MV
Microsoft Windows MVP - Active Director

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for
pig. --
================================
 
In
Dan Grover said:
Unfortunately it is a DC. I have no fear of editing the registry.
Any additional help will be appreciated.
Click to expand...

Here's a repost that will help:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This will work to avoid that "Blank Domain FQDN" (as I call it) Private IP
that you don't want to register.

This is assuming the machine is also a GC. If not, don't worry about the
GcIpAddress part.

1.You need to disable the local IP address registration without stopping
netlogon from registering SRVs. Otherwise, you'll create a blank domain FQDN
with the external IP and delete the internal private IP just to find that
netlogon will re-register promptly every 60 minutes.
This will take care of that:
(taken from http://support.microsoft.com/?id=295328)
To disable only the registration of the local IP addresses, set the
following registry value:
Key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters

Registry value: DnsAvoidRegisterRecords
Data type: REG_MULTI_SZ
Values: LdapIpAddress
GcIpAddress

2. Then manually create the GC address that you want and the LdapIpAddress
of the interface you want to show up in DNS.

~~~~~~~~~~~~~~~~~~~~~~

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
Back
Top