Why adding secondary IP to NIC of DNS servers failed ?
- From: "Marlon Brown" <MarlonBrown@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 31 Jul 2006 08:47:06 -0700
This is the situation:
DNS-ADI-WINS1 = IP=200.1.1.1
DNS-ADI-WINS2 = IP=200.1.1.2
I will have to replace DNS-ADI-WINS1 IP addresses by IP=1.0.0.1 and 1.0.0.2
respectively.
What I did:
I added the IP addresses to the NIC of the DNS servers. That way addresses
200.1.1.1 and 1.0.0.1 coexist. I did that so people could start updating
firewall rules, static member server IP addresses, DHCP scope to point to
the new DNS IP addresses 10.0.0.x. At scheduled date I would remove the
200.1.1.1 addresses from the NIC of the respective DNS-ADI-WINS servers.
Problem:
After adding the secondary 1.x.x.x IP addresses to the DNS servers TCP/IP
properties, people with servers on the specific network 200.1.1.x
experienced problems with server resolution. All servers on 200.1.1.1 was
unable to successfully return nslookup queries and locate DNS resources.
Can someone explain what could be causing this ? Servers on other networks
performed OK, only the ones on the same network than the DNS servers
.
- Follow-Ups:
- Re: Why adding secondary IP to NIC of DNS servers failed ?
- From: Greg Lindsay [MSFT]
- Re: Why adding secondary IP to NIC of DNS servers failed ?
- Prev by Date: Can't Ping DNS name wich resosles to a public IP
- Next by Date: Re: Can I add additional IP address to DNS Server TCP/IP and keep using it ?
- Previous by thread: Can't Ping DNS name wich resosles to a public IP
- Next by thread: Re: Why adding secondary IP to NIC of DNS servers failed ?
- Index(es):
Relevant Pages
|
