Date: Fri, 5 Dec 2025 13:35:17 +0000 From: void <void@f-m.fm> To: freebsd-fs@freebsd.org Subject: Re: nfs exports by local dns Message-ID: <aTLflTlfKsoK5UaC@int21h> In-Reply-To: <aS9jHK0fdDMWSUBJ@int21h> References: <aS8eW048vdJOxdfR@int21h> <CAM5tNy49FMOMTMV11BMxf=EbAJ896ggjC081=QMSyUZkatev8Q@mail.gmail.com> <aS9jHK0fdDMWSUBJ@int21h>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, thought I'd follow up to this as it's all working and sorted and have learned something thanks On Tue, Dec 02, 2025 at 10:07:24PM +0000, void wrote: >On Tue, Dec 02, 2025 at 01:30:47PM -0800, Rick Macklem wrote: >>You cannot wildcard, so I'd list them all. >>Also, unless they are all in /etc/hosts, I'd list the IP addresses and >>not the host names, because I wouldn't want the NFS server to depend >>on DNS being up when it boots. >>(But that's just the way I would do it.) On this particular network the very first thing that starts, by design is the unbound server. This is now serving the local zone split horizon. It's too much of a headache for me with hosts files. If nfs shares fail to mount the first thing I'll look at is to see if the machine names resolve. >Would the list all go on one line or can/would it be like > >client1 client2 client3 client4 client5 client6 \ <== note the backslash >client7 client8 client9 > >(this is for inclusion in the zfs set sharenfs= line) the short form hostname seems to work well in the zfs sharenfs line but I've not needed to try yet to split it over long lines with backslash i got myself into a mess with using ips, dns was much more straightforward. I am so far out of my area of expertise with nfs it's not even funny, lol. errors like 'network/host conflict' 'can't get address info for host 10.0.0.5/32' or 'bad host 10.0.0.10/32 when specifying eg 10.0.0.5/32 and 10.0.0.10/32' But it's all working great with short form hostnames. Anyway, thanks for the assistance --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aTLflTlfKsoK5UaC>