Bind package for pfsense 2.1

[cuteredstorm]

I used custom options for transfer-source and notifiy-source. That is not something that needs special attention. I think it's ready for release. Good job!

[cl]

Hi,

This is a great piece of work, just about everything that is really needed for using BIND!

Maybe there are some remaining bugs:

1. No matter what I set the serial to, it defaults to a timestamp.
2. AAAA-records get a trailing dot at the end, which makes the zone-file not loading.
3. It is a little annoying that after adding a record when editing a zone, the web page scrolls all the way up to top (Firefox 25.0.1). After creating a zone, records are the most edited part so perhaps they should be placed at the top.
4. There are some minor misspellings (Loggin serverity).

Looking forward to the release, this will be used straightaway, when working for IPv6!

[cuteredstorm]

1. True. Since it is supposed to increment with every change, this is really the only viable solution. Have a better solution?
2. Don't have this issue. Can you post the record on UI+resulting zone file?
3. True.
4. True.

[cl]

1. No, maybe to remove the serial field from the zone editing page.
2. See attachment and below. I am running the 2.1 nanobsd release on an ALIX board.

The resulting Zone file:

$TTL 1h
;
$ORIGIN example.com.

;      Database file example.com.DB for example.com zone.
;      Do not edit this file!!!
;      Zone version 2385644025
;
example.com.    IN  SOA ns1.example.com.        cl.example.com. (
                2385644025 ; serial
                1d ; refresh
                2h ; retry
                4w ; expire
                1h ; default_ttl
                )

;
; Zone Records
;
@        IN NS  ns1.example.com.
@        IN A  93.184.216.119
www      IN AAAA        2606:2800:220:6d::aa7.

[cuteredstorm]

@2.: yes, this is a known issue and already resolved. You can check changes in Git or wait for the next version.

[marcelloc]

@cuteredstorm:

@2.: yes, this is a known issue and already resolved. You can check changes in Git or wait for the next version.

Just reinstall the package to get latest version.

[madforic]

I have been reinstalled the bind package, now it is 9.9.4 pkg v0.3.2, with no luck :-
It still append a dot at the end of ipv6 address in AAAA record.
Any workarounds?

Upd. I edited this files manualy and everything is ok! 8)

[marcelloc]

I have no idea what happened with the patch. I've updated it again.

Thanks for the feedback.

[EricE]

Awesome looking package - thanks (again) marcelloc!

It's been a while since I have messed with BIND - anyone have a quick walkthrough for setting up BIND via the pfSense package to be a slave server for a DNS zone?  In the meantime off to find the old BIND tutorials…

[marcelloc]

@EricE:

anyone have a quick walkthrough for setting up BIND via the pfSense package to be a slave server for a DNS zone?  In the meantime off to find the old BIND tutorials…

Config service from left to right, check field descriptions, it will be easy if you know how bind works.

[aarcane]

Editing zones which are also updated dynamically causes configuration to get out of sync with journal.  This is a common problem and there is a known workaround.  Read this short article for a brief explanation

http://www.thedumbterminal.co.uk/?action=showArticle&articleId=168

[johnross]

Hi, I would like to report some issues on the package for I am migrating my old setup of bind (terminal-based) to the new GUI package:

1. Serial auto-generates by itself. Which opposed from my current configuration (we need it to be timestamped for example: 2013122701)
2. zone domain record TYPE does not have NAPTR
3. When creating a SLAVE zone. The slave file (slave.example.com.DB) was missing at the SLAVE DIR : /cf/named/etc/namedb/slave/sample_slave/.
4. Cannot assign separate logging severity for each Logging Options.

and BTW this package is AWESOME  ;D

[aarcane]

Other feature I noticed:  adding a new static DHCP lease does not automatically update in bind.  It doesn't automatically update when restarting bind.  It doesn't update until you edit the relevant zone file and click Save, then restart bind.

With regard to my other bug post:
I'd like to recommend that zone files be configured to be bare, then the data for the zone be loaded dynamically for editing and modified dynamically when editing/clicking apply.  The utility nsupdate from the bind utility can be configured for this functionality.

[lucky]

