WintermuteCL
asked on
Changed IP Address of Server - old IP keep reappearing in DNS.
Changed the IP address of our PDC (only server in the environment) from 192.168.30.10 this morning to 192.168.30.5
All seems well, DHCP is updated, clients can all connect... then suddenly no-one can log in (well, very, very slowly) nothing has changed on clients, but pinging the server resolves to the old IP address.
in DNS, Server > Forward Lookup Zones > DOMAIN.local, there is an "A" record for the server, with it's *OLD* IP address.
I reset it and all is well again - for a few minutes.
Every ten minutes or so (or instantly if I "reload" the zone) the old IP address re-appears.
I have did an ipconfig /flushdns then rebooted the server, searched the registry and replaced all occurences of the old IP with the new one, checked WINS - the only record I can find for the old IP address is the 1Ch DOmain Controller Record, which lists both the old and new addresses.
Any suggestions?
This is urgent, hence high points!
![Avatar of Guy Hengel [angelIII / a3]](https://filedb.experts-exchange.com/files/public/2013/11/25/ddbe0ea6-aa6e-4279-b781-57b735dd3ea0.jpeg){kind=small}
I agree with gpriceee...
ASKER
kay, tried that - so, find out in 15 minutes if it worked :)
Are you replicating DNS or WINS?
Did you change the server's DNS server settings in the TCP/IP settings as well? The server needs to point to itself (only--no ISP DNS!) for DNS.
Anything in the event log?
Install the Support Tools (from CD, if Pre-SP1, from link below if SP1), then run netdiag.exe and dcdiag.exe.
Windows Server 2003 Service Pack 1 32-bit Support Tools
http://www.microsoft.com/downloads/details.aspx?familyid=6EC50B78-8BE1-4E81-B3BE-4E7AC4F0912D&displaylang=en
Anything in the event log?
Install the Support Tools (from CD, if Pre-SP1, from link below if SP1), then run netdiag.exe and dcdiag.exe.
Windows Server 2003 Service Pack 1 32-bit Support Tools
http://www.microsoft.com/downloads/details.aspx?familyid=6EC50B78-8BE1-4E81-B3BE-4E7AC4F0912D&displaylang=en
ASKER
More info:
The server is multihomed, internal 192.168.30.0/24 - this card has no default gateway set, and it's DNS Server is set to 192.168.30.5 (new IP of the server)
external is 10.20.0.0/24, has the feaulf gateway pointing at the Internet router, and DNS also set to 192.168.30.5
THere are no other servers in the environment, so no replication of either WINS or DNS.
The server is multihomed, internal 192.168.30.0/24 - this card has no default gateway set, and it's DNS Server is set to 192.168.30.5 (new IP of the server)
external is 10.20.0.0/24, has the feaulf gateway pointing at the Internet router, and DNS also set to 192.168.30.5
THere are no other servers in the environment, so no replication of either WINS or DNS.
Is it working?
Clear DNS registration and WINS registration for the external address, if they exist.
Also, you'll probably have to flush dns and nbtstat on the workstations if they have problems.
Clear DNS registration and WINS registration for the external address, if they exist.
Also, you'll probably have to flush dns and nbtstat on the workstations if they have problems.
ASKER
dcdiag shows:
Although the Guid DNS name
(6054508f-9a7e-4a64-b03c-b
resolved to the IP address (192.168.30.10), which could not be pinged,
the server name (SERVER.DOMAIN.local) resolved to the IP address
(10.20.0.10) and could be pinged. Check that the IP address is
registered correctly with the DNS server.
Which is odd, as 10.20.0.10 is not registered with DNS!
Although the Guid DNS name
(6054508f-9a7e-4a64-b03c-b
resolved to the IP address (192.168.30.10), which could not be pinged,
the server name (SERVER.DOMAIN.local) resolved to the IP address
(10.20.0.10) and could be pinged. Check that the IP address is
registered correctly with the DNS server.
Which is odd, as 10.20.0.10 is not registered with DNS!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
okay...
flush ok, nbstat ok
stop services
start services
ipconfig /register ok
ping -a resolves correctly to servername
ping servername resolves to *external* interface 10.20.0.10 :|
route table is correct.
*but* the server IP seems to be staying as 192.168.30.5 in DNS... I'll leave it for 15 mins or so to check, but it's looking good!
Check DNS for another record for the server.
Also check WINS.
If you have a hosts entry for the 10. address, it will resolve, so if you have it, clear it.
C:\%OS%\system32\drivers\e
check both the hosts and lmhosts files.
If you find the entry, clear it.
In the WINS tab of network properties, import the hosts file again.
Don't reboot--just go back to the old cmd --> nbtstat -RR
Also check WINS.
If you have a hosts entry for the 10. address, it will resolve, so if you have it, clear it.
C:\%OS%\system32\drivers\e
check both the hosts and lmhosts files.
If you find the entry, clear it.
In the WINS tab of network properties, import the hosts file again.
Don't reboot--just go back to the old cmd --> nbtstat -RR
I'm having exactly the same issue.. I changed my server's IP from 192.168.1.100 to 192.168.1.2 a couple days ago b/c i started running into problems by using such a common IP for my server.. But now my dhcp service is still sending out the old DNS entry.. I've tried gpriceee's solution, but its not working for me...
when i run netdiag /test:dns it say's passed but shows the following warning:
DNS test . . . . . . . . . . . . . : Passed
[WARNING] Cannot find a primary authoritative DNS server for the name 'home.mydomain.com.'.
[ERROR_TIMEOUT]
The name 'home.mydomain.com.' may not be registered in DNS.
[WARNING] The DNS entries for this DC cannot be verified right now on DNS
server 192.168.1.100, ERROR_TIMEOUT.
PASS - All the DNS entries for DC are registered on DNS server '192.168.1.2'
and other DCs also have some of the names registered.
I'm not sure what i'm doing really but i can see that .100 is still showing up which is most likely the problem.. Hope someone can lend a hand? Also, i'm new to EE so i hope it was okay that i posted my related problem here.. And advice would be appreciated.
when i run netdiag /test:dns it say's passed but shows the following warning:
DNS test . . . . . . . . . . . . . : Passed
[WARNING] Cannot find a primary authoritative DNS server for the name 'home.mydomain.com.'.
[ERROR_TIMEOUT]
The name 'home.mydomain.com.' may not be registered in DNS.
[WARNING] The DNS entries for this DC cannot be verified right now on DNS
server 192.168.1.100, ERROR_TIMEOUT.
PASS - All the DNS entries for DC are registered on DNS server '192.168.1.2'
and other DCs also have some of the names registered.
I'm not sure what i'm doing really but i can see that .100 is still showing up which is most likely the problem.. Hope someone can lend a hand? Also, i'm new to EE so i hope it was okay that i posted my related problem here.. And advice would be appreciated.
ipconfig /registerdns
Also, check hosts files.