NIS slaves and different domain names...

[Tony Walker_2]

Hi Guys,

I currently have a NIS domain with 1 master and 2 slaves (all clients are setup using ypinit -c so no broadcast issues). The 2 slaves are being decommisioned and I have to re-provide this service on 2 other machines on a different subnet. The problem is that the NIS domain is xxx.com and the machines I need to migrate to have yyy.com as their domainname. The 2 machines are also LDAP proxies - so I can't just change the domainname.
Is there any way that I can have a NIS master for xxx.com push out maps to slaves on yyy.com and whats more, will clients in the xxx.com domain be able to use those slaves once they are configured?

Thanks in advance,

Tony

[Dave Olker · Accepted solution]

Hi Tony,

If you look at page 125 of the NFS Services Administrator's Guide, posted here:

http://docs.hp.com/en/5991-5272/5991-5272.pdf

You will see this text:
____________________________________________

A host cannot be the primary server for more than one NIS domain. However, a primary server for one domain may be a secondary server for another domain. A host can be a secondary server for multiple domains. A client belongs to only one domain.
____________________________________________

So the answer to your first question about having the NIS primary for xxx.com push maps to secondary on yyy.com is "no" as this would mean using one server as the NIS primary for two domains. If a system is pushing maps to the secondary then it is, by definition, the primary.

Your second question - will clients in xxx.com be able to use secondary (I assume you mean secondary in the yyy.com domain) once they are configured - if I understand your question correctly I'd say the answer is "no" unless the secondary are serving both the xxx.com and yyy.com domains at the same time.

Clients in the xxx.com domain need to bind to a server that is providing maps for the xxx.com domain, just as clients in the yyy.com domain need to bind to servers providing maps for that domain.

Now, as the above text states, you can configure systems to be NIS secondary servers for multiple domains simultaneously. If that is what you're planning on doing - taking the new yyy.com secondary and making them dual-domain servers for both xxx.com and yyy.com then the clients in xxx.com should be able to bind to them.

Obviously you'd want to use ypinit -c on these clients to tell them the IP addresses of the new xxx.com servers to bind to.

If I've misunderstood your questions then I apologize. If so, please clarify exactly what configuartion you're proposing.

Regards,

Dave

[Peter Nikitka]

Hi,

perhaps I do not understand you correctly as well (Hi Dave!), but perhaps you are mixing the terms 'NIS-domain' and 'DNS-domain'.

If there are hosts in two (or more) different DNS-domains, it is perfectly legal to have them served by one NIS-domain and NIS-servers of this NIS-domain, running in different DNS-domains.
You just have to configure the NIS-domain at a slave server in DNX-yyy.com explicitly to the value of the NIS-domainname of the NIS-master located in DMS-xxx.com.
There will be no impact for DNS-operations.

Presetting the NIS-domainname to the DNS-domainname is just a default: you can change it.

mfG Peter

[Tony Walker_2]

Hi Guys,

Thanks very much for the input. I'm almost confused reading my question back to myself anyway! As it happens I've slightly changed the design and will now be serving 3 NIS domains from 1 machine which I've tested it successfully.

Cheers,

Tony