NIS server migration problem

Hi all,

I'm working on an NIS server migration project and hit a wall. All systems described run CentOS.

Background: I need to migrate our current NIS server to another machine (actually a VM) located in a different subnet from all the NIS clients. Let's say the old NIS domain was lab.net, I planned to have the new NIS server run NIS domain lab2.net and then switch over the clients one by one. I installed a new NIS server, moved all the maps, settings from the old server, made adjustments to the Makefile to correspond to the Makefile on the old server and ran "make -C /var/yp".

To switch the client (located on a different subnet) over to the new server I modified
- /etc/yp.conf to specify the new domain and host
- /etc/sysconfig/network to specify the new NISDOMAIN
- domainname lists the new NIS domain lab2.net
I restarted ypbind in debug mode and start seeing the following messages:

Quote:

14261: parsing config file 14261: Trying entry: domain lab2.net server newnisserver.com 14261: parsed domain 'lab2.net' server 'newnisserver.com' 14261: add_server() domain: lab2.net, host: newnisserver.com, slot: 0 14261: [Welcome to ypbind-mt, version 1.19] 14261: ping interval is 20 seconds 14263: ping host 'newnisserver.com', domain 'lab2.net' 14263: Answer for domain 'lab2.net' from server 'newnisserver.com' 14261: ypbindproc_domain_2_svc (lab.net) 14261: Pinging all active server. 14261: Requested domain lab.net, found lab2.net, ignored. 14261: Status: YPBIND_FAIL_VAL

What I don't understand is where the is the old NIS domain appearing from in the debug messages? Is it something in the maps that I copied over from the old NIS server?

Now, as a test, I configured a client located on the same subnet as the new NIS server. Running ypbind on this client in debug mode everything seems fine:

Quote:

25946: parsing config file 25946: Trying entry: domain lab2.net server <new NIS server IP address> 25946: parsed domain 'lab2.net' server '<new NIS server IP address>' 25946: add_server() domain: lab2.net, host: <new NIS server IP address>, slot: 0 25946: [Welcome to ypbind-mt, version 1.37.1] 25946: ping interval is 20 seconds 25946: rebind interval is 900 seconds 25948: NetworkManager is running. 25948: Network is available. 25948: Switch to online mode 25948: Going online, reloading config file. 25948: parsing config file 25948: Trying entry: domain lab2.net server <new NIS server IP address> 25948: parsed domain 'lab2.net' server '<new NIS server IP address>' 25948: add_server() domain: lab2.net, host: <new NIS server IP address>, slot: 0 25948: ping host '<new NIS server IP address>', domain 'lab2.net' 25948: Answer for domain 'lab2.net' from server '<new NIS server IP address>' 25948: interface: org.freedesktop.DBus, object path: /org/freedesktop/DBus, method: NameAcquired 25949: ping host '<new NIS server IP address>', domain 'lab2.net' 25949: Entry for lab2.net unchanged, skipping writeout 25949: Answer for domain 'lab2.net' from server '<new NIS server IP address>' 25949: Pinging all active servers.

As far as I know, the firewall rules were adjusted to allow traffic between the client subnet and the new NIS server subnet. Any ideas on what is going on and what is the proper procedure for migrating NIS server to another machine with NIS domain change?

I appreciate any advice you might have.

Thanks, AK.