Bind package for pfsense 2.1

qnarferao

Anybody else testing it? I'm planning to change status to release as it's running fine here.

When you added $ORIGIN, reverse lookup broke, a simple if statement will fix it:


		if($zonereverso == "on")
			$zone_conf .= "\$ORIGIN {$zonename}.in-addr.arpa.\n";
		else
			$zone_conf .= "\$ORIGIN {$zonename}.\n";

-Q

marcelloc

@qnarferao:

When you added $ORIGIN, reverse lookup broke, a simple if statement will fix it:

Thanks for the feedback!

marcelloc

@jbiss_ca:

Does this package integrate well with the pfsense DHCP?

Are you getting any error on logs?

Can you increase log debugging to see what is wrong.

Are your internal dnssec zone working?

CometJo

marcelloc

Thanks for creating this BIND packge for pfSense. And thanks for fixing it yesterday! I am new to pfSense and was trying to set up my domain with your package and banging my head trying to figure out why the reverse domain kept failing to load. I turned on extra debugging to see what the error was, then manually edited the zone file to add the rest of the proper SOA suffix (in-addr.arpa.) and it worked. Then I noticed this post and checked out the version history on the package and re-installed it. Edited/saved my reverse zone and now I see the GUI puts in the proper SOA syntax.

Thanks again! ;D

jbiss_ca

Are you getting any error on logs?

Here's an example of the server storage1 trying to update it's DNS record. The entry storage1 doesn't exist in bind yet as I want it to be automatically created when a DHCP lease is given. If the entry already exists, it would be simply updated.

named[95868]: client 192.168.1.6#57928: view internal: updating zone 'internal.myzone.lan/IN': update unsuccessful: storage1.internal.myzone.lan/TXT: 'RRset exists (value dependent)' prerequisite not satisfied (NXRRSET)

From reading bind documentation, the DHCP server would need a shared key with Bind in order to allow the creation of a new entry (not just updating an entry). In the current pfsense GUI, there's no option to add custom commands or parameters.

Are your internal dnssec zone working?

I was using dnssec but to keep things simple I disabled it. It's not being used anymore

marcelloc

@jbiss_ca:

In the current pfsense GUI, there's no option to add custom commands or parameters.

It has custom options fields on almost all gui tabs.

What additional configuration do you need?

jbiss_ca

I may be going in the wrong direction, I've been following the steps outlined from here http://www.semicomplete.com/articles/dynamic-dns-with-dhcp/#id2255991/ and therefore I would have liked to use a common key between dhcpd and bind in order to authorize the creation of new entries in bind.

jcyr

This is nice and I might just switch to this from unbound!

But….

If I select listen on all interfaces, you generate:

options {
directory "/etc/namedb";
pid-file "/var/run/named/pid";
statistics-file "/var/log/named.stats";
max-cache-size 256M;
listen-on-v6 { Any; };
listen-on { Any; };
version "N/A";

};

That's good. However I don't want it to listen on the WAN interface, so if I select individual interfaces other than the WAN interfaces, you generate:

options {
directory "/etc/namedb";
pid-file "/var/run/named/pid";
statistics-file "/var/log/named.stats";
max-cache-size 256M;
listen-on-v6 { none; }; <------------- This is bad!!!
listen-on { 192.168.4.1; 192.168.0.1; 24.98.144.135; 127.0.0.1; };
version "N/A";

};

What? No IPV6 support???

jcyr

Oh! And another thing. If I disable bind, then reboot… it is restarted anyway!

marcelloc

@jcyr:

What? No IPV6 support???

Do you have ipv6 address assigned to any interface?

bind found these (192.168.4.1; 192.168.0.1; 24.98.144.135; 127.0.0.1; )

marcelloc

@jcyr:

Oh! And another thing. If I disable bind, then reboot… it is restarted anyway!

Disable on gui or just stop the service?

jcyr

Of course. All interfaces have IPV6 addresses, but it seems the config generating script didn't find them. And yes to answer your other question, disabled (or rather, not enabled) in the GUI. Great package though. I've switched to it and rely on the firewall to block IPV6 DNS queries from the WAN interface.

I think it may be a timing thing (as in the time when the config file is generated) since it missed one of the IPV4 addresses and IPV6 address allocation is a little slower than IPV4 address allocation since IPV6 must receive IPV6 router advertisements before it can configure its IPV6 subnets.

marcelloc

I'll check service startup.

After a while can you check if ipv6 addresses are listed on bind conf?

jcyr

Here's your bug (attached fix). You weren't checking for IPV6 correctly in listen-on processing logic in bind.inc.

bind.inc.txt

marcelloc

@jcyr:

Here's your bug (attached fix). You weren't checking for IPV6 correctly in listen-on processing logic in bind.inc.

Thanks! fixed.

~~I'll check now bind startup while disabled.~~

EDIT

Startup check fixed too

brtlvrs

I think I found a tiny bug.
when I use one ore more fowarders the named service won't (re)start.
It gives an error about missing a ; on line 22.
I traced it back to the line where the ip forwarders are defined.
When I enter one or more IP's as forwaders and close them with a ;
then I service restarts without a problem.

The forwarders is configured on the setting page of the bind service.

I've tested this on an greenfield installation with 2.1-RELEASE (amd64)
built on Wed Sep 11 18:17:48 EDT 2013
FreeBSD 8.3-RELEASE-p11

marcelloc

I'll check it.
Are you on latest package version?

asracomp

thanks all…

I just learned about bind
and try...
please guide...

i am on pfsense 2.1 amd64

wan=pppoe
lan= 192.168.1.1/24 dhcp on
opt1=17.0.0.1/8 dhcp on

1. disable dns forwarder
2. enable named on LAN&OPT1
result = dhcpd stop

1. enable dns forwarder just on lan
2. enable named just on opt1
result = no problem...

if something wrong please guide...

thanks...

jcyr

You probably need to specify the DNS server address in the DHCP server tab for LAN (192.168.1.1) and OPT1 (17.0.0.1). It isn't automatically handled like it is when using the DNS forwarder.

asracomp

@jcyr:

You probably need to specify the DNS server address in the DHCP server tab for LAN (192.168.1.1) and OPT1 (17.0.0.1). It isn't automatically handled like it is when using the DNS forwarder.

thanks a lot for fast response

solved…

thank u very much...