Operating System - HP-UX
1753863 Members
7357 Online
108809 Solutions
New Discussion юеВ

Re: 11.31 NFS using FQDN in "share" command

 
Dave Olker
HPE Pro

Re: 11.31 NFS using FQDN in "share" command

What happens when you actually resolve the non-fully-qualified hostname on both the NFS client and server system?

# nslookup rx260-16
I work for HPE

[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
mvpel
Trusted Contributor

Re: 11.31 NFS using FQDN in "share" command

It's the nsswitch.conf and /etc/hosts files on your NFS server, not your client, that you need to concern yourself with.

I assume RX26-156 was able to ping RX260-16 by hostname when you made the nsswitch.conf change, right? What did the /etc/hosts entry for RS260-16 on RX26-156 look like?
SoorajCleris
Honored Contributor

Re: 11.31 NFS using FQDN in "share" command

Hi,

# nslookup rx260-16
Using /etc/hosts on: rx26-156

looking up FILES
Name: rx260-16
Address: 192.168.112.142
Aliases: rx260-16
==================================
/etc/hosts - rx26-156 ( I tried to use both rx260-16 and rx260-16.usa.hp.com)

16.118.114.125 rx26-156.usa.hp.com rx26-156
127.0.0.1 localhost loopback
16.118.114.250 hpvldas1 hpvldas1.usa.hp.com
192.168.112.142 rx260-16 rx260-16

=================================
Thanks
sooraj
"UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity" - Dennis Ritchie
Dave Olker
HPE Pro

Re: 11.31 NFS using FQDN in "share" command

Do you get the exact same output on both the NFS client and server?

Is there a need to have the same hostname listed twice on the same line?

192.168.112.142 rx260-16 rx260-16

Do you get the same behavior if you change the line to:

192.168.112.142 rx260-16

on both the NFS client and server?

Dave
I work for HPE

[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
Horia Chirculescu
Honored Contributor

Re: 11.31 NFS using FQDN in "share" command

Hello Sooraj,

This is what I understand from the man page and tried to suggest you in my first intervention.

>Hi Steven,

>You mean to say, the manpage clear that if at >all there is dns mentioned in nsswitch we >should use FQDN?

Horia.
Best regards from Romania,
Horia.
SoorajCleris
Honored Contributor

Re: 11.31 NFS using FQDN in "share" command

but horea , I have used the same but see the output posted above.

Regards,
Sooraj
"UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity" - Dennis Ritchie
mvpel
Trusted Contributor

Re: 11.31 NFS using FQDN in "share" command

Maybe the share command allows unqualified hostnames if DNS is not used, but someone forgot to tell the nfsd team and so it doesn't allow unqualified names when making hostname-based access decisions.

But in any case, using FQDNs is a better practice in general, since it removes any ambiguity about which host you're referring to. I ran into the same situation in Nortel a few years ago, where we had five internal domain names in active use.
SoorajCleris
Honored Contributor

Re: 11.31 NFS using FQDN in "share" command

ha ha .. thats great. I am planning to tell NFSD team :)
"UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity" - Dennis Ritchie