-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
During the root zone (.) update later today, specifically with root
zone serial number 2003090501, the entries for .org will me modified.
The current zone entry contains the following authoritative
nameservers for the .org tld:
org. 2D IN NS A7.NSTLD.COM.
org. 2D IN NS L7.NSTLD.COM.
org. 2D IN NS G7.NSTLD.COM.
org. 2D IN NS F7.NSTLD.COM.
org. 2D IN NS M5.NSTLD.COM.
org. 2D IN NS TLD1.ULTRADNS.NET.
org. 2D IN NS TLD2.ULTRADNS.NET.
org. 2D IN NS J5.NSTLD.COM.
org. 2D IN NS I5.NSTLD.COM.
org. 2D IN NS C5.NSTLD.COM.
org. 2D IN NS E5.NSTLD.COM.
Effective with the 2003090501 load, the entry will reflect the
removal of the Verisign NSTLD.COM nameservers. The zone entry will
therefore contain the following only:
org. 2D IN NS TLD1.ULTRADNS.NET.
org. 2D IN NS TLD2.ULTRADNS.NET.
If you have the 9 ??.NSTLD.COM nameservers cached or hard coded in
any way, you may wish to flush your cache or modify your nameservers
in the near future to avoid any inconsistent or stale data, and you
may want to make your system administrators, NOCs and customer
support groups aware of the changes.
The .org zone file will continue to be pushed to the Verisign
nameservers for a short period of time. However due to the fact that
the UltraDNS nameservers publish and propagate zone changes globally
within 5 minutes, rather than the twice daily update schedule of the
Verisign nameservers, answers from the NSTLD.COM nameservers may be
out of date and inconsistent with the actual SOA for up to 24 hours
after a change is accepted by the Public Interest Registry (PIR.org).
Any questions or concerns regarding this change should be directed to
the PIR (http://www.pir.org).
Sincerely,
Rodney Joffe
CTO and Chairman
UltraDNS Corp.
http://www.ultradns.com
-----BEGIN PGP SIGNED MESSAGE-----
Rodney Joffe wrote:
During the root zone (.) update later today, specifically with root
zone serial number 2003090501, the entries for .org will me modified.
<SNIP>
org. 2D IN NS TLD1.ULTRADNS.NET.
org. 2D IN NS TLD2.ULTRADNS.NET.
From your FAQ:
8<------------------
Q. Do you support IPv6?
A. Our back-end server software already supports IPv6. All systems will be set up to handle IPv6 when/if it becomes a widely adopted standard on the Internet.
- ------------------>8
This talks about transport, but how about AAAA's for NS's and their glue?
Do these ultra super duper servers allow that in .org?
And when do you think that will happen?
$ host -t aaaa TLD1.ULTRADNS.NET.
TLD1.ULTRADNS.NET AAAA record currently not present
$ host -t aaaa TLD1.ULTRADNS.NET.
TLD2.ULTRADNS.NET AAAA record currently not present
Greets,
Jeroen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Jeroen,
Jeroen Massar wrote:
This talks about transport, but how about AAAA's for NS's and their
glue? Do these ultra super duper servers allow that in .org?
And when do you think that will happen?
Ignoring the possible sarcasm ;-)...
1) The UltraDNS nameserver does fully support IPv6.
$ host -t aaaa ipv6-gw.juniper.net udns1.ultradns.net
Using domain server:
Name: udns1.ultradns.net
Address: 204.69.234.1#53
Aliases:
ipv6-gw.juniper.net has AAAA address 3ffe:28ff:9::1
2) As far as TLD IPv6 records, this question would have to be
referred to the TLD registry operator. If they allow it, we support
it. I am not aware of any of the tlds that we are authoritative for
actually inserting any domain records with IPv6 data, but I could be
wrong.
3) We're working on a native IPv6 feed to all of our nodes, and would
hope to have this live and active before the end of this year.
Anycast creates an additional challenge for us in deploying IPv6.
I hope that answers your questions.
- --
Rodney Joffe
CenterGate Research Group, LLC.
http://www.centergate.com
"Technology so advanced, even we don't understand it!"(SM)
Rodney,
Thanks for the announcement. I now have something to forward when people wonder why a domain update can take 24hrs. For those of us not on 50 lists a one time post to nanog like this is a big help.
Dave
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm speaking officially only for myself here, although my opinion is
informed by the fire drill at work today. 
During the root zone (.) update later today, specifically with root
zone serial number 2003090501, the entries for .org will me modified.
Rodney,
Thanks for giving us this update, any notice is better than none.
However, I have two requests that I'd like you (and anyone with similar
responsibilities elsewhere) to take into account for next time.
1. A little _more_ advanced notice would be appreciated. At least 24
hours, preferably more.
2. Making the actual change on a day other than Friday would be
fabulous, so I don't have to change critical systems right before the
weekend.
Fortunately, this particular change didn't cause a lot of hair pulling,
but in general it would be nice if folks would take these two points
into consideration. I'm sure I'm not the only one who'd appreciate it.
Happy weekend,
Doug
- --
"You're walkin' the wire, pain and desire. Looking for love in between."
- The Eagles, "Victim of Love"
-----BEGIN PGP SIGNED MESSAGE-----
Rodney Joffe wrote:
Hello Jeroen,
Jeroen Massar wrote:
>
> This talks about transport, but how about AAAA's for NS's and their
> glue? Do these ultra super duper servers allow that in .org?
> And when do you think that will happen?
Ignoring the possible sarcasm ;-)...
1) The UltraDNS nameserver does fully support IPv6.
Ack.
2) As far as TLD IPv6 records, this question would have to be
referred to the TLD registry operator. If they allow it, we support
it. I am not aware of any of the tlds that we are authoritative for
actually inserting any domain records with IPv6 data, but I could be
wrong.
Apparently Network solutions can be bribed per phone passing your
user&password over it to do it manually. There are some others too.
Would be nice to have a FAQ explaining how to get it though.
3) We're working on a native IPv6 feed to all of our nodes, and would
hope to have this live and active before the end of this year.
Anycast creates an additional challenge for us in deploying IPv6.
That would be a great thing to see happening. a TLD like .org will
quite possibly also be in the position to request IPv6 glue into
the rootzone. When this is enabled don't forget to cc the relevant
IPv6 lists and ofcourse present your findings to everyone.
Greets,
Jeroen