discuss AT lists.opennicproject.org
Subject: Discuss mailing list
- From: David <davidvargas1 AT mac.com>
- To: discuss AT lists.opennicproject.org, shdwdrgn AT sourpuss.net
- Subject: Re: [opennic-discuss] Root zone testing
- Date: Thu, 11 Sep 2014 08:19:37 +0800
In my opinion, feel free to correct ME.
what exactly is define as "root Zone and dnssec entries in opennic
This what I understand of DNSSEC
I read LOTS of article about it and honestly, it could be counter
productive and use as a tool of censorship or too much power to the Isp/
hostile governments. It does not help De-centralizing the internet.
What operational statistics have we gathered about DNSSEC?
Is it changing DNS patterns?
How are our name servers handling DNSSEC traffic? Is the volume as
Have we seen anything other unusual incidents?
Are there experiences being documented in the form of best practices,
or something similar, for transfer of signed zones?
I was wondering, How that will affect "tor users"
I'm not in favor of root zone, but favor openness, that will give too
much "power" to the regimental ISP, meaning they could force you to use
their default DNS tier2 ican settings in their local web servers.
For example: I discover that my local ISP is making extra money on the
consumers by re-routing their base-band to 18.104.22.168.
Due to my bandwidth limitations, I noticed that was a main factor for
lagging at certain hours during the day.
When I discover through my perseverance and research that opennic
offered a few DNS servers free from finger printing, and with faster
pings/tlc to my region, which is Singapore and Japan.
Knowing this I had no issues and I'm able to cap my maximum base-band
of my pc by redirecting my DNS to Japan or Singapore.
Let us be clearly understood that the Philippines IS MONOPOLIZED by 2
major telecom, Smart and Globe.
Globe owns or has bought rights to 3 major fiber optical transoceanic
under water cables. Including one of them from the Philippines to Japan.
This oceanic cables does not traverse across the Planet like the other
ones. Yet it is beneficial for opennic users like me.
because Japan opennic dns Is free and very stable.
Singapore opennic has its moments of glory and a lot of lag, too much
of it. So they sit on second place.
Even 22.214.171.124 is super fast, but they "DON'T RESPECT PRIVACY", they
finger print your browsing habits. I only use 126.96.36.199 when the other
opennic DNS are having "DIGITAL HICCUPS OR ASTHMA".
On 9/9/2014 1:49 AM, Jeff Taylor wrote:
> A recent discussion has brought up the possibility that not all tier2
> servers may be carrying the same root zone, or even staying up to date
> with the file. This came to light when a user noticed they couldn't
> resolve an icann TLD that was created this April.
> So I would like to start a discussion on policies and testing
> methodology. First, what should we consider to be a standard policy for
> the public tier2 servers? The wiki pages on setting up a tier2 server
> all state that the root zone should be slaved from NS0, however if you
> are not running BIND then slaving a zone may not be possible (although
> this setup should be passing the queries on to one of the tier1
> servers). There is also the situation where some folks also run servers
> for other alt-roots, and they may not have the tools available to merge
> multiple root zones together... Do we want to enforce the usage of the
> opennic root zone for tier2 servers (complete with dnssec entries), or
> do we want to keep the openness that our project was created on, and
> allow for the possibility of other root zones?
> Second, how should we test for functionality of the root zone? If we
> insist on everyone using opennic's root, then it could be as simple as
> checking the serial and making sure it is within a couple days of what
> NS0 has posted. However if we want to remain open, we still want to
> ensure that the tier2 servers are carrying recent changes to
> icann/opennic TLDs, but how do we detect that? It could be quite a
> chore to try and detect every time a new TLD is added to the icann list,
> and we certainly couldn't reply on matching the serial for the root zone
> if everyone is using a different source.
> One more point -- the server that caused the original discussion has
> been updated, so at this point every tier2 server is currently resolving
> an up-to-date opennic root zone. This means if we wanted to make it a
> policy to require the use of our root, nobody would have to change
> anything, and the policy would only have to be enforced moving forward
> with new servers.
> You are a member of the OpenNIC Discuss list.
> You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org
- [opennic-discuss] Root zone testing, Jeff Taylor, 09/08/2014
- Re: [opennic-discuss] Root zone testing, Guillaume Parent, 09/08/2014
- Re: [opennic-discuss] Root zone testing, David, 09/10/2014
Archive powered by MHonArc 2.6.19.