DNS entry keeps changing on it's own.
I have a network with 6 Wk2003 and 2ea. w2k8 servers. One of my older W2k3 servers is acting as my internal DNS server. I have an entry for this server in the forward lookup zones for my domain. Each day, about every 6 hours or so it changes the IP address. Let me explain further.
This server was a proxy server with 3 nics. 1ea. for the Internet, 1ea. for network A and 1ea. for network B. It's IP was 192.168.1.1 as it was the gateway. I've since installed a router that does this routing for me and this server is now only acting as a DNS server. Although there are other services running on it (leftover) DNS is all that's really needed. I have entries for each server and it's associated address, including this server. And although I've changed the IP from 192.168.1.1 to 192.168.1.2, the server entry in the forward lookup zone periodically changes BACK to 192.168.1.1. Any ideas? It's throwing my internal network for a loop as it's periodically loosing it's DNS server in essence.
This server was a proxy server with 3 nics. 1ea. for the Internet, 1ea. for network A and 1ea. for network B. It's IP was 192.168.1.1 as it was the gateway. I've since installed a router that does this routing for me and this server is now only acting as a DNS server. Although there are other services running on it (leftover) DNS is all that's really needed. I have entries for each server and it's associated address, including this server. And although I've changed the IP from 192.168.1.1 to 192.168.1.2, the server entry in the forward lookup zone periodically changes BACK to 192.168.1.1. Any ideas? It's throwing my internal network for a loop as it's periodically loosing it's DNS server in essence.
ASKER
Do I nee to remove the other nics or ca you give me the directions needed. Keep in mind that I already have an entry for this server at 1.1 and it keeps changing automatically to 1.2 multiple times a day.
Thanks for your help.
Thanks for your help.
You do not have to remove the other nics, you could disable then or on the TCP/IP advanced properties chose dns and then make sure register this connection is not marked.
ASKER
I disabled the other two nic's and deselected 'register this connection' on both.
I'm still not clear on how or why this address could have changed on it's own with the DNS table.
I'm still not clear on how or why this address could have changed on it's own with the DNS table.
Each network card will try to register in dns so one first then the other, we had this problem on our citrix server they started fine and then the management card registered with antoher ip adres.
ASKER
Issue remains. Any other ideas?
Thx.
Thx.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You must only set this on the connector with IP adres 192.168.1.2. The other network cards should not register in dns.