Server 2003 Duplicate DNS entries point to old and new shared storage file server even though old file servers name and IP have been changed


we have old server 2003 file server named 'storage' ip address of x.x.10.12.  set new server 2008 r2 file server , gave unique name , unique ip address.

i copied shared data on new server , changed name of old server storage1. changed storage1 ip x.x.10.9.

i named new file server 'storage' , gave ip address of x.x.10.12.

after making sure ping new hostname , ip address , share still mapped users, happy thereafter noticed ip hostname had changed on ping x.x.10.9. went dns , noticed there 2 entries named 'storage', 1 10.9 ip , 1 10.12 ip , users had access , didnt. removed incorrect entry (storage 10.9)from primary dns , propogated secondary , stabilised few hours later problem resurfaced there 2 records in dns storage ip addresses of both servers.

another person unplugged 2 network cables old file server (storage1 x.x.10.9) , within few minutes whole company unable access shares on storage x.x.10.12. both servers became slow , unresponsive , started hanging, storage1 reconnected , both servers rebooted , shares came back. naturally began think perhaps users still accessing shares on old file server , ran tests confirmed shares being accessed indeed on new server (storage 10.12)

nobody here knows how shares set , think gpo cannot find 1 anywhere. reason opted change hostname , ip of new server match old one. there shared folder on old storage server (now named storage1) called dfs there nothing in folder. still shared , didnt break share. other shares on old server broken.

any clues can offer me might point me in right direction helpful.

 

hello,

changing ip addresses, if required, should done time in between , using 3rd 1 until dns replicated , cleaned correct.

so should use old server complete different 1 before , run ipconfig /flsuhdns , ipconfig /registerdns, make sure dns forward/reverse lookup zones reflecting change.

after done can use free ip address new server , same way ipconfig commands.

as clients still have local dns cache containing wrong information @ least ipconfig /flushdns should run on them or a reboot shold done on them clear local dns cache.


best regards meinolf weber disclaimer: posting provided "as is" no warranties or guarantees , , confers no rights.


Windows Server  >  Network Infrastructure Servers



Comments

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

Cannot access Anywhere Access using domain name?

WMI Failure: Unable to update Local Resource Group