Date: Sat, 15 Apr 2017 11:19:30 -0500 From: Bob Willcox <bob@immure.com> To: Thomas Steen Rasmussen <thomas@gibfest.dk> Cc: Mathieu Arnold <mat@FreeBSD.org>, ports@freebsd.org Subject: Re: default named.conf in bind ports and slaving from f-root Message-ID: <20170415161930.GA59758@rancor.immure.com> In-Reply-To: <5d03fad7-1836-8863-7bb5-0db2985a8407@gibfest.dk> References: <85573e9f-c0e7-1e30-6f95-2fec13e0ac26@gibfest.dk> <f7ffd0b9-7749-fa2a-596f-afc4aa3db892@FreeBSD.org> <5d03fad7-1836-8863-7bb5-0db2985a8407@gibfest.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
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@immure.com | -- McCoy, "The Tholian Web", stardate unknown Austin, TX |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170415161930.GA59758>