- dns-wg - mailman.ripe.net

Deprecation of DOMAIN object attributes
by Denis Walker 21 Aug '12

21 Aug '12

[Apologies for duplicate emails] Dear Colleagues, At RIPE 62, the RIPE NCC was asked to look at the attributes in DOMAIN objects. A suggestion was put forward to deprecate the following attributes: mnt-lower: sub-dom: dom-net: refer: These were considered to be of no use after the removal of forward domain data and no longer allowing hierarchical, reverse delegation data. The RIPE NCC is now removing these attributes from the syntax. It will no longer be possible to create objects with these attributes. To modify objects already containing them, these attributes will need to be removed. As a follow up the RIPE NCC will "clean" the reverse delegation and ENUM DOMAIN object data to remove these attributes. The web forms for both updates and queries will also have these attributes removed. Regards, Denis Walker Business Analyst RIPE NCC Database Group

1 0

Call for agenda items for the RIPE65 DNS WG meeting
by Peter Koch 20 Aug '12

20 Aug '12

Dear WG, the next RIPE meeting is eight weeks away and we have our usual two DNS WG slots on the Wednesday of the meeting week: <https://ripe65.ripe.net/programme/meeting-plan/> Your chairs would like to invite you to send in agenda item suggestions to either of us or to <dns-wg-chairs(a)ripe.net>. If you have anything to share or an idea that you'd like community feedback for, this is the time to speak up. Take this non-exhaustive list as a start: o operational practices o operational observations, traffic patterns o measurements o deployment experiences o tools (yes, that might be _your_ basket of scripts) o ... Since we have received positive feedback regarding the panel discussions (twice in a row makes it almost a tradition now), we would like to use this format once more, but again: we're dependent on your contributions. Please let us know of issues that you'd like to see addressed and/or volunteer for participation. Thanks in advance, Peter (for the three co-chairs)

1 1

New delegation checking software
by Anand Buddhdev 08 Aug '12

08 Aug '12

[Apologies for duplicates] Dear colleagues, Tomorrow, 8 August 2012, the RIPE NCC will deploy a change to the RIPE Database update software. As part of this deployment, we will switch to a new DNS delegation checker, developed by .SE, the Swedish domain name registry. This change should not have any impact on the process of registering a reverse DNS delegation in the RIPE Database. However, the informational and diagnostic messages this software returns will look different from the ones you have been seeing so far. There should be no noticeable outage in any of the services during this deployment. There will be no change to any other parts of the RIPE Database update or query software with this deployment. Along with these changes to the back-end software, the RIPE NCC will also update the web-based delegation checker at: http://www.ripe.net/data-tools/dns This new web-based delegation checker will use the same software as the back-end. We will send another announcement after we have deployed this new software. If you have any questions or comments, please send an email to <dns(a)ripe.net>. Regards, Anand Buddhdev RIPE NCC

1 1

rDNS Incident: The Facts
by Daniel Karrenberg 19 Jun '12

19 Jun '12

We have just published the time-line of events that led to the rDNS service issues last week: https://labs.ripe.net/Members/dfk/timeline-of-reverse-dns-events I realise that our operational performance was not up to the standard you expect from us and I apologise again for the considerable inconvenience we have caused some of you. Another report will follow once we have fully analysed what happened. Daniel

1 0

Graphs of DNSKEY queries at K-root
by Anand Buddhdev 19 Jun '12

19 Jun '12

Dear colleagues, During the DNS Working Group session at RIPE 64, Olaf Kolkman asked the RIPE NCC to provide graphs of DNSKEY queries arriving at K-root. These graphs, especially the yearly one, are a good indicator about the level of DNSSEC validation happening for the root zone. We have enabled automatic generation of these graphs. They are available at: http://k.root-servers.org/statistics/ROOT/dnskey_queries.html If you have any questions, please email <dns(a)ripe.net>. Regards, Anand Buddhdev RIPE NCC

4 4

Update on Reverse DNS Outage - Resolved
by Serge Radovcic 15 Jun '12

15 Jun '12

Dear colleagues, As of Friday, 15 June 2012 at 07:30 UTC, reverse DNS operations are fully back to normal. The service update has been posted at: http://www.ripe.net/lir-services/service-announcements/reverse-dns-services… However, if you are still experiencing abnormal reverse DNS responses, please email us at <dns-help(a)ripe.net>. ======================== Summary Report and Incident Analysis ======================== We are analysing the incident and preparing a summary report on the facts, cause and effects of the outage. We will send this report out early next week. We will follow up with a detailed incident analysis. ============== Service Updates ============== All RIPE NCC-related service announcements will be posted on <ncc-announce(a)ripe.net> and published at: http://www.ripe.net/lir-services/service-announcements We will also alert our Twitter and Facebook followers that an update has been posted. Social media updates are posted and maintained during regular business hours. Please note that the RIPE NCC does not use the <members-discuss(a)ripe.net> mailing list to post service announcements or updates. =================== Reporting Procedures Review =================== We strive to provide you with accurate updates on outages. We understand that for incidents of this nature, timely and regular updates to our stakeholders is of the utmost importance. We are analysing feedback from the incident and using it to improve our communication procedures. Kind regards, Serge Radovcic Chief Communications Officer RIPE NCC

