slave server ip change and network domainname change.

[jane zhang]

Hi all,

We have a NIS slave server and several it's clients will be moved to another network domain.
The salve nis server was on the same network domain as the master server now ( sv.hp.com)
master.sv.hp.com
slave1.sv.hp.com --> slave1.sx.hp.com

I understand we need to do set_parms to change all the network parameters for the machines moved. But what do I do on the master server for those changes? The machines affected will still use the same NIS domainname and we intend to use the same slave server for the new site.

Thanks,
Jane

[Govind]

On the NIS master you would need to update your /var/yp/maps/ypservers file to reflect the new Slave (complete hostname with the new domain). On the Slave try doing a "ypinit -s nis_master" and select to destroy any existing maps on the Slave and update it with the new maps. I once ran into some issues and had to manually update the /etc/rc.config.d/namesvrs to refelct the changes.
Goodluck
Govind

[Sachin Patel]

I don't think you have to do anything if nis domain name is same

Note: nis and dns domain names are two different thing.

#domainname (will give you nis domain name)

As long as your master and secondary can see each other over the different network master will try to push map to slave.

Sachin

[jane zhang]

Thanks for the replies.

Sachin, I also think I do not need to do anything since we are going to use the same hostname and same nis domainname.

But I am wondering network DNS domain name
change should have some adverse effects?

"ypcat -k ypservers" command (only show up hostnames, and currently all the slaves has the same DNS network domainname sv.hp.com )
# ypcat -k ypservers
slave
slave1
slave2
slave3

But slave1.sv.hp.com ---> slave1.sx.hp.com, I would like to confirm nis master has no problem to push the map to slave1 even though there is no network domain info in the ypservers map? ( sv become sx here)

Thanks for the clarification.

Jane

[Sachin Patel · Accepted solution]

Hi Jane,
As long as you can resolve the slave name from master.sv.hp.com. you don't have to change anything.

master#nslookup slave1 (should resolve to new ip address that you have)

If you can't resolve this then you have to add sx.hp.com zone as a secondary zone in your master server or add slave1 as a CNAME to your zone.

Thanks
Sachin

[jane zhang]

Sachin,

Yeah, I think I need to resolve slave1 no matter which network domain it will be.

Can I achieve by this:

master:/etc/resolv.conf

domain sv.hp.com
search sv.hp.com sx.hp.com hp.com
nameserver ip
nameserver ip
nameserver ip

Could you more specific about how to achieve this?

Thanks.

[Peter Nikitka]

Hi,
that depends on the 'hosts' -entry in
/etc/nsswitch.conf .
If you have
hosts: dns nis files(DNS first),
than you are right. You can even drop the
'domain' - line, just use
search sv.hp.com sx.hp.com
...
If NIS is first used, and your entry for
'slave1' contains the short name, nothing has to be done.