Update Broke NFS Exports
imntreal at gmail.com
Sat Jan 17 02:49:20 UTC 2009
> 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
> 18.104.22.168.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.
More information about the users