Dns-operations mailing list

[Alex Hanselka <alex AT opennicproject.org>]

It is impossible for us. It is extremely expensive in both initial and 
maintenance costs. 

On May 16, 2012, at 2:23 PM, Joshua Berriadias wrote:

> Anycast is very well possible, OpenDNS uses Anycast. We could do the same, 
> it's just a matter of HOW...
> 
> -----Original Message-----
> From: dns-operations-request AT lists.opennicproject.org 
> [mailto:dns-operations-request AT lists.opennicproject.org] On Behalf Of Alex 
> Hanselka
> Sent: Wednesday, May 16, 2012 3:12 PM
> To: dns-operations AT lists.opennicproject.org
> Subject: Re: [opennic-dns-operations ] Server removal
> 
> I agree, in this respect.  I think the key to getting the users support is 
> to either offer a program of some sort to change their DNS and thus the 
> program would know if a server was going down, or somehow do Anycast (which 
> is super impossible for the record, but that is an option)
> 
> 
> 
> 
> On May 16, 2012, at 1:18 PM, mike wrote:
> 
>> Travis,
>> 
>> I am sorry but I would tend to disagree on this.
>> 
>> What if a person is mostly not doing inter-web for instance? One might 
>> be doing p2p development or ssh/telnet (.bbs for instance does a lot 
>> of that), I think it's more troublesome to troubleshoot if you send 
>> back the wrong IP address than if you simply don't respond.
>> 
>> I understand the argument for the redirecting, I just speak from 
>> experience that it can be a frustrating and time consuming issue to 
>> debug when you observer that you can ping "domain.tld" but your 
>> application does not seem to be able to connect to the port you are 
>> expecting to be able to connect to, only to eventually discover that 
>> you are being handed the wrong IP address by the DNS resolver.
>> 
>> I think that a good solution to the somewhat transient nature of the 
>> OpenNIC resolver pool is a client-side resolver evaluator along the 
>> lines of http://sourceforge.net/projects/opennicwizard/ although I am 
>> a little partial toward that particular effort. I am suggesting that 
>> the transient nature of the resolver pool seems to ask for a 
>> client-side solution that is adaptable to resolvers coming and going, 
>> until we can get a lot more OpenNIC-friendly ISPs on board.
>> 
>> PS. I currently do not advocate using OpenNICWizard in a production 
>> environment, although it is working quite well in many regards, it is 
>> still in development. Also, for those who have been waiting, another 
>> OpenNICWizard release is due out shortly, I freely admit that I am 
>> guilty of slacking, sorry.
>> 
>> - --Mike
>> 
>> On 05/16/2012 03:39 AM, Travis McCrea wrote:
>>> Before a server is removed from service, I feel the T2 operator 
>>> should redirect all queries to a page telling them that their DNS 
>>> server will be disabled soon and that they should use new servers… 
>>> this way people don't just have their DNS queries just stop 
>>> responding Travis McCrea Deputy Leader, Pirate Party of Canada Chief 
>>> Administrative Officer, Pirate Parties International Captain, United 
>>> States Pirate Party (PNC) Member, Washington State Pirate Party
>>> 
>>> Canada: 1(778)709-4859 US: 1(206)552-8728
>>> 
>>> Twitter: @TeamColtra Facebook: fb.me/teamcoltra Blog:
>>> http://travismccrea.com
>>> 
>>> The views expressed in this email represent my own personal values 
>>> and not the values of the Pirate Party, the Pirate Ideology, or any 
>>> of my associations.
>>> 
>>> On 2012-05-15, at 5:29 AM, Jon Plews wrote:
>>> 
>>>> Hi,
>>>> 
>>>> Please remove 89.16.173.11 from the server lists, it will be going 
>>>> away by the end of the year. It is being replaced by
>>>> 213.138.101.252
>>>> 
>>>> Regards
>>>> 
>>>> Jon
>>> 
>>> 
>> 
> 
>

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail