Moving DNS/NIS server to new network

[MarkSyder]

Hi everybody.

Some time ago I asked a question about moving servers/workstations to a new network. This job is now complete except for one server - the DNS/NIS server, which I have saved till last as it is more likely to be troublesome than a standard server/WS.

I have gone through all my servers/WSs this morning and confirmed that they are set up for both the old ip address and the new one for DNS. NIS is done by server name rather than ip address.

Have I missed anything or can I go ahead with the change using the standard instructions that worked so well before?

Points awarded to anyone who helps to prevent me from getting into a mess.

Mark Syder (like the drink but spelt different)

[Robert-Jan Goossens]

Hi Mark,

Check your steps.

Title: NIS: Moving the NIS Master within the same or different domain
Document ID: KBRC00001416

http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000081003366

Best regards,
Robert-Jan

[MarkSyder]

Thanks Robert-Jan.

I've read that document and it doesn't seem relevant. I'm not making a new server the NIS server, I'm changing the ip address on the NIS server.

Mark

[Peter Nikitka]

Hi,

if possible, attach the new address as an IP-alias to the NIS master.
Make shure, that in your DNS configuration there is permission to use both addresses for lookups.

When changing the hosts entry of the NIS server in (/etc/)hosts then a propate of maps should have no problems, whatever the setting of the hostname of the NIS master is during the yppush/ypxfr.

mfG Peter

[MarkSyder]

What a traumatic day this has been!

Most things are now working, but users who log in from PCs via exceed cannot access. If I try from one of their PCs, logging in as root, it works. If a user whose home directory is nfs mounted tries it logs him straight out again. The same users can log in via workstations without difficulty.

Any useful suggestions will be rewarded with points.

Mark

[Victor Fridyev]

Hi Mark,

Two possible things: font server in exceed is defined via IP and now the IP does not exist.

Check users' environment: HISTFILE and DISPLAY.

HTH

[Peter Nikitka]

Hi Mark,

have your users confg files of Exceed located in windows shares, which are connected to their home directories of the unix hosts?

Then check for the accessability of their UNIX-Homes via smb - perhaps you have to change the name resolution (DNS, WINs) of their PC network configuration as well!

mfG Peter

[MarkSyder]

Hi everybody.

Google to the rescue! I found an error message: "fatal IO error 232" in the user's .dt/startlog. I read that this can be caused by an incorrect entry in the .login file. I couldn't find anything wrong in .login but nor could I find anything useful, so I moved it and asked the user to try again. Success!

Thanks for the suggestions.

Mark

[Dave Johnson_1]

FYI:
The document referred to by Robert-Jan has moved to:
http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en&docId=emr_na-c01003466-1
and is now known by Doc ID: emr_na-c01003466-1
The title is:
NIS: Moving the NIS Master within the same or different domain