Bind package for pfsense 2.1

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.

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?