Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] EMC - peering problem - UPDATE

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] EMC - peering problem - UPDATE


Chronological Thread 
  • From: David <davidvargas1 AT mac.com>
  • To: discuss AT lists.opennicproject.org
  • Subject: Re: [opennic-discuss] EMC - peering problem - UPDATE
  • Date: Mon, 08 Jun 2015 02:59:19 +0800


Agree totally

I/m in Asia, and the local opennick servers of Singapore, japan, and HK
are not showing up at all.


On 6/7/2015 8:10 AM, Jeff Taylor wrote:
> Please see Julian's message from Jun 04 -- [MIGRATION]
> www.opennicproject.org -- which already noted that the table of nearest
> servers is currently not working. In fact I'm not even sure where that
> page is getting its information because 195.34.136.145 isn't even in our
> list of servers, and the two that returned NXDOMAIN have been marked for
> deletion due to failure to maintain a valid root zone. You can see the
> accurate list of opennic public servers here:
> http://wiki.opennicproject.org/Tier2
>
> For the best source of nearest servers, please see my post on May 07 --
> GeoIP list of nearest OpenNIC servers -- which will allow you use URL
> parameters to generate different forms on the information. You can see
> the help information by browsing to
> https://api.opennicproject.org/geoip/?help
>
> I did a check of a few random servers around the US, and they all seem
> to be resolving the .lib zone correctly. Please try selecting DNS
> servers suggested from the API page, I believe you will have much better
> results.
>
>
> On 06/05/2015 04:04 PM, Oleg Khovayko wrote:
>> Hi,
>>
>> After some investigation I found:
>> Four servers, provided by your page
>> https://www.opennicproject.org/nearest-servers/ as nearest to me,
>> aren't really nearest.
>>
>> I live near Wash, DC, USA, and real OpenNIC nearest are:
>> 75.127.14.107;
>> 104.237.144.172;
>> 107.170.95.180;
>> 69.28.67.83;
>>
>> But, your geolocation system shows wrong nearest:
>>
>> 185.16.40.143 (MD, ES) 87.216.170.85 (MD, ES) 109.69.8.34 (BCN, ES)
>> 195.34.136.145 (T, AT)
>>
>> And, by fact, from those "nearest" only one works correct with peering
>> (109.69.8.34).
>>
>> Thus, I assume, you need pay attention to:
>> - restore search engine for "nearest search".
>> - remove dead T2 server 195.34.136.145 from database.
>> - check, why another T2 servers 185.16.40.143 and 87.216.170.85 do
>> not work correctly.
>>
>> Thanks,
>> Oleg
>>
>>
>>
>>
>> --------
>> 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
>



Archive powered by MHonArc 2.6.19.

Top of Page