Discuss mailing list

[Jonah Aragon <jonaharagon AT gmail.com>]

Spamhaus IS resolving .bit domains, which is rediculous because they don't exist on the normal network. The whole thing is terrible. Spamhaus shouldn't be testing like that.

Jonah

On Dec 17, 2016 3:09 PM, "JC" <jc AT motorsports-x.com> wrote:

Doesn't net neutrality prevent them from blocking entire servers for way?   They should be tageting the single malware producing subdomain. ...  Why is this a problem anyway if spam Hause isnt resolving opennic ip's?   What do you reckon the number of devices is that can actually access . Bit? 

On Dec 17, 2016 14:59, "Jonah Aragon" <jonaharagon AT gmail.com> wrote:

Because other servers aren't pointing to domains that aren't located outside of ICANN's zone.

The issue isn't malware, it's that his DNS server (like all of ours) is resolving .bit domains.

Jonah

On Dec 17, 2016 2:09 PM, "Aaron J. Angel" <aaron.angel AT gmail.com> wrote:

How do they not have every DNS server blacklisted if resolving a domain name pointing to a server hosting malware is good enough to get blacklisted?

On Sat, Dec 17, 2016, 3:01 PM Fusl Dash <opennic AT lists.dedilink.eu> wrote:

On 12/17/2016 08:51 PM, Aaron J. Angel wrote:
> So, another server is hosting malware, and Spamhaus goes to the effort of finding a DNS server that resolves a domain name to that server and blocks it...from doing what, exactly? The DNS server isn't delivering mail content with malware, is it? This makes no sense to me. What am I missing? I wasn't on IRC.

See https://www.spamhaus.org/sbl/query/SBL325026

>
>
> On Sat, Dec 17, 2016, 2:44 PM Theo B <me AT theos.space> wrote:
>
>     Hi -
>
>     So, on thursday a big conversation took place on IRC about Spamhaus deciding to block Fusl's anycast DNS server IPs because a .bit domain was hosting malware. The conversation never really came to a conclusion, so I wanted to throw out some ideas that we talked about.
>
>     Here are some of the options we talked about in IRC:
>
>     1. Just ignore Spamhaus and move along(This could be bad because some ISPs block the IPs that Spamhaus blocks)
>     2. Send them an email explaining what we do, and how we're not responsible for any of the content on .bit.. and then hope they remove it.
>     3. Drop .bit completely, and tell them that the content is no longer there.
>
>     What do you people think about this?
>
>     -Theo
>
>
>     --------
>     You are a member of the OpenNIC Discuss list.
>     You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org <mailto:discuss-unsubscribe AT lists.opennicproject.org>
>
>
>
>
>
> --------
> You are a member of the OpenNIC Discuss list.
> You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org
>

--
Best regards

Fusl - root AT meo.ws - http://meo.ws/

--------
You are a member of the OpenNIC Discuss list.
You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org

--------
You are a member of the OpenNIC Discuss list.
You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org

--------
You are a member of the OpenNIC Discuss list.
You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org