[167249] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: Comcast DNS Issue?

daemon@ATHENA.MIT.EDU (Childs, Aaron)
Thu Dec 5 11:12:19 2013

From: "Childs, Aaron" <aaron@westfield.ma.edu>
To: 'Christopher Morrow' <morrowc.lists@gmail.com>
Date: Thu, 5 Dec 2013 16:09:57 +0000
In-Reply-To: <CAL9jLaY0b3tkn_t6Xe4YypUh6m2PxXFtq==LLSfFxtsguiGRGA@mail.gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

Yes clients had both IPs in their relative DNS configuration settings.


Aaron Childs, CCNA
Associate Director, Networking
Information Technology
www.westfield.ma.edu/it=20
Please Note: new e-mail address - aaron@westfield.ma.edu


-----Original Message-----
From: christopher.morrow@gmail.com [mailto:christopher.morrow@gmail.com] On=
 Behalf Of Christopher Morrow
Sent: Thursday, December 05, 2013 11:09 AM
To: Childs, Aaron
Cc: Ulf Zimmermann; nanog@nanog.org
Subject: Re: Comcast DNS Issue?

On Thu, Dec 5, 2013 at 11:02 AM, Childs, Aaron <aaron@westfield.ma.edu> wro=
te:
> Our issue was that 75.75.75.75 was not responding to queries at all and f=
or some reason clients weren't getting redirected to 75.75.76.76.

did the clients not have 75.75.76.76 in their resolv.conf (or
equivalent) as the second nameserver entry? that 'redirect' is the host-os =
knowing it has more than one 'nameserver' to ask questions of, right? so wi=
thout the config... you are SOL.


home help back first fref pref prev next nref lref last post