Windows DSN refresh
Posted on 2014-03-12
In our organization we use two domain let say one to server co1.com.sg and other co1.local. The co1.com.sg for internet FDQN and co1.local for Windows AD. The co1.com.sg DNS server is a Linux and the co1.local consists of two servers let say dns1 and dns2. The dns1 and dns also as slave for co1.m1.com.sg.
Yesterday I did some DR test for backup (we are using NetBackup), the master server that use a virtual name let say masterbck we failed over to DR site, so for example masterbck.m1.com.sg the ip would be changed to the DR site IP. I changed also for the reverse DNS The test was successfull then I failed back again.
After I put back the all the DNS entries back to like normal production includes the reverse DNS. All the backup using the co1.m1.com.sg as name resolver. All the Unix server in our site using the linux dns as resolver are fine, but windows that is using dns1 are having problem, funny thing the the windows using the dns2 are ok. The netbackup that failed were MS SQL backup is using agent, for this kind of backup reverse DNS is important. Then I check the dns1 could not resolve the reverse name properly, where dns2 was correct.
My question is how I push the the co1.m1.com.sg to the dns2 (function like a slave)? I did try to reload the DNS on the windows site, but still having problem.