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



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: Help with initial small org AD setup convention when using DMZ network
    ... Consider using Dynamic DNS internally (aka Active Directory Integrated ... > firewall which then connects the public IP dmz network to a private IP ... > domain name for such subnets based on the nearest airport code, ... > servers to serve acme.com names for external users. ...
    (microsoft.public.win2000.active_directory)
  • Re: Change IP subnet for a site
    ... > The only problem being that the network is part of a private network in ... > clients are connected, but I have to allow for the possibility that they ... >>> servers. ... >>> DNS to ensure proper DNS registration. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Dcidag errors
    ... Port blockage between servers ... Other sorts of networking issues (lack of connectivity between the points ... These errors are typically a result of a network connectivity issue of some ... > replicating this nc. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Creating a new AD
    ... "Jorge Silva" wrote: ... I have pulled this setup from a different network and want to configure it ... I tried to change the ip setup on all these servers and restarted dns and ... i did a dnsflush and dns register and i am still not ...
    (microsoft.public.windows.server.active_directory)
  • Re: Creating a new AD
    ... MCSE, MVP Directory Services ... I have pulled this setup from a different network and want to configure it ... I tried to change the ip setup on all these servers and restarted dns and ... i did a dnsflush and dns register and i am still not ...
    (microsoft.public.windows.server.active_directory)