Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Aristar <LeetMiniWheat@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Upgraded to 3.10.38-1, DNS issues?
Date: Sun, 11 May 2014 13:54:00 +0200	[thread overview]
Message-ID: <BE017D02-8582-4C90-9794-741499925E5E@gmx.de> (raw)
In-Reply-To: <CAGHZhqHjVfGgO02uJp253wAuzJKUf-aGoOL1m+LASgTvx74SdA@mail.gmail.com>

Hi Aristar,


On May 9, 2014, at 18:17 , Aristar <LeetMiniWheat@gmail.com> 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.

	I think Dave changed the default for 3.10.38-2 to avoid the negative proof checks, and that, at least on my system, made automatic DNS configuration though my upstream router functional again. I had the same issues as you with 3.10.38-1 and some earlier ones. So you might want to test the latest cerowrt to see whether that solves the issue. (I think there was some discussion of how DNS recurs or work differently with DNSSEC than dnsmasq, which operates as a forwarder.)

Best Regards
	Sebastian

> 
> 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
> 
> 
> On Fri, May 9, 2014 at 5:34 AM, Aristar <LeetMiniWheat@gmail.com> wrote:
>> Sorry if this is a dumb question but I'm not sure what's changed since
>> 3.7.5 but I can't get DNS working. my resolv.conf says 127.0.0.1, the
>> /tmp/resolv.conf.auto has valid dns servers and I can't resolve
>> anything locally on the router via ssh or on any client device. I CAN
>> get dns LOCAL only if I add a dns server to /etc/resolv.conf but
>> clients using nameserver 172.30.42.1 can't
>> 
>> Any ideas? I did a fresh install/clean configs and it isn't working
>> out of the box or with any GUI or manual editing I've tried.
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel


  parent reply	other threads:[~2014-05-11 11:54 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
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 [this message]
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=BE017D02-8582-4C90-9794-741499925E5E@gmx.de \
    --to=moeller0@gmx.de \
    --cc=LeetMiniWheat@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