Re: Why adding secondary IP to NIC of DNS servers failed ?

Just one correction below:

In preparation to the IP address migration to the 1.0.0.x range, I assigned
the IP address inteh 1.0.0.x range to the TCP/IP properties on the
respective DNS01 and DNS02 only. I did not touch application servers or
devices pointing to the server yet.

That said, yes, both DNS01 and DNS02 are configured to listen on "All IP
addresses".
When I added the 1.0.0.x IPs to the respective NICs on the DNS server, than
the application servers and devices on the same network 1.0.0.x experienced
the name resolution issue.

From my AppSvr, which is originally on the 1.0.0.x network, I can
portqry.exe TCP 53 and UDP 53 Ok, pointing to the DNS01 and DNS02 servers
(using original 200.1.1.x range).

If you agree with me that it makes no sense that the addition of the 1.0.0.x
and coexistence of IP's should cause a problem, I will have to focus on the
layer 3 switch to see what's going on.


"Greg Lindsay [MSFT]" <greg.lindsay@xxxxxxxxxxxxx> wrote in message
news:e4E4FratGHA.1504@xxxxxxxxxxxxxxxxxxxxxxx
Let me see if I understand the issue correctly.

You had some DNS servers and application servers on subnet 200.1.1.x and
everything was working fine.
You are planning to migrate this subnet to a new range of addresses:
1.0.0.x. In preparation, you assigned a secondary IP address in the
1.0.0.x range to the interfaces of all the servers (DNS and application
servers).
You also added the new DNS server IP addresses (1.0.0.x range) to the "Use
the following DNS server addresses" list on your application server. If
needed to list more than 2 DNS servers, you used the advanced TCP/IP
settings DNS tab.
After you made these changes, the application server was unable to resolve
DNS names. It's IP address was in the 1.0.0.x range, but the DNS server
it was trying to use was in the 200.1.1.x range.

If all of this is correct, then please tell me:

1) Can you ping the DNS server from the application server?
2) Does the application server show that the interface is assigned 2
addresses, or just 1?

If the application server has just one IP address in the 1.0.0.x range,
then you need to add a 200.1.1.x to it.

I hope I understood this correctly, and I apologize if I am making this
more complicated than it needs to be.

--
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:OHWhUkZtGHA.3912@xxxxxxxxxxxxxxxxxxxxxxx
From a member server MyAppserver which experienced the DNS resolution
issues after DNS01 and DNS02 got the additional IP 1.x.x.x added to the
NIC:

Advanved TCP/IP Settings

DNS Server addresses
200.1.1.2 (note it is pointing to the original DNS IP address)
200.1.1.1


As you can see the member servers were not touched. All I did was adding
the 1.x.x.x. IPs to the TCP/IP properties on the respective DNS Servers
and let the new IP's ready for people to use them if they wanted, while
letting the original 200.x.x.x IP's coexist for few days.




"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote in message
news:%23i6uMzYtGHA.1216@xxxxxxxxxxxxxxxxxxxxxxx
Hi

I hope that you don't mind for me to step in.

I just want to add something:
Check if you have under the dns properties:
netmask ordering selected on advanced tab, and under the interfaces tab
if you have listen for both ipaddress.

--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"Greg Lindsay [MSFT]" <greg.lindsay@xxxxxxxxxxxxx> wrote in message
news:OwOQYWYtGHA.1216@xxxxxxxxxxxxxxxxxxxxxxx
You mean it is input manually with different subnets for DNS and
IP/gateway? When you correct it, does it stay corrected, or return to
the previous values?

I've not heard of this sort of problem before, but perhaps someone else
has. If it's happening on more than one machine, I still think it might
be related to the new DHCP server test. Is it possible that someone
else was messing with the settings?

--
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:O3crZ5XtGHA.4140@xxxxxxxxxxxxxxxxxxxxxxx
I know, but in this case, both IP and DNS information has been input
manually. Any idea what could have caused this ?


"Greg Lindsay [MSFT]" <greg.lindsay@xxxxxxxxxxxxx> wrote in message
news:eVDzAkPtGHA.4748@xxxxxxxxxxxxxxxxxxxxxxx
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




















.

Relevant Pages

  • Re: [RFC] Automated generation of /etc/resolv.conf from the rc.d script
    ... DNS servers we learn from DHCP. ... +# resolv. ... Implement creation of namedforwarders file via /etc/rc.d/resolv ... +as the first DNS server when building of the forwarders file is enabled. ...
    (freebsd-current)
  • Re: Why adding secondary IP to NIC of DNS servers failed ?
    ... network on the 1.0.0.x subnet and some DNS servers on the 200.1.1.x subnet, ... When you added the 1.0.0.x address to the DNS server, ... If you don't have the 1.0.0.x application servers and the 1.0.0.x DNS ... If only the 1.0.0.x network is having trouble, ...
    (microsoft.public.windows.server.dns)
  • Re: Why adding secondary IP to NIC of DNS servers failed ?
    ... I thought you said the 200.1.1.x network was having problems. ... between the 1.0.0.x application servers and the DNS servers? ... Can you ping the DNS server from the application server? ... confers no rights. ...
    (microsoft.public.windows.server.dns)
  • Re: browser redirect prob
    ... >> Another possibility is that the DNS Server in your ... >> TCP/IP Properties may have been changed, to point to the dodgy site ... >> You should check to see what Name Servers have been Assigned to the ... TCP/IP settings for the network adaptor used for the connection. ...
    (uk.people.silversurfers)
  • Re: FRS/DNS/RPC after joining 2003 Servers on 2000 domain
    ... All are GC's but not DNS servers, ... existing 2000 servers as DC's until flaws and dependencies are ... AD-Integrated DNS server, and the other has inherited the WINS ... communication with the new DNS server (DC3). ...
    (microsoft.public.windows.server.dns)