discuss AT lists.opennicproject.org
Subject: Discuss mailing list
List archive
Re: [opennic-discuss] !ATTENTION! FurNIC Sponsored T1 178.63.145.230 aka ns4.opennic.glue ceasing OpenNIC operation immediately(no .bit / no recusion)
Chronological Thread
- From: Jonah Aragon <jonaharagon AT gmail.com>
- To: discuss <discuss AT lists.opennicproject.org>
- Subject: Re: [opennic-discuss] !ATTENTION! FurNIC Sponsored T1 178.63.145.230 aka ns4.opennic.glue ceasing OpenNIC operation immediately(no .bit / no recusion)
- Date: Thu, 18 May 2017 14:05:17 -0500
On a minor tangent, I wonder if we should reconsider peering the Namecoin and Emercoin zones. They seem to be causing more trouble than they're worth, and we don't even seem to have a true peering agreement with us as far as I can tell, we resolve their names but not vice versa.
In my opinion we should drop their zones unless they can agree to include our zones in their official DNS clients. I have my doubts we can do this with Namecoin but perhaps we could convince Emercoin to do this as we have a bit of an official relationship with them.
Just my two cents on the whole thing.
Jonah
On May 18, 2017 1:59 PM, "Jonah Aragon" <jonaharagon AT gmail.com> wrote:
ISP's DNS servers are generally whitelisted internally (to their customer network) so they don't have to deal with stuff like that, with a few exceptions, ours on the other hand are publicly accessible to anyone.The issue doesn't seem to be with Spamhaus necessarily here however, it seems to be with the hosting provider ns4 is using, because they'd rather block a paying customer than have an IP blacklisted by a spam organization (which may be a good trade-off for them, who knows, I have no idea how much is being paid for ns4's servers). For example if Spamhaus came after me I could easily just laugh and not pay them attention because my hosting providers aren't going to care, and I'm not going to care because being blacklisted generally doesn't come with many consequences outside of email deliverability. The provider for ns4 on the other hand was prepared to completely nullroute their network.There's definitely an issue here with misunderstanding between us, Spamhaus, and our hosting providers, but it should be a fairly trivial task to move to a provider who won't be swayed so easily by random third party organizations.That's how I see it at least.Jonah
- [opennic-discuss] !ATTENTION! FurNIC Sponsored T1 178.63.145.230 aka ns4.opennic.glue ceasing OpenNIC operation immediately(no .bit / no recusion), Stephan Jauernick, 05/18/2017
- Re: [opennic-discuss] !ATTENTION! FurNIC Sponsored T1 178.63.145.230 aka ns4.opennic.glue ceasing OpenNIC operation immediately(no .bit / no recusion), Daniel Shirley, 05/18/2017
- Re: [opennic-discuss] !ATTENTION! FurNIC Sponsored T1 178.63.145.230 aka ns4.opennic.glue ceasing OpenNIC operation immediately(no .bit / no recusion), Daniel Quintiliani, 05/18/2017
- Re: [opennic-discuss] !ATTENTION! FurNIC Sponsored T1 178.63.145.230 aka ns4.opennic.glue ceasing OpenNIC operation immediately(no .bit / no recusion), Zach Gibbens, 05/18/2017
- Re: [opennic-discuss] !ATTENTION! FurNIC Sponsored T1 178.63.145.230 aka ns4.opennic.glue ceasing OpenNIC operation immediately(no .bit / no recusion), Jonah Aragon, 05/18/2017
- Re: [opennic-discuss] !ATTENTION! FurNIC Sponsored T1 178.63.145.230 aka ns4.opennic.glue ceasing OpenNIC operation immediately(no .bit / no recusion), Jonah Aragon, 05/18/2017
- Re: [opennic-discuss] !ATTENTION! FurNIC Sponsored T1 178.63.145.230 aka ns4.opennic.glue ceasing OpenNIC operation immediately(no .bit / no recusion), Zach Gibbens, 05/18/2017
- Re: [opennic-discuss] !ATTENTION! FurNIC Sponsored T1 178.63.145.230 aka ns4.opennic.glue ceasing OpenNIC operation immediately(no .bit / no recusion), Jonah Aragon, 05/18/2017
- Re: [opennic-discuss] !ATTENTION! FurNIC Sponsored T1 178.63.145.230 aka ns4.opennic.glue ceasing OpenNIC operation immediately(no .bit / no recusion), Daniel Quintiliani, 05/18/2017
- Re: [opennic-discuss] !ATTENTION! FurNIC Sponsored T1 178.63.145.230 aka ns4.opennic.glue ceasing OpenNIC operation immediately(no .bit / no recusion), Daniel Shirley, 05/18/2017
Archive powered by MHonArc 2.6.19.