Server IP changing in DNS - how do I stop it?

Under the network card IP properties, you find a check box that states "register this connections IP address" under the DNS properties tab.

Under the DNS Server Properties you can tell DNS what interface to listen on.  If this server is multihomed and has both interfaces listed then it's picking up DNS information from the external NIC also.  If its not multihomed and only has a LAN NIC then somewhere in your LAN is a DNS server providing the MX record.

Try rebooting the server with the network cable connected to a hub not connected to the network.  Does the new MX and Server record stay in the records then?  This will tell you whether the records are coming from an internal source or are just not being saved.

jimshoe

Thanks for the help. The network this Win2000 server is attached to only has 2 machines on it, itself, and a WinXP client.

"Under the network card IP properties, you find a check box that states "register this connections IP address" under the DNS properties tab."

I unchecked this box and it did not help. The server is not multi-homed, only 1 nic. It has an IP of 192.168.0.3. When I register this server in the DNS (installed and running on this server) with this IP address it works fine ie. Outlook will connect to the Exchange server also running on the server. But when I reboot it picks up a completely different IP address.

Any more thoughts?

For Servers it is the norm to allocate set IP addresses and not let APIPA allocate the IP address as is happening in your case. Set the IP address of the server in either the network card (NO DCHP) or in the dns snap-in.
192.x.x.x is a private range which (I would bet) is not the range you are using. There are a few server settings that can be set in DNS snap-in that would help...
Andy

I have the IP address for the server NIC TCP/IP set at 192.168.0.3. My router/gateway to DSL is 192.168.0.1. My DNS setting in both the only client on the network and the server NIC TCP/IP are 4.2.2.1 and 4.2.2.2. My DSL currently uses a dynamic IP address. When I create a server entry in DNS on the server and select the server it resolves the IP address to 192.168.0.3 as it should as that is the IP address of the NIC in the server. But when I reboot the server the server record in DNS resolves to 209.x.x.x, even though the server IP is still 192.168.0.3.

Check the binding order.  Under network connections/advanced properties, verify that tcp is bound to the lan network adapter.

HOW TO: Change the Binding Order in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;266771

OK, here is what to do.

The DNS settings on both the client and server should point to your server.

If you want to resolve internet stuff too, then delete the root zone (the "." - period) on your DNS server - restart the DNS services and set up the Forwarders tab (right-click the servername in DNS management, choose Properties) to point to your ISP's DNS servers.

Also, double check the Interface tab to make sure that DNS is only listening on your internal network.

See what happens.

OK, none of this is working, when I reboot the Win2000 server the Name Server listed in the Forward Loookup Zone picks up a different DNS IP address which prevents my Outlook clients from accessing the Exchange 5.5 server running on the same server.

Can anyone tell me how to stop the Name Server in the Forward Lookup Zone from picking up a different IP address when the system boots?

Can you identify the address?  Does it belong to you or is it your ISP's?

Also, make sure the internal NIC has NO gateway.  DNS should be itself only.  If you are running DHCP, make sure the option for name server is only your DNS address.

External NIC, gateway, DNS and IP supplied by ISP.  Uncheck MS networks, disable NetBIOS over TCP/IP, and uncheck register in DNS.

In DNS:

Expand your server, then the Forward Lookup Zone, then the domain zone.  Right-click the domain zone and select Properties.  On the name servers tab make sure only your server is there.  On the General tab make sure Dynamic updates are set to Secure only.  On Zone transfer tab, make sure the Allow Zone Transfers in UNchecked.  And on the WINS tab, unless you have a WINS server this should be unchecked too.

Now, all this being set/checked, remove the name server entries from the Forward Lookup Zone - you could remove everything in the zone if you want, it will be recreated.

Let me know what you find.

Netman666,


"Also, make sure the internal NIC has NO gateway. "
Done

" DNS should be itself only"
Done

"If you are running DHCP"
Not running DHCP

"External NIC, gateway, DNS and IP supplied by ISP.  Uncheck MS networks, disable NetBIOS over TCP/IP, and uncheck register in DNS"

Done

" Right-click the domain zone and select Properties.  On the name servers tab make sure only your server is there"
Done

"General tab make sure Dynamic updates are set to Secure only"

Done


"On Zone transfer tab, make sure the Allow Zone Transfers in UNchecked."

Done


Good effort but no go. It will not allow me to delete the name server entries from the Forward Lookup Zone.

Also I have discovered something else since posting the last update. Even though all the IP addresses, MX, Name Server, A record, in DNS are 192.168.0.3, when I do a
NSLOOKUP servername it comes back with 219.21.229.199 which has nothing to do with this small network.

This server is registered in your ISP's DNS server isn't it?  Likely as the mailserver for your domain.  If not, are you using a real domain name internally that does exist in the internet cloud?

After testing the IP you provided, it looks like a user node at Yahoo!

In DNS console, if you right-click the servername and select Properties, on the Interfaces tab it should be set to Only the following IP addresses - and your server IP should be all that's there.

Now, try also from a commandline on the server:

ipconfig /flushdns

then

ipconfig /registerdns


With respect to NSLOOKUP, it can be set to use another server as the root for lookups.

Advise.

The DNS supplied by ISP (4.2.2.1 and 4.2.2.2) should be in forwarders of DNS properties, not in the properties for TCP.  

In TCP properties for the LAN NIC,  you should have the servers ip address (192.168.0.3) for DNS Primary and WINS Primary (if running wins on server).  Under advanced, DNS tab, be sure you have the checkbox register this connections address in DNS checked.

If you need a Q article explaining this let me know and I'll look one up.

Let us know the results after you have this correct configuration.

Also, have you rebooted this box since making any of the changes?

"This server is registered in your ISP's DNS server isn't it?  "

No, this is purely a test server on a separate network from company network for developing with SQL Server, though we want it to have internet access we do not want it on the internet and the router it is behind had a dynamic IP address.

"If not, are you using a real domain name internally that does exist in the internet cloud?"

No and don't want to.

"Only the following IP addresses - and your server IP should be all that's there."

Already been set.

"ipconfig /flushdns"

Done that many times but as soon as soon as the server reboots it picks up the new IP address.

"With respect to NSLOOKUP, it can be set to use another server as the root for lookups"

Only have one server and one client on this test network.


jimshoe:

"Under advanced, DNS tab, be sure you have the checkbox register this connections address in DNS checked."

I have tried this both unchecked and checked it seems to have no affect, but when it says register this connection, what does that mean, register it with my ISP DNS? I don't want that as this is purely a test server on a separate network from the company behind its own router with a dynamic IP address. We want it to have access to the internet (research and downloading) but do not want it to be on the internet with a domain name (like a home setup).

awilson1199,

HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

This question is still open and getting old. If any of the comment(s) above helped you please accept it as an answer or split the points who ever helped you in this question. Your attention in finalising this question is very much appreciated. Thanks in advance,

****** PLEASE DO NOT ACCEPT THIS AS AN ANSWER ********

- If you would like to close this question and have your points refunded, please post a question in community support area on https://www.experts-exchange.com/Community_Support/ giving the address of this question. Thank you      

Pasha

Cleanup Volunteer

I put this command "ipconfig /registerdns" in a bat file on my client and put it in the Startup of my client. It solved my problem for now, but I will have to come back and figure out why it is needed.