- dns-wg - mailman.ripe.net

DNS provisioning system maintenance, 8th Aug
by Sjoerd Oostdijck 02 Aug '07

02 Aug '07

Dear Colleagues, On Wednesday, 8 August 2007 we will update the provisioning system for our DNS servers. There will be no zone updates between 08:30 and 09:30 (UTC) on that day. We apologise for any inconvenience this may cause. If you have any questions or concerns about this, please send an e-mail to <dns-help(a)ripe.net>. Regards, Sjoerd Oostdijck, DNS Services RIPE NCC

1 0

RIPE-55 coming up
by Jaap Akkerhuis 24 Jul '07

24 Jul '07

Yes, I know it will be October but these things have a habbit of sneaking up on you before you know it. Therefore, now is the time not only for vacation but also to spend some thought about contributions to the dns-wg or suggestions for topics. jaap

1 0

IPv6 backresolve with DNSSEC
by Max Tulyev 09 Jul '07

09 Jul '07

Hi All, I tried to create a DNSSEC signed backresolve domain for my IPv6 block: domain: 0.d.0.0.1.0.a.2.ip6.arpa descr: NetAssist LLC org: ORG-NL64-RIPE admin-c: MT6561-RIPE tech-c: MT6561-RIPE zone-c: MT6561-RIPE nserver: ns.netassist.kiev.ua nserver: ns.netassist.ru ds-rdata: 46236 5 1 B42280F344BB12FCC5030673109EF84EF2C4D3A7 mnt-by: MEREZHA-MNT mnt-lower: MEREZHA-MNT changed: support(a)netassist.kiev.ua 20070704 source: RIPE and it fails with: ***Error: DS records are not accepted for this zone. ***Error: RDNS Authorisation failed but without ds-rdata everything works fine. Is it a (my) bug or a feature? -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)

2 3

RIPE NCC Network Maintenance Wednesday 20 June 17:00 to 19:00 UTC/GMT
by Mark Guz 18 Jun '07

18 Jun '07

[apologies for duplicates] Dear Colleagues, On Wednesday 20/06/2007, between 17:00 and 19:00 (UTC), the RIPE NCC will carry out planned maintenance work on our network infrastructure. This may result in brief interruptions to RIPE NCC services during the posted maintenance window. We apologise for any inconvenience that this may cause. This work is due to planned resilience testing of our network. If you have any questions about this, please send an e-mail to: ops(a)ripe.net <mailto:ops@ripe.net>. Regards Mark Guz Senior Engineer RIPE NCC

1 0

RIPE Community Requests that ICANN Signs DNS Root
by Axel Pawlik 14 Jun '07

14 Jun '07

[Apologies for duplicates.] Dear Colleagues, During the RIPE 54 Meeting in Tallinn, Estonia on 7 -11 October, the RIPE DNS Working Group agreed that a formal request should be made to the Internet Corporation for Assigned Names and Numbers (ICANN) for it to sign the DNS root as soon as possible. The working group formulated a statement and asked the RIPE community for endorsement during the closing plenary. The RIPE community unanimously supported this statement and, as a result, a formal letter of request was sent to ICANN. This letter, which includes the statement, can be viewed at: http://www.ripe.net/ripe/wg/dns/icann-root-signing.pdf Regards, Axel Pawlik Managing Director RIPE NCC

2 2

Secondary service on ns.ripe.net for reverse delegations.
by Brett Carr 05 Jun '07

05 Jun '07

As mentioned in my presentation at RIPE 54 last week we have become aware that there is an inconsistency between ipv4 and ipv6 with regard to obtaining reverse delegation. The reverse delegation procedure listed at http://www.ripe.net/rs/ reverse/reverse_howto.html has the following listed: -----snip Secondary Service by the RIPE NCC For IPv4: If your zone is a /16 reverse zone, you will need to set up ns.ripe.net as a secondary server For IPv6: If your zone is a /32 reverse zone, you may use ns.ripe.net as a secondary -----snip We think it would be a good idea to address this inconsistency, this could be done in several ways including but not limted to: Make ns.ripe.net mandatory on ipv4 and ipv6 delegations Make ns.ripe.net optional on ipv4 and ipv6 delegations Discontinue the secondary service on ns.ripe.net for new delegations. Our suggestion and preference would be to make ns.ripe.net optional on both ipv4 and ipv6 delegations. We would welcome and encourage input from the dns community on this subject. Regards Brett -- Brett Carr Manager -- DNS Services Group RIPE Network Coordination Centre Amsterdam

8 8

RIPE NCC Network Maintenance Thursday 07 June 1700-1900 UTC
by Mark Guz 04 Jun '07

04 Jun '07

[apologies for duplicates] Dear Colleagues, Between 17:00 and 19:00 (UTC/GMT) on Thursday, 07 June 2007, the RIPE NCC will carry out planned maintenance work on our network infrastructure. During this period, www.ripe.net and associated sites, ftp.ripe.net, whois.ripe.net and Authorative DNS services as provided by the RIPE NCC may be interupted. We apologise for any inconvenience that this may cause. If you have any questions about this, please e-mail ops(a)ripe.net Regards Mark Guz Senior Engineer Operations Department RIPE NCC

1 0

RIPE NCC Network Maintenance Wednesday 23 May 1700 - 1900 UTC/GMT - COMPLETED
by Mark Guz 24 May '07

24 May '07

Dear Colleagues, The above mentioned maintenance was performed successfully and within the specified maintenance window. If you have any questions about this, please e-mail ops(a)ripe.net Regards Mark Guz Senior Engineer Operations Dept RIPE NCC

1 0

RIPE NCC Network Maintenance Wednesday 23 May 1700 - 1900 UTC/GMT - COMPLETED
by Mark Guz 24 May '07

24 May '07

Dear Colleagues, The above mentioned maintenance was preformed successfully and within the specified maintenance window. If you have any questions about this, please e-mail ops(a)ripe.net Regards Mark Guz Senior Engineer Operations Dept RIPE NCC

1 0

RIPE NCC Network Maintenance Wednesday 23 May 1700 - 1900 UTC/GMT
by Mark Guz 21 May '07

21 May '07

Dear Colleagues, Between 17:00 and 19:00 (UTC) on Wednesday, 23 May 2007, the RIPE NCC will carry out planned maintenance work on our core network infrastructure. During this period all RIPE NCC services will suffer intermittent interruptions We apologise for any inconvenience that this may cause. If you have any questions about this, please e-mail ops(a)ripe.net Regards Mark Guz Senior Engineer Operations Dept RIPE NCC

1 0