Why does NIS produce duplicate results when I query from a client?

jimieee · 06-07-2013, 12:52 PM

I'm just curious why I get two results:

Code:

[root@pandora ~]# ypcat hosts | grep dione
192.168.56.22    dione.localnet dione
192.168.56.22    dione.localnet dione

Yet on the NIS server:

Code:

[root@oceanus ~]# grep dione /etc/hosts
192.168.56.22    dione.localnet dione

Is this normal?
What can I look at to find out more?

Any help much appreciated.

acid_kewpie · 06-10-2013, 02:24 AM

you could start by showing us the actual config, we're not psychic.

jimieee · 06-10-2013, 07:40 AM

Hi Chris,

I appreciate you picking up on this. Please don't interpret the following as a dig at you personally - I just wanted a chance to explain my initial question a little more clearly given the negative tone of your comment.

You're correct - I could have shown you the config. There's two reasons I did not do this:

1) Whether or not there's a configuration problem, it's not relevant to my question "Is this normal?".
2) I already demonstrated that I don't have a duplicate entry in /etc/hosts on oceanus (which was used to generate /var/yp/localnet/hosts.byname). This seems, to me, to be the most obvious legitimate explanation.

NIS seems to work regardless, so I don't know if I've done something wrong - or if this behaviour is correct. If I have done something wrong I'd rather someone tell me "this is wrong", so that I can figure out what the problem is for myself. Of course if this were the case I fully intend to provide an update to explain what I got wrong.

I did think of something else I could include though - If I go on the master and run strings against /var/yp/localnet/hosts.byname I get this entry at the end for dione:

Code:

......dione.localnet192.168.56.22    dione.localnet dionedione192.168.56.22    dione.localnet dione

Best regards,

James

acid_kewpie · 06-10-2013, 08:15 AM

If you wanted a one word answer if it's normal or not then... no.