[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Update Broke NFS Exports



Jameson wrote:
Ok, now, I've set up a reverse zone containing just the two entries
for the 192.168.1.55 client and my server at 192.168.1.51.  Forward
look ups work fine.  host 192.168.1.55 gives me:  Host
55.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)

Well, I fixed this..  I accidentally setup my reverse zone as
192.168.1.0 as apposed to 192.168.1.  It looks like this also fixed my
NFS woes.  I wonder why it worked before if I need this now.
Hopefully, if it stops working anywhere else someone will come across
this, and learn that they now need reverse DNS working to get NFS
working.  Which is kind of a shame, as I doubt most home users will
even have forward DNS setup.

=-Jameson

I would expect adding an entry for 192.168.1.51 to your /etc/hosts on the nfs server to also be a solution, in lieu of configuring private dns.

I was hoping to find an argument that could be added in /etc/sysconfig/nfs to turn off the inverse lookup requirement, but have only found rpc.mountd's -r option which is the opposite of what you need.

--
  "A society grows great when old men plant trees whose shade they know
  they shall never sit in" - Greek Proverb


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]