You are most welcome, I'm glad you got it running. Now the fun starts! :D
Greg
On Tue, 30 May 2023 at 21:02, Pacific wrote:
> 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
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
I think default configuration file is usually created by the package
distributor. It depends on how you want to use your named, but for basic
iterative server running just on your host, empty file is enough.
Defaults work fine enough for default configuration.
If you run "named -c /dev/null",
I would like to re-iterate what Greg said here - use the Homebrew package.
Using the Homebrew hides some gory details about the system administrators
and could be a good entry to learn how the system administration works.
Otherwise, you need to look at the output that the build process produced,
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
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
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
Hello.
By far the simplest way to install BIND natively on Mac is to use the
Homebrew package manager. I have 9.18.14 installed on mine and it works
fine.
The other alternative is to run it from the Docker image. See here for
details: https://hub.docker.com/r/internetsystemsconsortium/bind9
Hope
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
9 matches
Mail list logo
