On 06/11/2019 17:16, Pedro Alves wrote: > HTTP: http://mirror.nbtelecom.com.br/centos/ > HTTPS: https://mirror.nbtelecom.com.br/centos/ > RSYNC: rsync://mirror.nbtelecom.com.br/centos/ > Sync schedule: Every 1 hrs > Bandwidth: 100G > Location: Brazil / Rio de Janeiro > Sponsor: NB Telecom > Sponsor URL: http://www.nbtelecom.com.br > IPv4 address to authorize: 189.45.5.90 > IPv6 address to authorize: 2804:74::189:45:5:90,2804:74::189:45:5:76 > Email contact: noc at nbtelecom.com.br > Mirroring AltArch: no Thanks ! Your mirror http://mirror.nbtelecom.com.br/centos/ has been enabled back (you were there already) in the mirrors DB It will be listed as a public mirror (and on https://mirror-status.centos.org / https://www.centos.org/download/mirrors/ ) in the following minutes/hours. Your IP address[es] (189.45.5.90 2804:74::189:45:5:90,2804:74::189:45:5:76) has/have been added in the ACL and so you should be able to rsync from msync.centos.org in the next ~10min PS : while you asked for ipv6, you don't publish AAAA record for that node, so it wouldn't be validated over ipv6, and so would not enter the ipv6 mirrorlists. Can you advertise AAAA for that node ? -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos-mirror/attachments/20191118/e1d76a1e/attachment-0006.sig>