Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt-3.10.48-2 released
Date: Fri, 25 Jul 2014 12:04:45 -0600	[thread overview]
Message-ID: <CAK-n8j7DS1kiXpEYu-bWo0LJ7=Lpo2wD1EeP=4VQsE2yyOD1ZA@mail.gmail.com> (raw)

Regarding my DNS problems.....

I tried flashing back to 3.10.44-6 but the DNS problems persisted.  So
I cracked open /etc/config/network to discover I was using Google's
DNS servers:

config interface ge00
        option 'ifname' 'ge00'
        option 'proto'  'dhcp'
        option 'dns' '8.8.8.8 8.8.4.4'
        option 'peerdns' '0'

I then tried the OpenDNS servers, but the problems still continued.
Finally, I went back to the Comcast DNS servers (my ISP):

config interface ge00
        option 'ifname' 'ge00'
        option 'proto'  'dhcp'
        option 'dns' '75.75.75.75 75.75.76.76'
        option 'peerdns' '0'

Things seemed to be much better after that.

I then re-flashed 3.10.48-2 and the problems were still gone.

I don't know why all of a sudden trying to use non-Comcast DNS servers
became a problem.  I wonder if has something to do with IPV6.  But I'm
leaving things as-is now.

On Wed, Jul 23, 2014 at 9:44 AM, Jim Reisert AD1C
<jjreisert@alum.mit.edu> wrote:

> I seem to be experiencing random DNS failures with this version.  At
> first I thought it was just a couple of domains (fcc.gov and
> census.gov) but last night it took me a few tries to get to my
> personal web site (ad1c.us).  The problem persists today:
>
> f:\>nslookup census.gov
> Server:  UnKnown
> Address:  2601:1:a980:372::1
>
> DNS request timed out.
>     timeout was 2 seconds.
> *** Request to UnKnown timed-out
>
> f:\>nslookup census.gov
> Server:  UnKnown
> Address:  2601:1:a980:372::1
>
> Non-authoritative answer:
> Name:    census.gov
> Address:  148.129.75.218
>
> I don't remember how to tell which DNS service I'm running, either
> OpenDNS or Comcast.  It's not obvious from the GUI.
>
> Is anyone else experiencing DNS-related issues with this version?

-- 
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us

             reply	other threads:[~2014-07-25 18:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-25 18:04 Jim Reisert AD1C [this message]
2014-07-25 18:08 ` Jim Reisert AD1C
  -- strict thread matches above, loose matches on Subject: below --
2014-07-17 22:18 Dave Taht
2014-07-17 22:36 ` Dave Taht
2014-07-18 14:23 ` Valdis.Kletnieks
2014-07-18 14:31   ` Dave Taht
2014-07-18 14:43     ` Dave Taht
2014-07-18 20:04     ` Dave Taht
2014-07-23 15:44       ` Jim Reisert AD1C

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='CAK-n8j7DS1kiXpEYu-bWo0LJ7=Lpo2wD1EeP=4VQsE2yyOD1ZA@mail.gmail.com' \
    --to=jjreisert@alum.mit.edu \
    --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