Delivery-Date: Tue, 21 Oct 2014 23:50:05 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	RP_MATCHES_RCVD autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 0CBB51E0A9A;
	Tue, 21 Oct 2014 23:50:04 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 96E0831118;
	Wed, 22 Oct 2014 03:49:59 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 4AF9630707
 for <tor-talk@lists.torproject.org>; Wed, 22 Oct 2014 03:49:56 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id XTT2PqUxHmD7 for <tor-talk@lists.torproject.org>;
 Wed, 22 Oct 2014 03:49:56 +0000 (UTC)
Received: from mail-lb0-f175.google.com (mail-lb0-f175.google.com
 [209.85.217.175])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id E2C6D305D2
 for <tor-talk@lists.torproject.org>; Wed, 22 Oct 2014 03:49:55 +0000 (UTC)
Received: by mail-lb0-f175.google.com with SMTP id u10so2092299lbd.20
 for <tor-talk@lists.torproject.org>; Tue, 21 Oct 2014 20:49:52 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:date:message-id:subject:from:to
 :content-type;
 bh=PUjg93K5FjUG5ivU8HCVg5Bc4Oi0FwCtgj1Jg3Zxvzg=;
 b=DVy+Dvaew/HSUurhI3RV8f9dvChMN9BmKNWrRTbK6RAfIEbkY/aZxY06otWXw0/aJR
 wFq6lrW0tP7cyMNGljdNUdIY8osQihq7Ek538bMmxYlGmLo1VCtQPvFVmCF+YoiAbRVt
 NRwCrYhWGpk7Wt7UFz0sWe52E+TVj7+s2T83ZzeVddqewxNHCBR8uddqK0XwhbP65SBX
 NdG767KuP8U3ODZtPu9866Xy9BsxetFWMK6S3pACdsqsO8dBCrqiVr14oXMDah3G8DSU
 hY4eFrfRc3p1ZPELoBkShqmo+nwa0aXtCRGq6DJpamsFypVLoPxXkozSFZeIg8Aif4Hz
 FxFQ==
X-Gm-Message-State: ALoCoQlU6txy/pThhfjZrGA2bdvw7xMmseKAvZ1j58pIDZWSuTH1ymrYhMrW6QP04Si8SPE/nly0
MIME-Version: 1.0
X-Received: by 10.112.147.225 with SMTP id tn1mr38952045lbb.37.1413949791960; 
 Tue, 21 Oct 2014 20:49:51 -0700 (PDT)
Received: by 10.112.218.102 with HTTP; Tue, 21 Oct 2014 20:49:51 -0700 (PDT)
Date: Tue, 21 Oct 2014 20:49:51 -0700
Message-ID: <CADoG9xnQO_4v0JXvPah+HwN8UJPanA6QfUfr2+BdMohU8OuELA@mail.gmail.com>
From: Robert Watson <robert@gillecaluim.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [tor-talk] trying to setup tor relay on verizon fios
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Setting up tor relay on verizon fios and not sure what, if anything I can
do about DNS error in log....
*Oct 21 20:38:14.000 [notice] Self-testing indicates your DirPort is
reachable from the outside. Excellent.*
*Oct 21 20:38:15.000 [notice] Self-testing indicates your ORPort is
reachable from the outside. Excellent. Publishing server descriptor.*
*Oct 21 20:38:22.000 [notice] Performing bandwidth self-test...done.*
*Oct 21 20:40:03.000 [notice] Your DNS provider gave an answer for
"elrnjy6c.invalid", which is not supposed to exist. Apparently they are
hijacking DNS failures. Trying to correct for this. We've noticed 1
possibly bad address so far.*
*Oct 21 20:40:03.000 [notice] Your DNS provider has given "92.242.140.21"
as an answer for 10 different invalid addresses. Apparently they are
hijacking DNS failures. I'll try to correct for this by treating future
occurrences of "92.242.140.21" as 'not found'.*

I looked at the verizon router settings and can't set the dns servers
directly.  Can I ignore this notice?
Will I be able to forward dns queries via tor, or is that a different issue
entirely?
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

