BIND Package (or similar functioning authoritative DNS server)
-
Hi there
I've got the exact same problem as @sgoldtho and @CaptainElmo either with a fresh 2.3.1-RELEASE (nanoBSD) or when upgraded to 2.3.2.
Symptom :
Bind cannot be launched from the GUI, while it can be started from the command line using:/usr/local/etc/rc.d/named onestartor
/usr/local/sbin/named -c /etc/namedb/named.conf -u bind -t /cf/named/BTW When Bind is launched (from CLI first) it can be stopped from the GUI.
And there is nothing showing in the log file….After fighting a few hours I finally found the fix 8) :
In the rcfile : /usr/local/etc/rc.d/named.sh
change this line:
if [ -z "`/bin/ps auxw | /usr/bin/grep "[n]amed" | /usr/bin/awk '{print $2}'`" ]; thento
if [ -z "`/bin/ps auxw | /usr/bin/grep "[n]amed " | /usr/bin/awk '{print $2}'`" ]; then–-->Notice the vicious SPACE after [n]amed !
I hope that the maintainer would check this easy fix and include it in the Bind pkg so that next pkg upgrade should work flawlessly.
HTH
-
Hi,
sorry for the restart bug.
That line of code changed because it was not working on ipv4 and ipv6 enabled bind systems.
@wxop thank you for finding the fix.
A new version was just submitted.Best
SvenVoleatech
pfSense Select Partner -
@wxop cheers!
Was fighting over the same issue. I can reconfirm the extra space does the trick.
-
@voleatech
Thank for your amazing fast reaction, I just saw your PR at:
https://github.com/pfsense/FreeBSD-ports/pull/193/files
while I was myself just figuring on which GH branch I should post the fix to ;-)You definitely rock !!!!!!
BTW, now that i found the bug (comparing this file with the squid.sh rcfile), I can not understand why this extra space character is needed even after re-reading the grep manual. As a reward for me having spent hours, to find/fix this bug, would someone be kind enough to explain me WHY the hell this fu***g space is mandatory in the grep pattern ?
best regards -
@wxop
Thanks :)the PR just got merged.
I honestly don't know at this point why it didn't work.
When I run it on the shell in pfSense both versions work on my box and output the PID.Best
SvenVoleatech
pfSense Select Partner -
the PR just got merged.
Whaou !!! The Pf team is just as amazing as you… or I guess this is just a merge bot ! ;D
I honestly don't know at this point why it didn't work. When I run it on the shell in pfSense both versions work on my box and output the PID.
That's why it did take me hours to figure out why the "if/ps/grep/awk" statement was not working as expected… This is really weird!
Any grep guru out there, to show us the light?
all the best
-
New version worked here as well! Thank you!!!
-
Now I can't get it to accept lookup requests on the WAN interface. Port scan shows port 53 is open as expected from internal interfaces, but port 53 is NOT open on the WAN interface.
Has this changed from previous versions or is my configuration messed up somewhere? It used to work on 2.2.6 with my existing configuration.
-
Bind didn't change except for the GUI between 2.2 and 2.3.
Can you check if bind is actually running on the WAN IP with netstat -ln?Best
SvenVoleatech
pfSense Select Partner -
It turns out the problem was my WAN interface got messed up during the upgrade. I reassigned my WAN connection to a different interface and everything started working again.
I can't tell you how thrilled I am to have the BIND package available - thank you Sven!!!
-
Any chance of update to 9.10.4-P3 re: https://kb.isc.org/article/AA-01419/0 ?
-
Hi,
the source for the bind package comes from the freeBSD port git repository.
You would have to ask in the freeBSD mailing list when this is going to be updated there.Best
SvenVoleatech
pfSense Select Partner
www.voleatech.de