default named.conf in bind ports and slaving from f-root
Bob Willcox
bob at immure.com
Sat Apr 15 16:45:03 UTC 2017
On Fri, Apr 14, 2017 at 05:25:21PM +0200, Thomas Steen Rasmussen wrote:
> On 04/14/2017 04:51 PM, Mathieu Arnold wrote:
> > Hi,
> >
> > I'm busy right now, could you open a PR so that I don't loose and forget
> > this ?
>
> Sure thing, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218656
>
> /Thomas
>
Thomas,
I am really glad you posted this to the mailing list. This morning I woke up
to a non-functioning named as it could no longer transfer data from
192.5.5.241 and my arpa/IN/internal-view expired at about midnight last night.
I suppose I should have noticed the transfer failure messages in my
/var/log/messages file over the past two weeks, but I didn't (or it didn't
occur to me how serious they were).
I was left with NO outside nameserver resolution at all. Looks like I need to
find a reliable backup nameserver that I can use should something like the
happen again.
Anyway, luckly my mail server had already received you message to
freebsd-ports describing the issue and what you did to correct it. I followed
your example and got my nameserver back to the working state.
Thank you!!
Bob
--
Bob Willcox | You're dead, Jim.
bob at immure.com | -- McCoy, "The Tholian Web", stardate unknown
Austin, TX |
More information about the freebsd-ports
mailing list