1 0

Update: Reverse DNS Outage (as of 20:00 UTC, 14 June)
by Romeo Zwart 15 Jun '12

15 Jun '12

Dear colleagues, As of 20:00 UTC, Thursday 14 June 2012, all regular zone information is again complete and up-to-date. However, we are still processing some imported ERX zones from the APNIC region. If you are still experiencing any abnormal responses, other than related to the above mentioned ERX zone, you can contact us atdns-help(a)ripe.net. Provide as much detail as possible. This update is available online at: http://www.ripe.net/lir-services/service-announcements/reverse-dns-services… Kind regards, Romeo Zwart GII Services Manager RIPE NCC

2 1

Update 4: Reverse DNS Services Outage
by Romeo Zwart 14 Jun '12

14 Jun '12

Dear colleagues, We'd like to update you on the reverse DNS outage situation: As of 13:00 UTC on Thursday, 14 June 2012 the zones listed in the previous update have been restored to the state of 13:30 UTC, Wednesday, 13 June 2012. So all zones we maintain are now available and zones in the list are no longer special. There may be a very few ERX zones maintained by other RIRs that are still not fully restored. The update has been posted online at: https://www.ripe.net/lir-services/service-announcements/reverse-dns-service… <http://www.ripe.net/lir-services/service-announcements> All updates since 13:30 UTC yesterday are still pending and are not reflected in the zones. However, no updates were lost. Any updates you will submit or you have already submitted will eventually be reflected in the zones once we complete our restoration procedure. ============= Next actions ============= We will now create up-to-date zones that include all the updates since yesterday 13:30 UTC. We will also recreate all ERX zones with current data. We expect to complete this by this evening. Once that is complete, we will re-enable regular provisioning and everything will be back to normal. If you experience any abnormal responses beyond the residual inconsistencies described here, please let us know atdns-help(a)ripe.net with as much detail as possible. Kind regards, Romeo Zwart GII Services Manager RIPE NCC

1 0

Update 14 June (11:22 UTC): Reverse DNS Services Outage
by Romeo Zwart 14 Jun '12

14 Jun '12

Dear colleagues, We'd like to update you on the reverse DNS service outage situation. As of 10:45 UTC on Thursday, 14 June 2012, all reverse DNS zones we publish and that are not on the list below are correct and reflect the state of 13:30 UTC yesterday, 13 June. If you continue to see problems after this time, please contactdns-help(a)ripe.net with details of what responses you are getting. Please consider (negative) caching TTLs and restart your caching servers if possible. We've posted this update online at: https://www.ripe.net/internet-coordination/news/announcements/update-14-jun… =============== Outage Details =============== We know that some zones not mentioned in the list of the previous update (20:45 UTC, 13 June) were not correctly propagated to some authoritative servers after the roll-back last night. We do not know the extent of this at the present time. However we are sure that as of 10:45 UTC today all authoritative servers answer correctly with the state of 13:30 UTC 13 June for all zones but the few on the list in the previous update. We are working hard to restore the zones listed. We are busy adding all the updates since 13:30 UTC 13 June to all zones. We will report on how this work is progressing. The zones known to be still affected are: 0.4.1.0.0.2.ip6.arpa 185.in-addr.arpa 4.1.1.0.0.2.ip6.arpa 5.1.0.0.2.ip6.arpa 6.1.1.0.0.2.ip6.arpa 7.0.1.0.0.2.ip6.arpa 7.1.1.0.0.2.ip6.arpa 7.4.1.0.0.2.ip6.arpa 8.0.1.0.0.2.ip6.arpa a.0.1.0.0.2.ip6.arpa a.1.1.0.0.2.ip6.arpa a.4.1.0.0.2.ip6.arpa b.0.1.0.0.2.ip6.arpa b.1.1.0.0.2.ip6.arpa b.4.1.0.0.2.ip6.arpa We will publish a full report once we've restored all the zones and have had sufficient time to fully analyse what went wrong. We have been working hard over the past 18 hours to resolve this problem and we apologise for the considerable inconvenience. Kind regards, Romeo Zwart GII Services Manager RIPE NCC

2 1

Fwd: WG Action: Web Extensible Internet Registration Data Service (weirds)
by Kaveh Ranjbar 16 May '12

16 May '12

