From jaap at NLnetLabs.nl Tue Mar 6 14:16:33 2012 From: jaap at NLnetLabs.nl (Jaap Akkerhuis) Date: Tue, 06 Mar 2012 14:16:33 +0100 Subject: [dns-wg] Wanted: DNS WG Agenda items Message-ID: <201203061316.q26DGXVX065109@bartok.nlnetlabs.nl> Dear all, The RIPE meeting will be upon us soon. The website http://ripe64.ripe.net/ is up with the tentative programme, time to get you agenda proposals in for the DNS-WG meeting. Send them to this list or to the chairs directly. Remember, it is your working group and you meeting. Regards, jaap From anandb at ripe.net Mon Mar 12 17:31:28 2012 From: anandb at ripe.net (Anand Buddhdev) Date: Mon, 12 Mar 2012 17:31:28 +0100 Subject: [dns-wg] Migration of ns.ripe.net to new IP addresses Message-ID: <4F5E24E0.2020807@ripe.net> Dear colleagues, The RIPE NCC allows users to use ns.ripe.net as a secondary DNS server for reverse zones of /16 IPv4 and /32 IPv6 address space. This name server has had the addresses 193.0.0.193 and 2001:610:240:0:53::193 for several years. We are now migrating all the secondary zones on this server to a new, modern cluster of servers. For this, we have to assign new addresses to ns.ripe.net. These new addresses will be: 193.0.9.6 2001:67c:e0::6 We will change the addresses tomorrow, 13 March. The TTL of the address records is currently six hours, so we expect that most DNS clients will be talking to the new server by the next morning. This change has one important consequence as far as NOTIFY messages are concerned. Our new DNS cluster is in an anycast prefix, so we do not transfer zones directly to any server in the cluster. We transfer zones to our provisioning server, and then transfer them to the cluster. If you wish to use DNS NOTIFY, please add the following IP addresses of our provisioning server to your notify list and allow zone transfers to these addresses: 193.0.0.198 2001:67c:2e8:5:53::6 If you do not send NOTIFY messages to our provisioning server, the zones will be refreshed based on the refresh timer in the SOA record of the zone. Finally, I would like to take this opportunity to remind users that the use of ns.ripe.net as a secondary server is not mandatory. You do not have to use it. If you have good DNS infrastructure and do not require ns.ripe.net as a secondary, you may remove it from your zone and from the domain object of that zone in the RIPE Database. If you have any other questions about this change of addresses, please send email to . Regards, Anand Buddhdev RIPE NCC From denis at ripe.net Thu Mar 22 16:37:19 2012 From: denis at ripe.net (Denis Walker) Date: Thu, 22 Mar 2012 16:37:19 +0100 Subject: [dns-wg] DOMAIN Object Syntax Review - Final Call Message-ID: <4F6B472F.3080507@ripe.net> Dear colleagues, Now that all forward DOMAIN objects have been removed, the RIPE NCC is working on the action point from RIPE 62 that asked us to consider the attributes in DOMAIN objects. This topic has since been raised several times on RIPE working group mailing lists. There has been very little community response, which may suggest that these attributes are not important to anyone. After discussion with the Working Group Chairs, it has been agreed to send out a final call for comments. If there is no negative response, the syntax change outlined below will be implemented. Please send any comments to the DNS-WG mailing list before Monday, 2 April 2012. The proposal is to deprecate these attributes from the DOMAIN object: mnt-lower sub-dom dom-net refer We propose the following timeline for deprecating these four attributes: - Final mailing list comments by 2 April 2012 If there are no objections posted to the mailing list: - Announcement of the change at RIPE 64 - Change syntax for RIPE Database updates shortly after RIPE 64 - Notify maintainers of objects that include these attributes when syntax is changed - Cleanup of data by changing any instances of these attributes into "remarks:" by RIPE 65 Regards, Denis Walker Business Analyst RIPE NCC Database Group