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

Re: Update Broke NFS Exports



On Fri, Jan 16, 2009 at 8:40 PM, Jameson <imntreal gmail com> wrote:
>> Is 192.168.1.55 one of the other hosts trying to mount the export?  And if
>> so, what does 'host 192.168.1.55' command yield at the nfs server?
>
> Yes, unfortunately it seems to be trying to pull the look up from a
> public server, and rejecting it due to it being a private address.  I
> never bothered with reverse zones, so I don't know why it would need
> it now, but not before.

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)

It looks like this may be my issue, but I have no idea how to fix it.
If anyone knows how to make it not bother with the reverse look up,
that would be a fine workaround for me, as I said, I don't need
reverse DNS for anything else.

Thanks,
=-Jameson


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