thank you - Re: bind9 (9.18.14) build / install on macOS Ventura (13.3.1) fails to create dirs or files as expected
Thank you and to everyone who took the time to respond. Your collective input did the trick and I now have bind running successfully through a brew install. I got pulled into another project and wanted to reply with thanks sooner. Your time is valuable and I sincerely appreciate everyone who took the time to make suggestions. > On May 10, 2023, at 1:39 AM, Greg Choules > wrote: > > The named binary *could* exist in many places; it depends on the OS. For > example, with a Homebrew install on my Mac it's here: > /usr/local/Cellar/bind/9.18.14/sbin/named because of this build parameter: > --prefix=/usr/local/Cellar/bind/9.18.14 > It's linked to from /usr/local/opt/bind/sbin/named, for convenience. > > I don't recall whether you get an example "named.conf" Mine is here, by the > way: > /usr/local/etc/bind/named.conf because of this build parameter: > --sysconfdir=/usr/local/etc/bind > > Again, search for a named.conf and if you don't have one, 'touch' it to > create it then try running it. By default it doesn't need to contain > anything, just exist. The built-in defaults are enough to get a server > running. > As you start to customise your config, keep an eye on the log, which will > tell you whether named starts or not and if not, why. Then you can correct > errors and try again. > > I don't think it should matter that artefacts from a previous install attempt > are hanging around. But before you try installing it another way I would > search for files called "named": > sudo find / -name named > and see if you have a binary. In my case: > %file /usr/local/sbin/named > /usr/local/sbin/named: Mach-O 64-bit executable x86_64 > > If you find an executable, do /named -V (uppercase V), which will print > a summary of how it was built. > Similarly /named -C (uppercase) will print the defaults. > > Hope this helps. > Greg > > > On Wed, 10 May 2023 at 05:55, Pacific <mailto:i...@pacific-holding.com>> wrote: > Hi, thanks for the reply. > > For some reason I thought it did install or drop a base bones named.conf > file, however, it should have dropped the named binary into /usr/local — > which it didn’t do. And none of the other “various BIND 9 libraries”. > > The bind docs at > https://bind9.readthedocs.io/en/latest/chapter10.html#build-bind > <https://bind9.readthedocs.io/en/latest/chapter10.html#build-bind> > > in section 10.2 on building show this: > > make install installs named > <https://bind9.readthedocs.io/en/latest/manpages.html#std-iscman-named> and > the various BIND 9 libraries. By default, installation is into /usr/local, > but this can be changed with the --prefix option when running configure. > > The option --sysconfdir can be specified to set the directory where > configuration files such as named.conf > <https://bind9.readthedocs.io/en/latest/manpages.html#std-iscman-named.conf> > go by default; --localstatedir can be used to set the default parent > directory ofrun/named.pid. --sysconfdir defaults to $prefix/etc and > --localstatedir defaults to $prefix/var. > > If I’m missing something please let me know - or if you have any suggestions, > like just moving the named binary from my temp dir into /usr/local I’d > appreciate. Thanks. > >> On May 9, 2023, at 5:08 PM, Anand Buddhdev > <mailto:ana...@ripe.net>> wrote: >> >> On 09/05/2023 22:23, Pacific wrote: >> >> Hi Pacific, >> >>> Installing bind9 (9.18.14) on macOS Ventura (13.3.1) — install is >>> not creating a namedb directory nor can I find a boilerplate named.conf. >> >> As far as remember, the bind install procedure doesn't create a named.conf. >> >> -- >> Anand > > -- > Visit https://lists.isc.org/mailman/listinfo/bind-users > <https://lists.isc.org/mailman/listinfo/bind-users> to unsubscribe from this > list > > ISC funds the development of this software with paid support subscriptions. > Contact us at https://www.isc.org/contact/ <https://www.isc.org/contact/> for > more information. > > > bind-users mailing list > bind-users@lists.isc.org <mailto:bind-users@lists.isc.org> > https://lists.isc.org/mailman/listinfo/bind-users > <https://lists.isc.org/mailman/listinfo/bind-users> -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: bind9 (9.18.14) build / install on macOS Ventura (13.3.1) fails to create dirs or files as expected
Hi, thanks for the reply. For some reason I thought it did install or drop a base bones named.conf file, however, it should have dropped the named binary into /usr/local — which it didn’t do. And none of the other “various BIND 9 libraries”. The bind docs at https://bind9.readthedocs.io/en/latest/chapter10.html#build-bind in section 10.2 on building show this: make install installs named <https://bind9.readthedocs.io/en/latest/manpages.html#std-iscman-named> and the various BIND 9 libraries. By default, installation is into /usr/local, but this can be changed with the --prefix option when running configure. The option --sysconfdir can be specified to set the directory where configuration files such as named.conf <https://bind9.readthedocs.io/en/latest/manpages.html#std-iscman-named.conf> go by default; --localstatedir can be used to set the default parent directory ofrun/named.pid. --sysconfdir defaults to $prefix/etc and --localstatedir defaults to $prefix/var. If I’m missing something please let me know - or if you have any suggestions, like just moving the named binary from my temp dir into /usr/local I’d appreciate. Thanks. > On May 9, 2023, at 5:08 PM, Anand Buddhdev wrote: > > On 09/05/2023 22:23, Pacific wrote: > > Hi Pacific, > >> Installing bind9 (9.18.14) on macOS Ventura (13.3.1) — install is >> not creating a namedb directory nor can I find a boilerplate named.conf. > > As far as remember, the bind install procedure doesn't create a named.conf. > > -- > Anand -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
bind9 (9.18.14) build / install on macOS Ventura (13.3.1) fails to create dirs or files as expected
Installing bind9 (9.18.14) on macOS Ventura (13.3.1) — install is not creating
a namedb directory nor can I find a boilerplate named.conf.
Steps taken:
Downloaded tar directly from isc, saved to a local directory as a user with
admin privs.
Steps to build:
tar xzf bind-9.18.14.tar.gz
cd bind-9.18.14
./configure
Config summary reads:
=
Configuration summary:
-
Optional features enabled:
Memory allocator: jemalloc
GSS-API (--with-gssapi)
DNSSEC validation active by default (--enable-auto-validation)
-
Features disabled or unavailable on this platform:
Small-system tuning (--with-tuning)
Allow 'dnstap' packet logging (--enable-dnstap)
GeoIP2 access control (--enable-geoip)
DNS Response Policy Service interface (--enable-dnsrps)
Allow 'fixed' rrset-order (--enable-fixed-rrset)
Very verbose query trace logging (--enable-querytrace)
Single-query trace logging (--enable-singletrace)
LMDB database to store configuration for 'addzone' zones (--with-lmdb)
IDN support (--with-libidn2)
-
Configured paths:
prefix: /usr/local
sysconfdir: ${prefix}/etc
localstatedir: ${prefix}/var
Compiler: gcc
Apple clang version 14.0.3 (clang-1403.0.22.14.1)
Target: arm64-apple-darwin22.4.0
Thread model: posix
InstalledDir:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
CFLAGS: -Wall -Wextra -Wwrite-strings -Wpointer-arith
-Wno-missing-field-initializers -Wformat -Wshadow
-Werror=implicit-function-declaration -Werror=missing-prototypes
-Werror=format-security -Werror=parentheses -Werror=implicit
-Werror=strict-prototypes -Werror=vla -fno-strict-aliasing
-fno-delete-null-pointer-checks -fdiagnostics-show-option -g -O2 -pthread
-Wno-deprecated-declarations
CPPFLAGS: -D_FORTIFY_SOURCE=2 -I/opt/homebrew/opt/openssl@3/include
LDFLAGS: -L/opt/homebrew/opt/openssl@3/lib
—
After configure completes:
make
When make successfully completes, ran test suite:
sudo ./bin/tests/system/ifconfig.sh up
make test
Tests run clean, bring down interface and do make install which runs to
completion:
sudo ./bin/tests/system/ifconfig.sh down
sudo make install
Install appears to complete successfully, however there is no namedb directory
in either /etc or /usr/local/etc
In fact there is no named.conf file anywhere on the system except in the source
tree.
Please advise as to where to look or please advise if there are additional
build steps to take, if configure needs edits, etc.
Thanks for any assistance.
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