Hello all, Below you can find the announcement from the IESG on the formation of the IETF Web Extensible Internet Registration Data Service (WEIRDS) Working Group. The aim of the working group is to work on a unified whois request-and-response format based on the web technologies. If you find the subject interesting, please kindly participate in discussions using the pointers in the original announcement. The RIPE NCC will do its best to make sure requirements and current practices of our community are reflected in the discussions but your direct participation is really appreciated. Kind regards, Kaveh. --- Kaveh Ranjbar, RIPE NCC Database Group Manager Begin forwarded message: > From: IESG Secretary <iesg-secretary(a)ietf.org> > Subject: [weirds] WG Action: Web Extensible Internet Registration Data Service (weirds) > Date: May 15, 2012 6:58:40 PM GMT+02:00 > To: IETF Announcement List <ietf-announce(a)ietf.org> > Cc: weirds(a)ietf.org > > A new IETF working group has been formed in the Applications Area. For additional information, please contact the Area Directors or the WG Chairs. > > Web Extensible Internet Registration Data Service (weirds) > ---------------------------------------------------------- > Status: Proposed Working Group > Last updated: 2012-04-24 > > Chairs: > Olaf Kolkman <olaf(a)nlnetlabs.nl> > Murray Kucherawy <msk(a)cloudmark.com> > > Applications Area Directors: > Barry Leiba<barryleiba(a)computer.org> > Pete Resnick<presnick(a)qualcomm.com> > > Applications Area Advisor: > Pete Resnick<presnick(a)qualcomm.com> > > Mailing List: > Address: weirds(a)ietf.org > To Subscribe: https://www.ietf.org/mailman/listinfo/weirds > Archive: http://www.ietf.org/mail-archive/web/weirds/ > > Description of Working Group: > > Internet registries for both number resources and names have > historically maintained a lookup service to permit public access > to some portion of the registry database. Most registries offer > the service via WHOIS (RFC 3912), with additional services being > offered via world wide web pages, bulk downloads, and other > services, such as RPSL (RFC 2622). > > WHOIS has never been internationalized. In the absence of formal > specification, ad hoc solutions to signal internationalized > registration data have been adopted and deployed. Providing a > standards-based solution that scales well could minimize further > proliferation of ad hoc solutions. > > WHOIS also has no data model: replies are basically just free-form > text. This means that processing of WHOIS output amounts to > "screen scraping", with specialized handlers for every service. > While many of the domain name registries share a basic common output > format, the addition of data elements changes the output > and causes problems for parsers of the data. > > The WHOIS protocol does not offer any differential service; it > cannot differentiate among clients to offer different subsets of > information or to allow different access rates to it. > > Various attempts to solve the limitations of WHOIS have met with > mixed success. The most recent of these was IRIS (RFC 3891). > IRIS has not been a successful replacement for WHOIS. The primary > technical reason for this appears to be the complexity of IRIS, the fact > that it builds upon many available technologies that in the aggregate > form a complex system. There may also exist non-technical reasons, > but they lie in areas upon which the IETF does not pass judgement. > > In recent years, ARIN and RIPE NCC have fielded production RESTful > web services to serve WHOIS data, and each has met with success. > It is widely believed that this simpler re-use of Web technologies > familiar to modern web developers has enabled this success. The > purpose of this working group is to broaden the use of RESTful web > services by achieving simple and common URI patterns and responses > amenable to all number resource and domain name registries. > > This Working Group shall determine the general needs of such a > service, and standardize a single data framework. That framework > shall be used to encapsulate objects that could form part of an > answer. The framework shall be for data to be delivered via a > RESTful data service using HTTP (optionally using TLS), and may use > standard features of HTTP to support differential service levels > to different classes of user. The data shall have one mandatory > format, though the working group may consider other optional formats. > The overall effort will be broadly aligned with > a subset of the Cross Registry Internet Service Protocol (CRISP) > Requirements (RFC 3707), but with the explicit additional goals of > producing a simple, easy-to-implement protocol, supporting > internationalized registration data and, specifically for > name registries, capturing the needs of internationalized > domain names in the data model. > > As the number registries have more experience with these services > and have found common ground, with their dissimilarities resulting in > more complete working group input documents, the goals of the working > group are to produce standards-track specifications for both number > and name registries using the fashion and pattern of the number registry > input documents, draft-newton-et-al-weirds-rir-query and > draft-newton-et-al-weirds-rir-json-response, as an initial basis. > > Work to specify the query for domain name registration data will be > based on draft-sheng-weirds-icann-rws-dnrd. > > The Working Group shall determine the general requirements of such a > service, using draft-kucherawy-weirds-requirements as an input document, > and standardize a single data framework. The working group will likely > not seek publication of this draft. > > Should the Working Group reach a point where it determines that the > problem of producing a grand unified specification for both numbers and > names appears to be intractable, it will be permitted to divide the > problem into separate tasks and amend its milestones accordingly. > > Milestones: > > Nov 2012 Draft specifying the common infrastructure document to the > IESG for approval as a Proposed Standard. > > Feb 2013 Draft specifying the RESTful URL query format for RIRs to the > IESG for approval as a Proposed Standard. > > Mar 2013 Draft specifying the format for responses to RIR queries > to the IESG for approval as a Proposed Standard. > > Jul 2013 Draft specifying the RESTful URL query format for domain name > registration data to the IESG for approval as a Proposed > Standard. > > Aug 2013 Draft(s) specifying the format(s) for responses to domain name > registration data queries to the IESG for approval as a > Proposed Standard. > _______________________________________________ > weirds mailing list > weirds(a)ietf.org > https://www.ietf.org/mailman/listinfo/weirds

1 0