Resultados 1 a 8 de 8
  1. #1
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    18,423

    [EN] Reverse DNS issue for delegations in the RIPE NCC service region

    16 Mar 2017 07:00

    Between 17:00 UTC yesterday and 10:00 UTC today, we had an issue that affected some reverse DNS delegations.

    The delegations in the RIPE Database where the parent zone is operated by ARIN were affected.

    RIPE NCC publishes zonelet files containing these delegations, and these are picked up by ARIN's DNS provisioning system periodically. At the end of these zonelet files is a summary of the counts of various types of DNS records. A bug in some code accidentally published these summaries with zero counts, and as a result, the ARIN DNS provisioning system appears to have removed the delegations.

    We have corrected this bug, and the zonelet files now contain the correct counts. They have been published on the RIPE NCC FTP server, and ARIN's DNS provisioning system has picked them up and reintroduced the delegations.

    We apologise for any inconvenience caused by this. This is the first time that such an issue has occurred with delegations that are exchanged by the zonelet mechanism, and we will try to engineer monitoring to prevent such an outage in the future.

    The parent zones that were affected by this issue are:

    13.in-addr.arpa.
    23.in-addr.arpa.
    24.in-addr.arpa.
    45.in-addr.arpa.
    52.in-addr.arpa.
    65.in-addr.arpa.
    66.in-addr.arpa.
    104.in-addr.arpa.
    107.in-addr.arpa.
    128.in-addr.arpa.
    129.in-addr.arpa.
    130.in-addr.arpa.
    131.in-addr.arpa.
    132.in-addr.arpa.
    134.in-addr.arpa.
    135.in-addr.arpa.
    136.in-addr.arpa.
    137.in-addr.arpa.
    138.in-addr.arpa.
    139.in-addr.arpa.
    140.in-addr.arpa.
    143.in-addr.arpa.
    144.in-addr.arpa.
    146.in-addr.arpa.
    147.in-addr.arpa.
    148.in-addr.arpa.
    149.in-addr.arpa.
    152.in-addr.arpa.
    156.in-addr.arpa.
    157.in-addr.arpa.
    158.in-addr.arpa.
    159.in-addr.arpa.
    160.in-addr.arpa.
    161.in-addr.arpa.
    164.in-addr.arpa.
    165.in-addr.arpa.
    166.in-addr.arpa.
    168.in-addr.arpa.
    169.in-addr.arpa.
    170.in-addr.arpa.
    173.in-addr.arpa.
    198.in-addr.arpa.
    199.in-addr.arpa.
    206.in-addr.arpa.
    209.in-addr.arpa.
    216.in-addr.arpa.

    https://www.ripe.net/support/service...service-region

  2. #2
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    18,423
    Mickael Marchand‏ @mmarcha 56 minutes ago <- Online.net

    @RIPE_NCC I believe we have the same kind of issue for 163.172.0.0/16 actually, mind looking ?



    Matthew Buckett‏ @buckett 37 minutes ago

    @RIPE_NCC 163.in-addr.arpa isn't in the list of affected zones, has this been missed?


    Mickael Marchand‏ @mmarcha 19 minutes ago

    looks like APNIC was affected too RIPE is checking the issue


    Anthony Brodard‏ @Nawadanp 3 minutes ago

    @RIPE_NCC We have the same issue on an APNIC zone (153.in-addr.arpa ). Can you confirm it will be solved ?
    Última edição por 5ms; 17-03-2017 às 10:52.

  3. #3
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    18,423
    RIPE NCC‏ @RIPE_NCC 2 hours ago

    There was an rDNS issue for certain delegations (parent zone #ARIN) between 17:00 UTC 16 March - 10:00 UTC 17 March


    RIPE NCC‏ @RIPE_NCC 28 minutes ago

    @Nawadanp Thanks - we are aware that APNIC zones are affected and are investigating.


    Obs: A data do boletim (post#1) correta é 17 Mar 2017 07:00.
    Última edição por 5ms; 17-03-2017 às 11:26.

  4. #4
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    18,423
    RIPE NCC‏ @RIPE_NCC 19 minutes ago

    Update: two #APNIC zones are also affected: 153.in-addr.arpa & 163.in-addr.arpa - we're working on it

  5. #5
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    18,423
    RIPE NCC‏ @RIPE_NCC 20 minutes ago

    Just to confirm: the issue affecting the two #APNIC zones (153.in-addr.arpa & 163.in-addr.arpa ) has now been resolved.

  6. #6
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    18,423
    É de se pensar o número de erros que essa trapalhada pode ter causado.

    Somente agora estou recebendo nos servidores europeus e-mails do Google que normalmente teriam sido enviados ontem à noite.

    Embora um evento único, a redundância utilizando provedores diferentes em paises europeus diferentes não segurou a onda para um conjunto de dominios

    Felizmente, os dominios mais importantes estão em um outro conjunto redundante de servidores master-master: Online.net (FR) e Dacentec (USA) e não foram afetados.

  7. #7
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    18,423
    Received: by mail-pg0-f74.google.com with SMTP id []
    for <xxxxxxxx>; Fri, 17 Mar 2017 12:03:56 -0700 (PDT)
    X-Received: by 10.99.107.2 with SMTP id []; Fri, 17 Mar 2017 12:03:55 -0700 (PDT)
    Date: Thu, 16 Mar 2017 16:59:59 -0700
    From: noreply-dmarc-support@google.com


    Received: by mail-ot0-f202.google.com with SMTP id []
    for <xxxxxxx>; Fri, 17 Mar 2017 12:04:01 -0700 (PDT)
    X-Received: by 10.157.2.69 with SMTP id []; Fri, 17 Mar 2017 12:04:00 -0700 (PDT)
    Date: Thu, 16 Mar 2017 16:59:59 -0700
    From: noreply-dmarc-support@google.com


    Received: by mail-yw0-f201.google.com with SMTP id []
    for <xxxxxx>; Fri, 17 Mar 2017 12:04:57 -0700 (PDT)
    X-Received: by 10.129.177.130 with SMTP id []; Fri, 17 Mar 2017 12:04:56 -0700 (PDT)
    Date: Thu, 16 Mar 2017 16:59:59 -0700
    From: noreply-dmarc-support@google.com


    Aparentemente o Google colocou as mensagens em "hold" por 19 horas aguardando a correção e confirmação do RIPE.

  8. #8
    WHT-BR Top Member
    Data de Ingresso
    Jul 2011
    Posts
    1,159
    Afetou também algumas delegações na região do LACNIC, inclusive de redes brasileiras.

Permissões de Postagem

  • Você não pode iniciar novos tópicos
  • Você não pode enviar respostas
  • Você não pode enviar anexos
  • Você não pode editar suas mensagens
  •