There goes BIND


As previously foreshadowed, BIND has been removed from the DragonFly base system.  Instead, it’s installed from pkgsrc.  Note that this includes tools like nslookup or host.  Instructions after the jump.

Transition steps, taken from the next release’s notes:

# cd /usr/pksrc/net/bind96;
# bmake all install clean

or

# pkg_radd bind96

# cp /usr/pkg/share/examples/rc.d/named9 /etc/rc.d/
# /etc/rc.d/named stop

edit /etc/rc.conf, and remove

named_enable="YES"

then add

named9_enable="YES"
named_chrootdir="/etc/namedb"
named_flags="-c named.conf"
named_program="/usr/pkg/sbin/named"

# chown -R named /etc/namedb
# /etc/rc.d/named9 start

Test your setup with host, dig and so on. Check for a running named process with ps. Error messages should go to /var/log/messages.

Posted by     Categories: Committed Code, DragonFly, Heads Up!, pkgsrc     6 Comments
6 Comments on There goes BIND

Respond | Trackback

  1. Petr Janda says:

    Next thing sendmail out. Is DMA ready?

  2. DOSguy says:

    Are there any alternatives to nslookup, host and dig in de base installation?

  3. They will still be there; just from a pkgsrc package instead of the base system.

  4. DOSguy says:

    Sure, but does that mean you’ll have to compile the whole bind suite, just to get those tools?

  5. It’s added when the ISO is created. It’ll be functionally the same – the binary files will reside in /usr/pkg/ instead of /usr, and upgrades of BIND won’t be dependent on also upgrading the underlying base system. (A good thing, considering BIND’s security history.) It also means that time gets spent by developers working on DragonFly, not updating software that’s already been updated somewhere else.

  6. Anonymous says:

    if you need lookups (for automated remote installation etc) could take the client code from djbdns (public domain now I guess) and add it to base :)

Respond

Comments

Comments