Name Server cycling ip addresses

  • Thread starter Thread starter Mike K.
  • Start date Start date
M

Mike K.

I have a DNS Server with 2 Nics.
One is for the local network and I'm using ICS on it, so it gets the address
192.168.0.1
The second has 2 ips, internet ips on a live connection.
I'm hosting my domain site on the same pc but I get problems because when I
nslookup my server I get the tree ips... ipexternal.1, ipexternal.2 and
192.168.0.1. (it is an active directory zone).
Every time I nslookup the order changes.... ipexternal2, ipexternal1,
192.168.0.1. or 192.168.0.1, ipexternal1, ipexternal2.
My domain is registered under ipexternal1, so if not the first case is
true... my address is not resolved correctly and my domain is not found!
I tried to say to dns to listen only on the ipexternal1 and still in my A
records I had name server ips the other two.... Every time I reload the zone
manually, it is getting back to the ipexternal1, but after sometime the name
server is pointing to ipexternal2 and 192.168.0.1.
I even disabled round robin but nothing changed.
I alse use DHCP on the local network and I have set 192.168.0.1 as the
gateway and ipexternal1 as the name server.

Any ideas?
TIA

Mike
 
In
Mike K. said:
I have a DNS Server with 2 Nics.
One is for the local network and I'm using ICS on it, so it gets the
address 192.168.0.1
Click to expand...

You cannot use ICS with either DNS or DHCP you need to disable ICS and
configure NAT in RRAS.
If you are running a web site you need to map incoming connections on port
80 to the web site address. If the Web site is on the DC in IIS configure
your web site to listen on its internal IP then map port 80 to that address.
The second has 2 ips, internet ips on a live connection.
I'm hosting my domain site on the same pc but I get problems because
when I nslookup my server I get the tree ips... ipexternal.1,
ipexternal.2 and 192.168.0.1. (it is an active directory zone).
Every time I nslookup the order changes.... ipexternal2, ipexternal1,
192.168.0.1. or 192.168.0.1, ipexternal1, ipexternal2.
My domain is registered under ipexternal1, so if not the first case is
true... my address is not resolved correctly and my domain is not
found!
Click to expand...

You could have serveral problems with your setup especially since this is a
DC. But what you should do is have DNS listen only on the internal IP,
disable the registration of the "A" records and manually add the private
records you need. Basically you need to get rid of the public addresses in
DNS especially for the LDAP IP addresses because LDAP won't traverse NAT.

Also, since you have two NICs you need to make sure that the internal NIC is
at the top of the binding order and that File Sharing and Client for MS
Networks is only bound on it.
For that you need to use the Network and Dial up connections Control Panel,
Advanced Menu, Advanced settings to see your bindings and binding order.

Remember one important rule in an AD environment, all NICs on all machines
in an AD domain MUST point only to the internal DNS server, including the
DNS server machine.

Take a look at these:
300202 - HOW TO Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202&FR=1

246804 - How to Enable/Disable Windows 2000 Dynamic DNS Registrations
http://support.microsoft.com/default.aspx?scid=kb;EN-US;246804&FR=1

272294 - Active Directory Communication Fails on Multihomed Domain
Controllers
http://support.microsoft.com/default.aspx?scid=kb;en-us;272294&FR=1

295328 - Private Network Interfaces on a Domain Controller Are Registered in
DNS
http://support.microsoft.com/?id=295328&FR=1
 
Back
Top