Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Robert Bradley <robert.bradley1@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Upgraded to 3.10.38-1, DNS issues?
Date: Sat, 10 May 2014 13:15:58 +0100	[thread overview]
Message-ID: <536E187E.4000800@gmail.com> (raw)
In-Reply-To: <CAGHZhqHjVfGgO02uJp253wAuzJKUf-aGoOL1m+LASgTvx74SdA@mail.gmail.com>

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

On 09/05/2014 17:17, Aristar wrote:
> Okay I figured it out. It was DNSSEC I didn't realize it was enabled
> by default so I had to comment out the lines in /etc/dnsmasq.conf but
> I still had to manually specify a nameservers in a separate config
> under LUCI Network>DHCP and DNS>Resolv and Hosts Files>"Resolve file"
> and all is well again.
>
> Now to set up dnscrypt-proxy again which actually has a repository now
> and instructions for building from source. (Seems more reliable than
> DNSSEC anyways, though I have not read too much on DNSSEC).
>
> src/gz exopenwrt http://exopenwrt.and.in.net/ar71xx/packages
>
> https://forum.openwrt.org/viewtopic.php?id=36380&p=1
>
>

Out of interest, which upstream DNS servers were you using when DNSSEC
was blocked?  I noticed fairly recently that some Wi-Fi networks (Global
Gossip, using filtered OpenDNS upstream) refused all dnssec-enabled
requests with NXDOMAIN.  This was testing with a custom-built dnsmasq
2.70 on Ubuntu, but the same setup works fine behind both CeroWRT and
other DNSSEC-capable servers that I tried.

-- 
Robert Bradley



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]

  reply	other threads:[~2014-05-10 12:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09  9:34 Aristar
2014-05-09 16:17 ` Aristar
2014-05-10 12:15   ` Robert Bradley [this message]
2014-05-11 21:46     ` Robert Bradley
2014-05-11 21:48     ` Robert Bradley
2014-05-10 18:42   ` Aristar
2014-05-12  8:09     ` Maciej Soltysiak
2014-05-11 11:54   ` Sebastian Moeller
2014-05-11 12:14     ` Aristar

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=536E187E.4000800@gmail.com \
    --to=robert.bradley1@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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