ate with a recently
launched root server that few people are yet dependent on.
Hope my comments help you interpret the data.
kindest regards
joe baptista
--
Joe Baptistawww.publicroot.org
PublicRoot Consortium
---
, either
old or new IPv4 address.
Incidentally - just how much traffic is this representative of? How
many queries came in during the period the data was captured?
Thanks for the clarification.
regards
joe baptista
regards
joe baptista
I have already spoken to CAIDA about supplying them with
million and 864 million queries. So a fairly big
sample.. I would estimate that it is somewhere inbetween at about 750
million.
Interesting. Just doing some more estimating - what percentage of those
queries, or how are they divided between the old and new IP.
regards
joe baptista
I'll
for us? Whats going on.
Another very interesting thing is the incredible power behind one IP
number when it has experienced root activity. It only takes one rogue
root to highjack the entire root system. Its been done twice now in
internet history. How is that possible?
regards
joe baptista
an
supervision whatsoever.
what is really strange is that icann and the community have not learned
from this and continue to replace root IP numbers in what is a static
root system.
indeed very demure mr manning.
cheers
joe baptista
--
Joe Baptistawww.publicroot
ta compared to data
from f.root. f.root is a true legacy root system. I think it's been
around from the beginning and may be an excellent comparison to the
progress of the L root fragmentation.
cheers
joe baptista
It's nice to think that resolvers will automatically fix themse
lling participate. Not many do. Not many know
about AS112.
regards
joe baptista
--
Joe Baptistawww.publicroot.org
PublicRoot Consortium
The future of the Internet is Open, Transparent, Inclusive,
Represent
Paul Vixie wrote:
[EMAIL PROTECTED] (Joe Baptista) writes:
No it can't be done with BIND. Very lame. It would be a big asset to
root technology of the entire "*." wildcard TLD label could be pointed
to AS112. AS112 is truly the blackhole of this universe we call the
i
to AS112. AS112 is truly the blackhole of this universe we call the
internet. AS112 - the internet garbage can.
I support using AS112 for that. Great way to reduce the error traffic
at root-servers.net.
regards
joe baptista
--
Joe Baptistawww.publi
flexible and allow that.
regards
joe baptista
--
Joe Baptistawww.publicroot.org
PublicRoot Consortium
The future of the Internet is Open, Transparent, Inclusive,
Representative & Accountable to
elf. But
will eventually. I pray it is the case. Any root operator would
welcome a trash can for bogus traffic.
and its christmas time. what a wonderful gift.
regards
joe baptista
--
Joe Baptistawww.public
can't see them. Thats why you have so much bogus root traffic.
>
>
>I said COPY. I did not say "THEIR OWN ROOT". A copy needs to
>be kept up to date or it ceases to be a copy. It becomes a
>snapshot.
>
&
elp the user in the end. Would it
be more appropriate in my example above that the legacy root simply
recognize Chinese national tlds? That would get rid of some of the error
traffic of the root and do a service to travelers from china.
Think users - not roots.
cheers
joe baptista
t to AS112.
What we want and need is stability and world wide resolvability. What were
getting is a revolution.
regards
joe baptista
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
t; happened anyway).
Exactly - such happened a long time ago - the multi root universe.
regards
joe baptista
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
Gerv:
I asked you a question earlier in this conversation but have yet to get a
response. So I will ask it again.
What happens if a TLD is not on the Public Suffix list?
regards
joe baptista
--
Joe Baptista
www.publicroot.org
PublicRoot Consortium
ave you answered by question yet - or put it on the web
site? What happens to your web browsers behavior if I try to surf a TLD not
on the list?
cheers
joe baptista
--
Joe Baptista
www.publicroot.org
PublicRoot Consortium
---
not on the list?
Thanks in advance for your answer.
Joe Baptista
--
Joe Baptista
www.publicroot.org
PublicRoot Consortium
The future of the Internet is Open, Transparent, Inclusive, Repre
XFR wide open, at least for this client
> l.root-servers.net does not leave AXFR wide open, at least for this client
> m.root-servers.net does not leave AXFR wide open, at least for this client
>
Thats not bad. I remember a time when only the f root would AXFR. 5 out of
13 is not bad.
Are there any configuration changes that can be made to bind to force it to
only use TCP as opposed to UDP?
regards
joe baptista
--
Joe Baptista
www.publicroot.org
PublicRoot Consortium
The future of the Internet is Open
Thats not impressive. If it were not
for my putting an end to the European HEX that amount today would be more
like 40%. Back then the HEX accounted for a 5% drop in ICANN's market share
of root services.
later
joe baptista
--
Joe Baptista
ww
y businesses are going to end up paying big bucks
to protect themselves and even bigger bucks to deploy the DNSSEC patch. The
BIND boys are marketing gurus.
cheers
joe baptista
--
Joe Baptista
www.publicroot.org
PublicRoot Consortium
-
S recursive
servers is to integrate a smart IDS and firewall solution. Commerce needs
solutions - not more patches to patch the patches that should have been
patched years ago.
cheers
joe baptista
--
Joe Baptista
www.publicroot.org
PublicRoot Consortium
---
e a very interesting experiment. And finally a good test of
DNSSEC. Great for consultants.
cheers
joe baptista
--
Joe Baptista
www.publicroot.org
PublicRoot Consortium
The future of the
e a
transition to DNSSEC of all domains like this will. I wish them luck and
look forward to the results of this modest experiment.
regards
joe baptista
Joe Baptista
www.publicroot.org
PublicRoot Consortium
The future of th
.
Oh well - sorry for the interruption - and carry on.
cheers
joe baptista
On Wed, Mar 11, 2009 at 10:57 AM, Edward Lewis wrote:
> At 8:19 +1100 3/11/09, Mark Andrews wrote:
>
>> In message , Edward Lewis writes:
>>
>
> record involves less typing than a DNSKEY, I&#x
contrasting
> the info in the root zone is a valuable service to have.
>
Don't expect that to happen. Once the root is signed it is prudent to remove
DLV so as to ensure complete root slavery.
regards
joe baptista
___
DNSOP mailing list
DNSOP@i
rks?
That would certainly be an innovative move forward for the ietf.
cheers
joe baptista
On Thu, Feb 18, 2010 at 10:54 AM, Todd Glassey wrote:
> The real answer Tony is coming out of left field and it is the legal
> claims being asserted against people intentionally fielding code they know
. Todd is asking you how many
people in management positions at the IETF are black. Or as they used to
call them in the ol south - People of "color" or "Negroes" or the more
vulgar derisive and offensive term "niggers".
regards
joe baptista
_
Have you boys seen this yet?
http://twitter.com/joebaptista/status/9555178362
regards
joe baptista
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
My recommendation - upgrade your NAT.
regards
joe baptista
On Sun, Mar 7, 2010 at 3:06 AM, George Barwood <
george.barw...@blueyonder.co.uk> wrote:
> I have been wondering about this.
>
> For a resolver behind a NAT firewall that removes port randomization,
> it is possible
31 matches
Mail list logo
