After the change, NTT IRR is correctly mirroring the new IP address (thanks for that), but rr.level3.net and radb.net seem to be stuck with the old IP, and since the old IP address is non-authoritative (flag N), replication to those IRRs has in effect stopped.
So, if those two IRR operators could act on it, it would be nice. Thanks, Rubens (on behalf of TC) On Sat, Apr 10, 2021 at 4:27 PM Rubens Kuhl <rube...@gmail.com> wrote: > > Hi there. > TC, a large IRR database focused on Brazilian networks, just changed its > IP addresses. In most IRRd implementations it's necessary to sighup the > daemon to move to the new IP addresses, so we kindly ask those running > public and private IRR instances to sighup in order to move to the new IP > addresses. > > The new addresses of bgp.net.br are: > bgp.net.br has address 177.128.210.126 > bgp.net.br has IPv6 address 2804:890:0:102::102 > bgp.net.br mail is handled by 10 bgp.net.br. > > The old machine will be up and serving mirroring requests until we see > most, if not all, of requests being served by the new machine. > > Thanks, > TC > >
