Re: Why adding secondary IP to NIC of DNS servers failed ?
- From: "Greg Lindsay [MSFT]" <greg.lindsay@xxxxxxxxxxxxx>
- Date: Mon, 31 Jul 2006 16:28:16 -0700
Configuration of the TCP/IP settings for IP address and DNS are independent.
You can have a static IP address, but still select "Obtain DNS server
address automatically", and vice-versa.
Make sure you have both set to static (and have the correct addresses) if
you aren't using DHCP. Later when you switch to DHCP, make sure to switch
both again.
I hope this helps!
--
Greg Lindsay [MSFT]
greg.lindsay@xxxxxxxxxxxxx
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
"Marlon Brown" <MarlonBrown@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:umpOAKPtGHA.4140@xxxxxxxxxxxxxxxxxxxxxxx
On MyApplicationServer on the network 1.0.0.0, here is the IP address
configuration:
The servers which freaked out are all under static IP address
configuration. It is true folks are testing a new DHCP server on given
networks, but since our servers point to static IP address, I think that
is unrelated.
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 1.0.0.200
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 1.0.0.254
DNS Servers . . . . . . . . . . . : 200.1.1.2 (note it is pointing to the
original DNS IP address)
200.1.1.1
Primary WINS Server . . . . . Wrong IP ( I don't think this is related to
the DNS issue, but I noticed that WINS IP existing there is invalid)
Secondary WINS Server . . . Wrong IP
"Greg Lindsay [MSFT]" <greg.lindsay@xxxxxxxxxxxxx> wrote in message
news:u4%23nqnOtGHA.4968@xxxxxxxxxxxxxxxxxxxxxxx
Are the people on other networks using a different DHCP server?
What is the order of the preferred DNS servers being sent to clients on
the 200.1.1.x network?
--
Greg Lindsay [MSFT]
greg.lindsay@xxxxxxxxxxxxx
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
"Marlon Brown" <MarlonBrown@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ea3NWiLtGHA.1888@xxxxxxxxxxxxxxxxxxxxxxx
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: Marlon Brown
- Re: Why adding secondary IP to NIC of DNS servers failed ?
- References:
- Why adding secondary IP to NIC of DNS servers failed ?
- From: Marlon Brown
- 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 ?
- From: Marlon Brown
- Why adding secondary IP to NIC of DNS servers failed ?
- Prev by Date: Re: Why adding secondary IP to NIC of DNS servers failed ?
- Next by Date: Re: Name Servers
- Previous by thread: Re: Why adding secondary IP to NIC of DNS servers failed ?
- Next by thread: Re: Why adding secondary IP to NIC of DNS servers failed ?
- Index(es):
Relevant Pages
|