Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] [URGENT] [ROUND-ROBIN] DNS POISONING/POSSIBLE MITM ATTACK

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] [URGENT] [ROUND-ROBIN] DNS POISONING/POSSIBLE MITM ATTACK


Chronological Thread  
  • From: <vv AT cgs.pw>
  • To: discuss AT lists.opennicproject.org
  • Subject: Re: [opennic-discuss] [URGENT] [ROUND-ROBIN] DNS POISONING/POSSIBLE MITM ATTACK
  • Date: Wed, 1 Sep 2021 16:47:50 -0700

Thanks for reporting this. I have had a similar
problem but didn't completely diagnose it here
with my slightly convoluted system. However,
I have been using 185.121.177.177 as one of
my DNS choices for a long time, so your report
is very helpful.

I haven't checked for a long time, nor looked
at the Opennic site with servers. However, last
I knew that *.*.*.177 server was run by fusl,
who is/was a member here. I didn't know anything
had changed in that regard.

Regards,
Ole

---
On Wed, 1 Sep 2021 13:46:17 -0700
Se7en <se7en AT cock.email> wrote:

> On 21-08-31 16:10:25, Se7en wrote:
> > [Snip]
>
> Today, I switched back to check if the problem has been
> resolved. It has not. The DNS continues to be poisoned. I
> am providing the traceroute for the Anycast in text.
>
> $ traceroute 185.121.177.177
> traceroute to 185.121.177.177 (185.121.177.177), 30 hops
> max, 60 byte packets 1 www.routerlogin.com (192.168.1.1)
> 1.027 ms 0.985 ms 1.047 ms 2 [REDACTED] 7.015 ms
> 11.252 ms 11.315 ms 3 100.127.5.182 (100.127.5.182)
> 12.099 ms 12.075 ms 12.047 ms 4 100.120.102.40
> (100.120.102.40) 11.786 ms 11.851 ms 11.715 ms 5
> 68.1.4.252 (68.1.4.252) 17.560 ms 17.419 ms 17.506 ms
> 6 68.105.30.146 (68.105.30.146) 21.352 ms 17.797 ms
> 17.648 ms 7 63.223.47.122 (63.223.47.122) 44.426 ms
> 44.305 ms 45.681 ms 8 205.177.32.98 (205.177.32.98)
> 46.271 ms 46.254 ms 46.287 ms 9 * * * 10 * * *
> 11 * * *
> 12 * * *
> 13 * * *
> 14 * * *
> 15 * * *
> 16 * * *
> 17 * *
>
>




Archive powered by MHonArc 2.6.24.

Top of Page