Hi Bill,
I am speaking of this root-server system:
a.public-root.net. 900 IN A 205.189.71.2
b.public-root.net. 900 IN A 61.9.136.52
c.public-root.net. 900 IN A 68.255.182.111
d.public-root.net. 900 IN A 205.189.71.34
e.public-root.net. 900 IN A 216.138.219.83
f.public-root.net. 900 IN A 66.15.237.185
g.public-root.net. 900 IN A 199.5.157.131
h.public-root.net. 900 IN A 64.198.89.245
i.public-root.net. 900 IN A 203.187.202.205
j.public-root.net. 900 IN A 57.73.7.89
k.public-root.net. 900 IN A 81.19.74.67
l.public-root.net. 900 IN A 195.214.191.125
m.public-root.net. 900 IN A 205.189.71.26
and I am beeing told by experts that there is no difference to
what other root-server operators have found on their servers.
ICANNed root-server operators look with interest into what
Public-Root has experienced because in the near future they will
have to support more domains than they do today. We do share
information.
I dont count 25% of the root server traffic a minor issue.
With 90% of root server traffic used to be for localhost and with
25% of root server traffic already for local, we are looking into
a major DoS attack. This might overload ISPs DNS servers it might
even bring the root servers down if they let it free!
i'm going to have to raise the point that Peters "root-server" system
is his private "walled-garden" and not representative of the Internet's
authoritative root servers. Just for clarification.
--bill
--
Peter and Karin Dambier
Public-Root
Graeffstrasse 14
D-64646 Heppenheim
+49-6252-671788 (Telekom)
+49-179-108-3978 (O2 Genion)
mail: peter(_at_)peter-dambier(_dot_)de
http://iason.site.voila.fr
http://www.kokoom.com/iason
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf