On 2014/07/28 13:14, Sebastian Reitenbach wrote:
>
> On Monday, July 28, 2014 12:46 CEST, Stuart Henderson
> wrote:
>
> > On 2014-07-26, Sebastian Reitenbach wrote:
> > > On Saturday, July 26, 2014 10:04 CEST, Todd Zimmermann
> > > wrote:
> > >
> > >> Have name resolution failure after an up
On Monday, July 28, 2014 12:46 CEST, Stuart Henderson
wrote:
> On 2014-07-26, Sebastian Reitenbach wrote:
> > On Saturday, July 26, 2014 10:04 CEST, Todd Zimmermann
> > wrote:
> >
> >> Have name resolution failure after an upgrade ( rebooting into the the
> >> new system) on my crusty i3
On 2014-07-26, Sebastian Reitenbach wrote:
> On Saturday, July 26, 2014 10:04 CEST, Todd Zimmermann
> wrote:
>
>> Have name resolution failure after an upgrade ( rebooting into the the
>> new system) on my crusty i386 server. A # kill -9 'unbound pid' plus
>> starting unbound from rc.d after
On Sun, Jul 27, 2014 at 3:12 AM, Patrik Lundin
wrote:
>
> So you are basically daisy chaining three different resolvers? This
> seems a bit scary to me from a maintenence standpoint :). If nothing
> else I guess you need to verify all pieces of the puzzle are working as
> intended when problems oc
On Sun, Jul 27, 2014 at 12:22:52AM -0400, Todd Zimmermann wrote:
>
> The home LAN setup here is a humble /29 on IPv4: unbound listens on
> the internal and loopback interfaces, forwarded to dnscrypt-proxy on
> localhost, and then out to OpenDNS.
>
So you are basically daisy chaining three differ
Hey Sebastian and Patrik,
Thanks for the replies and sorry for the vagueness. Should have been
sleeping rather than upgrading/posting. By some minor miracle, a
reboot after sysmerge was done too :)
Started using unbound from ports on 5.4-stable last winter and once it
was working really haven't m
On Sat, Jul 26, 2014 at 04:04:32AM -0400, Todd Zimmermann wrote:
> Have name resolution failure after an upgrade ( rebooting into the the
> new system) on my crusty i386 server. A # kill -9 'unbound pid' plus
> starting unbound from rc.d after and everything is fine. Might have
> been going on for
On Saturday, July 26, 2014 10:04 CEST, Todd Zimmermann
wrote:
> Have name resolution failure after an upgrade ( rebooting into the the
> new system) on my crusty i386 server. A # kill -9 'unbound pid' plus
> starting unbound from rc.d after and everything is fine. Might have
> been going on fo
Have name resolution failure after an upgrade ( rebooting into the the
new system) on my crusty i386 server. A # kill -9 'unbound pid' plus
starting unbound from rc.d after and everything is fine. Might have
been going on for awhile, but usually it works itself out.
-- Z
9 matches
Mail list logo