About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

Experiments on production DNS (was: Re: NS.EU.NET running NSD)

  • To:
  • From: Berislav Todorovic < >
  • Date: Thu, 16 Jan 2003 11:18:11 +0100 (MET)
  • Cc:
    < >
    < >

As far as I remember, on 1 October 2002 people using ns.EU.net as secondary
for their zones received the following announcement from RIPE NCC (just
stating the significant part):

>> We, the RIPE NCC, host the nameserver ns.eu.net since the beginning of
>> June 2002 as a service to the Internet community, to give the
>> administrators of the large number of domains that ns.eu.net is still
>> running secondary nameservice for, ample time to stop referencing to it.
>>
>> We cannot provide this service indefinitely and are planning to stop
>> running ns.eu.net in 1 month time, in the beginning of November 2002.

Despite of the warning, ns.EU.net continued to operate normally after
November 2002. Well, many people probably appreciate this. However, since
few days ago a lot of ccTLD administrators started to complain about
reachability of ns.EU.net. Today we got the explanation about it:

>> Since January 13, the RIPE NCC is running the NS.EU.NET nameserver
>> with a new software, NSD ( http://www.nlnetlabs.nl/nsd ).

Well, experimenting is just fine, but don't you think people should have
been warned in advance? I don't need ns.EU.net anymore, since I moved
all domains we need to another server. However, some ccTLD's are
still using it and blaming our company for the problems, since EU.net
domain is still owned and operated by us.

Your argument might be that "they had enough time to migrate". True.
You are free to remove them completely from ns.EU.net, but as long
as ns.EU.net is a live box and serves as a DNS - it is a part of
production environment.

Would you, please, take a look into 4 ccTLD's that return NXDOMAIN and
take care they continue to have normal service:

al ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4
bg ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4
tp ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4
zw ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4

Their primaries are:

al	146.48.65.46
bg	192.92.129.1
tp	194.106.128.50
zw	194.133.122.47

Regards,
Beri

---------   Berislav Todorovic, Senior IP Specialist  --------
-----   KPN Eurorings B.V. - IP Engineering/NOC/Support  -----
----          Telecomplein 5, 2516 CK Den Haag, NL        ----
-----      Email: beri@localhost <=>  beri@localhost     ----







  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>
 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | Copyright Statement
RIPE.NET Homepage LIR Portal RIPE Community