public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Paul Simmons <redneckmother@hughes.net>
To: development@lists.ipfire.org
Subject: Re: [PATCH] DNS: Fall back to permissive mode if recursor mode is unavailable
Date: Mon, 06 Mar 2017 12:18:09 -0600	[thread overview]
Message-ID: <1488824289.28849.2.camel@hughes.net> (raw)
In-Reply-To: <1488714156.2451.1.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1485 bytes --]

On Sun, 2017-03-05 at 11:42 +0000, Michael Tremer wrote:
> Hi,
> 
> can you confirm if unbound is running?
> 
> What is the output of /etc/init.d/unbound restart?
> 
> -Michael
> 
> > > > ----<% snip %>----
> > > 
> > > I have nightly commit c016773b9816ad9be4ffc8643c30457e87c094e3
> > > available locally, and will beg my users for downtime to test.
> > > 
> > > Thank you, and best regards,
> > > Paul
> > > 
> > > 
> > 
> > Bad juju - build c016773b couldn't resolve any hosts (other than
> > those in "localdomain").
> > 
> > Provider is "hughes.net" and is the only ISP available (no
> > hardlines
> > or other LOS/NLOS WISPs available).
> > 
> > Tried assigning DNS servers 74.113.60.185 and 156.154.70.1 - no
> > change.
> > 
> > Paul
> > 

Sorry for the lllooonnnggg delay - had to get a testing time window.

Unbound was indeed running - verified with "/etc/init.d/unbound status"

Command and output from "restart":

# /etc/init.d/unbound restart
Stopping Unbound DNS
Proxy...                                          [  OK  ]
Starting Unbound DNS
Proxy...                                          [  OK  ]
Ignoring broken upstream name server(s): 74.113.60.185
156.154.70.1    [ WARN ]
Falling back to recursor
mode                                          [ WARN ]


Thank you,
Paul

  reply	other threads:[~2017-03-06 18:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01 16:11 Michael Tremer
2017-03-01 16:17 ` Michael Tremer
2017-03-01 18:00   ` Paul Simmons
2017-03-03 20:54     ` Paul Simmons
2017-03-05 11:42       ` Michael Tremer
2017-03-06 18:18         ` Paul Simmons [this message]
2017-03-06 21:00           ` Michael Tremer
2017-03-06 21:47             ` Paul Simmons
2017-03-06 22:37               ` Michael Tremer
2017-03-06 23:29                 ` Paul Simmons
2017-03-07 12:06                   ` Michael Tremer
     [not found] <1488903324.21248.2.camel@hughes.net>
2017-03-08 12:09 ` Michael Tremer
2017-03-08 16:19   ` Paul Simmons
     [not found] <1490455220.20288.4.camel@hughes.net>
2017-03-30 16:51 ` Michael Tremer
2017-03-30 18:21   ` Paul Simmons
     [not found] <1490979195.2643.88.camel@ipfire.org>
2017-04-02 16:37 ` Paul Simmons
2017-04-02 18:03   ` Michael Tremer
2017-04-02 19:07     ` Paul Simmons

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1488824289.28849.2.camel@hughes.net \
    --to=redneckmother@hughes.net \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox