[dns-wg] RIPE NCC DNSSEC trust anchors
Jim Reid jim at rfc1035.com
Tue Nov 18 16:27:50 CET 2014
On 18 Nov 2014, at 14:50, Jorma Mellin <jorma at jmellin.net> wrote: > I remember the day when ripe.net -domain was unreachable because of > failure to renew it. The hassle was pretty big, as it took a long time to convince the domain registry (at U.S) to understand that "yes, we really need this at european territory”. This must have happened a *long* time ago and I am sure the NCC now has robust procedures in place to ensure domain names get renewed in good time. Though it might be worth asking about that. > This was the primary reason to register .int as well. The origins of ripe.int are unclear and it would be good to know why it was done. > I have no clue have the situation changed about this but if not why to get rid > of the backup? It's not a backup: gromit% dig ripe.int mx ... ;; ANSWER SECTION: ripe.int. 21600 IN MX 250 kaka.ripe.net. ripe.int. 21600 IN MX 200 koko.ripe.net. gromit% dig www.ripe.int ... ;; ANSWER SECTION: www.ripe.int. 21600 IN CNAME www.ripe.net. FWIW I have never seen a URL or email address containing has ripe.int.
[ dns-wg Archives ]