NIS Overriding DNS

I set up an NIS server a few years ago on a RH7.3 system. Upgrades to
RH9, FC2, and FC3 followed. Three months ago, I wiped the disk and
installed CentOS-4. I thought I had the NIS server configured as it was
previously. There was little/no NIS client activity until recently and
of course there are now problems:

When NIS is enabled on a client, access to the server is diverted to
the loopback address. dig shows the proper address for the server, but
ping (and ftp, ssh, etc) goes to 127.0.0.1. When NIS is disabled on the
client, ping goes to the proper address. This happens on all clients
with various flavors of linux.

I've looked at the server configuration and can't see what I've done
wrong. The clients have not been modified.

Any suggestions are appreciated.

<(E-Mail Removed)> wrote in message
news:100820050020040947%(E-Mail Removed)...
> I set up an NIS server a few years ago on a RH7.3 system. Upgrades to
> RH9, FC2, and FC3 followed. Three months ago, I wiped the disk and
> installed CentOS-4. I thought I had the NIS server configured as it was
> previously. There was little/no NIS client activity until recently and
> of course there are now problems:
>
> When NIS is enabled on a client, access to the server is diverted to
> the loopback address. dig shows the proper address for the server, but
> ping (and ftp, ssh, etc) goes to 127.0.0.1. When NIS is disabled on the
> client, ping goes to the proper address. This happens on all clients
> with various flavors of linux.
>
> I've looked at the server configuration and can't see what I've done
> wrong. The clients have not been modified.
>
> Any suggestions are appreciated.

/etc/nsswitch.conf is correctly edited?

In article <(E-Mail Removed)>, ynotssor
<(E-Mail Removed)> wrote:

> <(E-Mail Removed)> wrote in message
> news:100820050020040947%(E-Mail Removed)...
> > I set up an NIS server a few years ago on a RH7.3 system. Upgrades to
> > RH9, FC2, and FC3 followed. Three months ago, I wiped the disk and
> > installed CentOS-4. I thought I had the NIS server configured as it was
> > previously. There was little/no NIS client activity until recently and
> > of course there are now problems:
> >
> > When NIS is enabled on a client, access to the server is diverted to
> > the loopback address. dig shows the proper address for the server, but
> > ping (and ftp, ssh, etc) goes to 127.0.0.1. When NIS is disabled on the
> > client, ping goes to the proper address. This happens on all clients
> > with various flavors of linux.
> >
> > I've looked at the server configuration and can't see what I've done
> > wrong. The clients have not been modified.
> >
> > Any suggestions are appreciated.
>
> /etc/nsswitch.conf is correctly edited?
>

Ah, yes. I see that the applet that enables NIS authentication changes
the hosts line to put nis before dns. Thanks.

Is it normal for the server to supply the clients with 127.0.0.1 as its
address? I don't think it was doing that before I reinstalled the
server.

<(E-Mail Removed)> wrote in message
news:100820052127567029%(E-Mail Removed)...

> > > Any suggestions are appreciated.
> >
> > /etc/nsswitch.conf is correctly edited?
>
> Ah, yes. I see that the applet that enables NIS authentication changes
> the hosts line to put nis before dns. Thanks.
>
> Is it normal for the server to supply the clients with 127.0.0.1 as its
> address? I don't think it was doing that before I reinstalled the
> server.

You should examine the /etc/hosts file to verify that 127.0.0.1 is the IP
address of "localhost" and no other alias.

In article <(E-Mail Removed)>, ynotssor
<(E-Mail Removed)> wrote:

> You should examine the /etc/hosts file to verify that 127.0.0.1 is the IP
> address of "localhost" and no other alias.

I would have sworn that that was the first thing I did. I probably
checked only the client. The server's hosts file had its name as an
alias for 127.0.0.1

Thanks.

<(E-Mail Removed)> écrivait news:100820050020040947%(E-Mail Removed):
> When NIS is enabled on a client, access to the server is diverted to
> the loopback address. dig shows the proper address for the server, but
> ping (and ftp, ssh, etc) goes to 127.0.0.1. When NIS is disabled on the
> client, ping goes to the proper address. This happens on all clients
> with various flavors of linux.

Check the 'order' directive in the /etc/host.conf file. 'nis' should be the
last option.

Regards