I installed the bind package today to set a couple of slave zones up. I added the zones, but they don't seem to get put into the config - they never transfer. The masters have transfer allowed. I did a quick packet capture and saw no traffic to the master on port 53. The bind config file in pfSense doesn't seem to have anything related to my zones in it…

Any ideas?

[marcelloc]

@lucky:

Any ideas?

Did you created firewall rules to allow dns traffic between slave and master?

[lucky]

@marcelloc:

@lucky:

Any ideas?

Did you created firewall rules to allow dns traffic between slave and master?

Thanks, sure did.

I was just looking at the named.conf on the firewall, and there are no configuration directives for the slave zone. Seems like the package is not properly creating the named.conf file.

[marcelloc]

@lucky:

Seems like the package is not properly creating the named.conf file.

On what dir are you looking for config files?

[lucky]

@marcelloc:

@lucky:

Seems like the package is not properly creating the named.conf file.

On what dir are you looking for config files?

/cf/named/etc/namedb

A screen shot of the zones tab under BIND config is attached. This is the resulting config file (named.conf):

#Bind pfsense configuration
#Do not edit this file!!!

 key "rndc-key" {
        algorithm hmac-md5;
        secret "**removed**";
 };

 controls {
        inet 127.0.0.1 port 953
                allow { 127.0.0.1; } keys { "rndc-key"; };
 };

options {
        directory "/etc/namedb";
        pid-file "/var/run/named/pid";
        statistics-file "/var/log/named.stats";
        max-cache-size 256M;
                        listen-on-v6 { none; };
                listen-on { *public ip address*;  };

        };

                logging { category default { null; }; };

[bryan.paradis]

@johnpoz:

I don't think this quite ready for prime time?

Oct 14 23:33:49 named[69425]: starting BIND 9.9.4 -c /etc/namedb/named.conf -u bind -t /conf/named/
Oct 14 23:33:49 named[69425]: loading configuration from '/etc/namedb/named.conf'

The command that it is starting with

named -c /etc/namedb/named.conf -u bind -t /conf/named/

Option -c for specifying the configuration file

-c /etc/namedb/named.conf/

@named(8):

-c config-file
  Use config-file as the configuration file instead of the default,
  /etc/namedb/named.conf. To ensure that reloading the configuration
  file continues to work after the server has changed its working
  directory due to to a possible directory option in the
  configuration file, config-file should be an absolute pathname.

Option -u for setting user

-u bind

@named(8):

-u user
  Setuid to user after completing privileged operations, such as
  creating sockets that listen on privileged ports.
  Note: On Linux, named uses the kernel's capability mechanism
  to drop all root privileges except the ability to bind(2) to
  a privileged port and set process resource limits.
  Unfortunately, this means that the -u option only works when
  named is run on kernel 2.2.18 or later, or kernel
  2.3.99-pre3 or later, since previous kernels did not allow
  privileges to be retained after setuid(2).

Option -t for chrooting/jailing named to the folder

-t /conf/named/

@named(8):

-t directory
  Chroot to directory after processing the command line arguments,
  but before reading the configuration file.
  Warning: This option should be used in conjunction with the
  -u option, as chrooting a process running as root doesn't
  enhance security on most systems; the way chroot(2) is
  defined allows a process with root privileges to escape a
  chroot jail.

So you can see that by jailing it with a chroot using -t the path for -c is actually going to be the -t path + -c path or:

/cf/conf/named/etc/namedb/named.conf

named8 BIND9 man

Had a look through the whole thread. Thought maybe this post would be helpful for anyone else.

[lucky]

@bryan.paradis:

So you can see that by jailing it with a chroot using -t the path for -c is actually going to be the -t path + -c path or:

/cf/conf/named/etc/namedb/named.conf

Had a look through the whole thread. Thought maybe this post would be helpful for anyone else.

This is the bind process that I currently see running on my firewall:

bind   55193  0.0  0.7 22108 14140  ??  INs  22Jan14   0:00.48 /usr/pbi/bind-i386/sbin/named -c /etc/namedb/named.conf -u bind -t /cf/named/

In this case, -t path + -c path = /cf/named/etc/namedb/named.conf, which is where the named config file actually is as part of this package. So that doesn't seem to be a problem.

My problem is that I configured a secondary zone, but that configuration does not appear in the config file.