Summary: name resolution issue in solaris 10

From: Gérard Henry <ghenry_at_cmi.univ-mrs.fr>
Date: Mon Mar 17 2008 - 11:57:47 EDT
thanks to darren dunham, rob mcmahon, crist clark, andrey borzenkov and 
kiran sharma for ttheir replies.

the simpliest solution is to add FQDN in netgroups file:
exports   clientA clientB
clientA   (clientA,,) (clientA.my.domain.fr,,)
clientB   (clientB,,) (clientB.my.domain.fr,,)

my original post
> since few days, i've got an issue with machines name resolution on the 
> nfs server.
> The nfs server (servA) is a NIS client (solaris 10 sparc 11/08), and 
> directories are shared with netgroups constraints. The nis map netgroup 
> contains all clients names (not fqdn names). It worked.
> But now, nfs clients can't mount the shared dirs, because the nfs server 
> see requests from clientA.my.domain.fr instead of clientA:
> servA-root% snoop clientA
> Using device /dev/e1000g0 (promiscuous mode)
> clientA.my.domain.fr -> servA         TCP D=111 S=658 Ack=3984864805 
> Seq=4069484885 Len=0 Win=7136 Options=<nop,nop,tstamp 1599660880 10605740>
>        servA -> clientA.my.domain.fr MOUNT3 R Mount Permission denied
> 
> When i use getent, i got the correct name:
> servA-root% getent hosts clientA
> 192.168.0.219   clientA
> 
> /etc/nsswitch.conf contains:
> hosts: files nis dns
> 
> ans /etc/resolv.conf:
> domain my.domain.fr
> nameserver 192.168.0.23
> 
> The only thing i notice is that if i suppress /etc/resolv.conf, it works 
> . But in this case, this is sendmail that become broken!
> 
> What is the right way to have nis resolution working?
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
Received on Mon Mar 17 10:58:03 2008

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:44:10 EST