<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">My ticket # is sci-251834 and I sent them Shawn's traceroutes as well.</div><div dir="ltr"><br></div><div dir="ltr">Thanks,<br clear="all"><div><div dir="ltr" class="gmail_signature"><div dir="ltr">Eric Rechnitzer<div><a href="mailto:eric.rechnitzer@gmail.com" target="_blank">eric.rechnitzer@gmail.com</a><br></div></div></div></div><br></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Oct 9, 2019 at 11:16 AM Jordan Morris via Outages <<a href="mailto:outages@outages.org">outages@outages.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I think you are correct that this is the root cause a few of the sites even the alternative DNS servers routed out <a href="http://0.ae1.pr0.dca20.tbone.rr.com" rel="noreferrer" target="_blank">0.ae1.pr0.dca20.tbone.rr.com</a> and went dead in the water after that.<br>
<br>
<br>
Jordan Morris<br>
SALES: 800-249-1348<br>
SUPPORT: 888-920-5685<br>
<a href="http://www.crosswindvoip.com" rel="noreferrer" target="_blank">www.crosswindvoip.com</a><br>
2201 N. Camino Principal Ste. 125<br>
Tucson, AZ 85715 <br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: Shawn Solomon <<a href="mailto:sdsolomo@gmail.com" target="_blank">sdsolomo@gmail.com</a>> <br>
Sent: Wednesday, October 9, 2019 8:04 AM<br>
To: Jordan Morris <<a href="mailto:jmorris@crosswindvoip.com" target="_blank">jmorris@crosswindvoip.com</a>><br>
Cc: <a href="mailto:outages@outages.org" target="_blank">outages@outages.org</a><br>
Subject: Re: [outages] Odd name resolution Errors OpenDNS In NC & SC<br>
<br>
potentially related, we are seeing problems with rr/charter/spectrum/brighthouse/tw getting traffic back to level3/centurylink this morning. Seems anything routing via <a href="http://0.ae0.pr0.dca20.tbone.rr.com" rel="noreferrer" target="_blank">0.ae0.pr0.dca20.tbone.rr.com</a><br>
just dies if its destined for as3356. If it takes a path via<br>
Atlanta, works great. Interestingly, both of the following destinations are in the same subnet, just a different fourth octet.<br>
<br>
roampile (0.0.0.0)<br>
Wed Oct 9 10:03:51 2019<br>
Keys: Help Display mode Restart statistics Order of fields quit<br>
<br>
Packets Pings<br>
Host<br>
Loss% Snt Last Avg Best Wrst StDev<br>
1. Linksys20360<br>
0.0% 4 0.8 1.1 0.8 1.9 0.0<br>
2. <a href="http://cpe-69-132-132-1.carolina.res.rr.com" rel="noreferrer" target="_blank">cpe-69-132-132-1.carolina.res.rr.com</a><br>
0.0% 4 11.7 13.3 11.7 16.1 1.9<br>
3. <a href="http://cpe-174-111-099-000.triad.res.rr.com" rel="noreferrer" target="_blank">cpe-174-111-099-000.triad.res.rr.com</a><br>
0.0% 4 20.3 18.7 15.1 22.8 3.4<br>
4. 24.93.70.64<br>
0.0% 4 9.2 13.8 9.2 18.7 4.1<br>
5. <a href="http://ge-5-1-0.rlghncpop-rtr1.southeast.rr.com" rel="noreferrer" target="_blank">ge-5-1-0.rlghncpop-rtr1.southeast.rr.com</a><br>
0.0% 4 34.4 22.7 16.8 34.4 8.2<br>
6. 66.109.10.176<br>
0.0% 4 32.9 32.9 27.2 40.6 5.7<br>
7. <a href="http://ae-2-0.c1.chi75.tbone.rr.com" rel="noreferrer" target="_blank">ae-2-0.c1.chi75.tbone.rr.com</a><br>
0.0% 4 35.9 35.2 29.8 41.3 4.7<br>
8. <a href="http://0.ae0.pr0.dca20.tbone.rr.com" rel="noreferrer" target="_blank">0.ae0.pr0.dca20.tbone.rr.com</a><br>
0.0% 4 30.9 33.7 26.7 48.0 9.7<br>
9. ???<br>
dead..goes no further..<br>
<br>
<br>
roampile (0.0.0.0)<br>
Wed Oct 9 10:04:20 2019<br>
Keys: Help Display mode Restart statistics Order of fields quit<br>
<br>
Packets Pings<br>
Host<br>
Loss% Snt Last Avg Best Wrst StDev<br>
1. Linksys20360<br>
0.0% 7 0.9 1.1 0.8 2.3 0.4<br>
2. <a href="http://cpe-69-132-132-1.carolina.res.rr.com" rel="noreferrer" target="_blank">cpe-69-132-132-1.carolina.res.rr.com</a><br>
0.0% 7 12.8 13.5 6.4 19.3 3.8<br>
3. <a href="http://cpe-174-111-099-002.triad.res.rr.com" rel="noreferrer" target="_blank">cpe-174-111-099-002.triad.res.rr.com</a><br>
0.0% 7 12.3 18.4 11.0 34.4 9.3<br>
4. <a href="http://chrlncnor-vis1.carolina.rr.com" rel="noreferrer" target="_blank">chrlncnor-vis1.carolina.rr.com</a><br>
0.0% 7 13.9 13.9 8.8 21.2 4.2<br>
5. 24.93.67.204<br>
0.0% 7 16.9 18.0 13.8 26.1 4.1<br>
6. <a href="http://bu-ether11.atlngamq46w-bcr00.tbone.rr.com" rel="noreferrer" target="_blank">bu-ether11.atlngamq46w-bcr00.tbone.rr.com</a><br>
0.0% 7 19.3 23.5 19.3 29.6 3.5<br>
7. 66.109.5.125<br>
0.0% 7 14.7 16.7 13.5 22.3 3.3<br>
8. <a href="http://ae-10.edge4.Atlanta2.Level3.net" rel="noreferrer" target="_blank">ae-10.edge4.Atlanta2.Level3.net</a><br>
0.0% 7 19.1 22.2 18.6 32.7 4.8<br>
9. ???<br>
10. hidden in dallas 0.0% 7<br>
38.8 37.5 32.1 41.0 3.5<br>
11. hidden in dallas<br>
0.0% 6 32.7 34.5 32.7 36.9 1.5<br>
<br>
<br>
On Wed, Oct 9, 2019 at 10:27 AM Jordan Morris via Outages <<a href="mailto:outages@outages.org" target="_blank">outages@outages.org</a>> wrote:<br>
><br>
> Seeing some odd name resolutions errors in the NC and SC regions getting random name resolutions that resolve to mail*.<a href="http://newsgeni.us" rel="noreferrer" target="_blank">newsgeni.us</a>. This is happening across multiple domain names even seeing it with reverse IP resolutions. Our monitoring alerts detected this so far at about 10+ sites in those states. The fix has been to move the sites off 208.67.222.222 and 208.67.220.220 and using a different DNS servers/providers. Anyone else seeing similar?<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Outages mailing list<br>
> <a href="mailto:Outages@outages.org" target="_blank">Outages@outages.org</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/outages" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/outages</a><br>
_______________________________________________<br>
Outages mailing list<br>
<a href="mailto:Outages@outages.org" target="_blank">Outages@outages.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/outages" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/outages</a><br>
</blockquote></div>