[148792] in North American Network Operators' Group
RE: VZ FiOS DNS issues:
daemon@ATHENA.MIT.EDU (Jamie Bowden)
Mon Jan 23 07:53:49 2012
From: Jamie Bowden <jamie@photon.com>
To: "'Robert E. Seastrom'" <rs@seastrom.com>, Christopher Morrow
<morrowc.lists@gmail.com>
Date: Mon, 23 Jan 2012 12:51:55 +0000
In-Reply-To: <867h0izmuc.fsf@seastrom.com>
Cc: nanog group <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
I don't care for the Actiontec boxes either, but the STB program guides and=
other features don't work without it, so I have mine forward all IP traffi=
c unmolested to my own as the DMZ host (thus the dual layer of [P|N]AT you =
see). It's just UDP/TCP 53 traffic that's not flowing for whatever reason;=
it's every device in the house phones, tablets, computers, you name it, so=
I'm not inclined to attribute it to malware. My neighbor was also seeing =
it (and like last time, it seems to have magically resolved itself after ~1=
.5h). I'm just wondering what Verizon is DOING that they are screwing up t=
heir own DNS traffic. If they were capturing my queries and sending them t=
o their own servers (I actually have Google's public facing servers at the =
top of the list handed out by DHCP) that would be one thing (irritating to =
be sure, but they aren't, so it's not), but when I'm explicitly hitting a n=
ame server down the street in Reston that VZ run and it's failing the same =
way? It makes me wonder.
Jamie
> -----Original Message-----
> From: Robert E. Seastrom [mailto:rs@seastrom.com]
> Sent: Monday, January 23, 2012 6:21 AM
> To: Christopher Morrow
> Cc: nanog group
> Subject: Re: VZ FiOS DNS issues:
>=20
>=20
> Christopher Morrow <morrowc.lists@gmail.com> writes:
>=20
> > On Sun, Jan 22, 2012 at 11:29 AM, Brandon Kim
> > <brandon.kim@brandontek.com> wrote:
> >>
> >> I have FIOS and I have no issues. However I do know awhile back they
> had issues and I was affected by
> >> the outage....
> >>
> >> Maybe it hasn't made its way to me yet....
> >>
> >
> > there have been instances over the time i've been a fios customer
> that
> > 'upgrades' to devices in the field have caused this problem (last was
> > ~2wks ago? in the washington, dc area).
> >
> > Could be you are seeing this problem affecting you :(
>=20
> I'm a FIOS customer (LATA 246 not 236 like Chris), and haven't had any
> issues with the network. On the other hand, between my location and
> the fact that I'm on an old BPON build, perhaps the software upgrades
> haven't affected me. To further complicate things, ever suspicious of
> ISP nameservers that don't do DNSSEC validation and monetize rcode 3,
> and not a fan of the Actiontec boxes that Verizon hands out I run my
> own cacheing nameserver (hand-built openbsd+pf on embedded hardware
> with latest bind or unbound and isc dhcpd).
>=20
> Do things magically start working for you if you hard-code 8.8.8.8 or
> 4.2.2.1 or one of the other usual suspects? That would seem to be a
> quick way of narrowing it down a bit.
>=20
> -r
>=20
