Date: Tue, 2 Dec 2025 13:30:47 -0800 From: Rick Macklem <rick.macklem@gmail.com> To: freebsd-fs@freebsd.org Subject: Re: nfs exports by local dns Message-ID: <CAM5tNy49FMOMTMV11BMxf=EbAJ896ggjC081=QMSyUZkatev8Q@mail.gmail.com> In-Reply-To: <aS8eW048vdJOxdfR@int21h> References: <aS8eW048vdJOxdfR@int21h>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 2, 2025 at 9:14 AM void <void@f-m.fm> wrote: > > Hi, > > Let's say there are two offices in one building and there > are three nfs shares on a central server /share/office1 /share/office2 > and /share/office3 > > office1 has 15 machines all *.office1.local most 192.168.1.2-12 but 3 .250-252 > office2 has 25 machines all *.office2.local 192.168.1.50-74 > > provided that I'm either doing this in /etc/hosts or a split > horizon unbound serving a local zone for both domains, is this feasible > in the (zfs) sharenfs statement, for in this example share/office1 > > # /share/office1 -maproot=root -alldirs *.office1.local > (guess I don't need a -network here?) > > If it can't be wildcarded then can each host be added like > > # /share/office1 -maproot=root -alldirs client1 client2 client3 \ > client4 client5 client6 client7 client8 client9 client10 client11 client12 \ > client13 client14 client15 etc etc 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.) rick > > which is messy but not as long as using ip/subnet > > (on a side note is local rDNS required) > > -- >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAM5tNy49FMOMTMV11BMxf=EbAJ896ggjC081=QMSyUZkatev8Q>