Bind package for pfsense 2.1

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...

cuteredstorm

Hi,

First of all thank you for your work. I intend to show my gratitude once I have the system set-up.

I wanted to inform you of an issue I believe exists with this package.

The package supports reverse zones, but assumes that all reverse zones are IPV4.

In bind.inc, lines 333 and 405 the string ".in-addr.arpa." is added to zonename. For IPV4 this is correct. For IPV6 string ".ip6.arpa" should be added instead.

Since there is currently no distinction between IPV4/IPV6, I believe another option should be added, but only if "Reverse Zone" is selected.

I will fix the bind_zones.xml and bind.inc so it works for myself, but don't consider it to be "clean". If you want, I can send the changed files.

redstorm.

EDIT: I have additionally found an error in line 435. A dot is added to the destination for all destinations that have letters in them. IPV6 uses letters but a dot should not be added. I have modified bind.inc to exclude AAAA type from this modifications. Both files attached, hope they help.

bind.inc.txt
bind_zones.xml.txt

marcelloc

Thanks for the feedback.

If you want, you can send your fixes directly to official repository on github.com/pfsense/pfsense-packages

cuteredstorm

https://github.com/cuteredstorm/pfsense-packages/pull/1

Also made smoe changes on sync for bind package. Everything i needed works now.

redstorm

marcelloc

Create a pull request so I can merge it to official repo.

Do you miss any other function on bind. I'm planning to change it's version to Release as you can confirm ipv6 is working fine too.

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:

No matter what I set the serial to, it defaults to a timestamp.
AAAA-records get a trailing dot at the end, which makes the zone-file not loading.
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.
There are some minor misspellings (Loggin serverity).

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

cuteredstorm

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

cl

No, maybe to remove the serial field from the zone editing page.
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.

BIND.png_thumb

cuteredstorm

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