From comms at afrinic.net  Mon Nov  2 10:49:30 2020
From: comms at afrinic.net (AFRINIC Communication)
Date: Mon, 2 Nov 2020 14:49:30 +0400
Subject: [Community-Discuss] Peering DB Satisfaction Survey
Message-ID: <E1CD57D6-4996-4EA5-A973-71F25972C5FA@afrinic.net>

Dear colleagues,

PeeringDB wants input from network operators, exchange operators, facility providers, content distributors and anyone who uses the interconnection database. PeeringDB is running an anonymous satisfaction survey and would like your feedback.

Please read the blog about the survey at : https://afrinic.net/20201102-peeringdb-survey <https://afrinic.net/20201102-peeringdb-survey>


Ashil Oogarah
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/community-discuss/attachments/20201102/80373169/attachment.html>

From comms at afrinic.net  Tue Nov  3 11:16:35 2020
From: comms at afrinic.net (AFRINIC Communication)
Date: Tue, 3 Nov 2020 15:16:35 +0400
Subject: [Community-Discuss] =?utf-8?q?Rappel=3A_Participez_au_webinaire_d?=
 =?utf-8?q?=27AFRINIC_=3A__La_R=C3=A9siliation_d=27une_Adh=C3=A9sion_?=
 =?utf-8?q?=C3=A0_AFRINIC?=
Message-ID: <2E57D593-1A08-4EA7-862C-60B4B80E7060@afrinic.net>

Chers coll?gues,

AFRINIC a le plaisir de vous inviter ? un webinaire intitul? ??La R?siliation d'une adh?sion ? AFRINIC??

Date: Mercredi 04 Novembre 2020

Heure:

* 12:30 UTC (Senegal, Cote D'Ivoire)
* 13:30 WAT (Cameroun, Tunisie)
* 14:30 CAT (Burundi)
* 16:30 GST (Maurice, Seychelles)

Langue: Fran?ais

Audience:

Les membres de la communaut? AFRINIC et toute autre personne int?ress?e par la gestion des ressources num?riques Internet dans la r?gion de service d'AFRINIC.

Objectifs

? la fin de cette session, les participants pourront:

- Ma?triser les conditions pour mettre fin ? un abonnement chez AFRINIC
- Dire qui peut mettre fin ? un abonnement donn?
- Comprendre les implications de la r?siliation d'un abonnement

Pr?sentateurs:

Kishna Dhondee - Juriste, AFRINIC
Arthur Nguessan - HoD - Engagement des parties prenantes, AFRINIC
Brice Abba - Responsable du d?veloppement communautaire, AFRINIC

Veuillez vous inscrire ? la date et l?heure qui vous conviennent le mieux : http://bit.ly/AFRINICWebinarRegistration-FR <http://bit.ly/AFRINICWebinarRegistration-FR>

Rendez-vous au webinaire!

Ashil  Oogarah

Pour le d?partement Stakeholders Engagement de l'AFRINIC 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/community-discuss/attachments/20201103/d11d12ff/attachment.html>

From comms at afrinic.net  Thu Nov  5 07:29:08 2020
From: comms at afrinic.net (AFRINIC Communication)
Date: Thu, 5 Nov 2020 11:29:08 +0400
Subject: [Community-Discuss] Launch of AFRINIC's New E-course on Mastering
 Neighbour Discovery Protocol
Message-ID: <202165F5-BF21-4385-9D58-0B4710FA4715@afrinic.net>

Dear colleagues,

AFRINIC is delighted to announce the launch of the ?Mastering NDP? e-course.

Through this course, learners will be able to engage in learning how five of ICPMv6 messages make up the Neighbour Discovery Protocol for IPv6 operations.

By the end of the course, learners should be able to:

 ? Identify and explain the content of the five ICMPv6 messages used by NDP
 ? Outline and explain NDP operations for IPv6
 ? Examine and deconstruct NDP packet captures
 ? Configure, verify and debug SLAAC as a provisioning mechanism for an IPv6
 network
 ? List potential NDP security treats and available countermeasures
 ? Deploy Secure NDP(SeNDP) and RA-Guard to protect NDP against malicious
 attacks

This course is free of charge and now open for registration at: http://bit.ly/Elearning-Neighbor-Discovery-Protocol <http://bit.ly/Elearning-Neighbor-Discovery-Protocol> 

For more e-course options, visit the AFRINIC E-learning platform here: http://bit.ly/afrinic-e-learning <http://bit.ly/afrinic-e-learning>

Ashil Oogarah

On behalf of AFRINIC?s Capacity Building Team


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/community-discuss/attachments/20201105/b6f48b98/attachment.html>

From rfg at tristatelogic.com  Thu Nov  5 14:42:44 2020
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Thu, 05 Nov 2020 06:42:44 -0800
Subject: [Community-Discuss] More data base problems/inconsistancies
Message-ID: <31317.1604587364@segfault.tristatelogic.com>

(My apologies to Noah <noah at neo.co.tz>.  I owe you a further follow-up
response.  I haven't forgotten. I have just been swamped.  I assure you
I will get to that.  But just now I have a different pressing issue.)

As I learned when I did some trivial scripting to check to see if in fact
all of the ORGANIZATIONs in the AFRINIC data base that were marked as
MEMBER-ONLY really and truly DID NOT have any number resources assigned,
it can actually be both helpful and enlightening when one does some
simple sanity checking on RIR WHOIS data bases.

I've just done some more of that in the case the AFRINIC WHOIS data base
and I am sorry to have to report that I am once again disappointed by
what I am finding.

It appears that no one in AFRINIC ever quite decided whether the various
.in-addr.arpa names mentiobned in the domain: records within the data base
should or should not include a final trailing period.  The result is that
in numerous cases, there are effectively *two* records within the data
base to represent the same single reverse DNS delegation.  Worse yet, 
it is often the case that the two records have conflicting information,
e.g. for which name servers the delegation is supposed to be to, for the
identities of maintainer(s) of the delegations, as well as for the admin-c,
tech-c, and zone-c contacts for the delegation.

I am including a full listing of all such cases below.  (The are exactly
40 of them.)  My hope is that some staff person can rectify all of these
issues promptly.  There cannot be more than one delegation of reverse
DNS for a given assigned block.  Someone needs to decide whether the
representation of .in-addr.arpa names within the data base should or
should not end with a period, and then that convention, whatever it may
be, should be strictly enforced by software, going forward, in order to
insure that these kinds of problems will never infect the data base again
in the future.  (This is just a matter of simple input consistancy checking.
It should not be hard for any competent software engineer to implement.)

Oh!  Yes! And it would also be nice if someone would decide whether the
various .arpa names mentioned in domain: records should be upper or lower
case.  (Examples of both are current present in the data base.)  Please
pick one convention or the other and then stick to it consistantly.  That
will make parsing and automated anaylsis of such records easier.

The allocations currently afflicted by duplicate reverse DNS delegation
records are as follows:

196.2.160
196.2.161
196.2.162
196.2.163
196.2.164
196.2.165
196.2.166
196.2.167
196.2.168
196.2.169
196.2.170
196.2.171
196.2.172
196.2.173
196.2.174
196.2.175
196.2.176
196.2.177
196.2.178
196.2.179
196.2.180
196.2.181
196.2.182
196.2.183
196.2.184
196.2.185
196.2.186
196.2.187
196.2.188
196.2.189
196.2.190
196.2.191
163.196
212.0.148
212.0.159
212.0.129
196.202.144
196.202.145
212.0.138
212.0.146

The duplicate records:

domain:         146.0.212.in-addr.arpa.
descr:          sudatel 212.0.146
admin-c:        hmo2-afrinic
tech-c:         hmo2-afrinic
zone-c:         hmo2-afrinic
nserver:        sun1.sudanet.net
notify:         ***@sudatel.net
mnt-by:         sudatel-mnt
changed:        ***@sudatel.net 20050831
source:         AFRINIC

domain:         146.0.212.in-addr.arpa
descr:          Reverse Delegation
nserver:        ns1.sudatel.sd
nserver:        ns2.sudatel.sd
org:            ORG-SA54-AFRINIC
admin-c:        SAC1-AFRINIC
tech-c:         STC1-AFRINIC
zone-c:         SUD1-AFRINIC
mnt-by:         SUDATEL-MNT
mnt-lower:      SUDATEL-MNT
changed:        ***@sudatel.sd 20140123
source:         AFRINIC

domain:         196.163.in-addr.arpa.
descr:          Reverse DNS for Nissan South Africa
admin-c:        ZRV-AFRINIC
tech-c:         ZRV-AFRINIC
zone-c:         ZRV-AFRINIC
nserver:        ns1.qdata.net
nserver:        ns2.qdata.net
notify:         ***@nissan.co.za
mnt-by:         AFRINIC-HM-MNT
mnt-lower:      TF-163-196-MNT
changed:        ***@afrinic.net 20050913
source:         AFRINIC

domain:         196.163.in-addr.arpa
descr:          Reverse DNS for Nissan South Africa
admin-c:        GH2-AFRINIC
tech-c:         GH2-AFRINIC
zone-c:         GH2-AFRINIC
nserver:        ns1.infovan.co.za
nserver:        ns.infovan.co.za
nserver:        ns2.infovan.co.za
nserver:        ns3.infovan.co.za
notify:         ***@nissan.co.za
mnt-by:         AFRINIC-HM-MNT
mnt-lower:      TF-163-196-MNT
changed:        ***@afrinic.net 20050913
changed:        ***@afrinic.net 20070419
changed:        ***@afrinic.net 20081010
changed:        ***@afrinic.net 20090820
source:         AFRINIC

domain:         164.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         164.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         180.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         180.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         129.0.212.in-addr.arpa.
descr:          reverse zone for 212.0.129
admin-c:        HFS16-AFRINIC
tech-c:         HFS16-AFRINIC
zone-c:         HFS16-AFRINIC
nserver:        MAIN.SDN-MOBITEL.COM
nserver:        MAIN.SDN-MOBINET.NET
notify:         ***@sudatel.net
mnt-by:         sudatel-mnt
changed:        ***@sudatel.net 20050831
source:         AFRINIC

domain:         129.0.212.in-addr.arpa
descr:          Sudatel 212.0.129.0
org:            ORG-SA54-AFRINIC
admin-c:        HFS16-AFRINIC
tech-c:         HFS16-AFRINIC
zone-c:         HFS16-AFRINIC
nserver:        ns1.sudatel.sd
nserver:        ns2.sudatel.sd
notify:         ***@sudatel.sd
mnt-by:         SUDATEL-MNT
mnt-lower:      SUDATEL-MNT
changed:        ***@sudatel.sd 20100209
changed:        ***@afrinic.net 20130711
changed:        ***@sudatel.sd 20181016
source:         AFRINIC

domain:         163.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         163.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         187.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         187.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         138.0.212.in-addr.arpa.
descr:          reverse zone for 212.0.138
admin-c:        hmo2-afrinic
tech-c:         hmo2-afrinic
zone-c:         hmo2-afrinic
nserver:        sun1.sudanet.net
notify:         ***@sudatel.net
mnt-by:         sudatel-mnt
changed:        ***@sudatel.net 20050831
source:         AFRINIC

domain:         138.0.212.in-addr.arpa
descr:          reverse zone for 212.0.138
org:            ORG-SA54-AFRINIC
admin-c:        SAC1-afrinic
tech-c:         STC1-afrinic
zone-c:         SUD1-afrinic
nserver:        ns1.sudatel.sd
nserver:        ns2.sudatel.sd
notify:         ***@sudatel.sd
mnt-by:         SUDATEL-MNT
mnt-lower:      SUDATEL-MNT
changed:        ***@sudatel.net 20050831
changed:        ***@sudatel.sd 20181016
source:         AFRINIC

domain:         178.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         178.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         190.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         190.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         175.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         175.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         191.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         191.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         174.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         174.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         173.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         173.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         186.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         186.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         189.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         189.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         145.202.196.in-addr.arpa.
descr:          reverse zone for 196.202.145
admin-c:        YAA8-AFRINIC
tech-c:         HFS22-AFRINIC
zone-c:         HFS22-AFRINIC
nserver:        ns1.sudacom.net
nserver:        ns2.sudacom.net
notify:         ***@sudatel.net
mnt-by:         sudatel-mnt
changed:        ***@sudatel.net 20050831
source:         AFRINIC

domain:         145.202.196.in-addr.arpa
descr:          reverse zone for 196.202.145
org:            ORG-SA54-AFRINIC
admin-c:        sac1-afrinic
tech-c:         stc1-afrinic
zone-c:         sud1-afrinic
nserver:        ns1.sudatel.sd
nserver:        ns2.sudatel.sd
notify:         ***@sudatel.sd
mnt-by:         SUDATEL-MNT
mnt-by:         MNT-HIBA
mnt-lower:      SUDATEL-MNT
mnt-lower:      MNT-HIBA
changed:        ***@sudatel.net 20100330
changed:        ***@afrinic.net 20130711
source:         AFRINIC

domain:         168.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         168.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         182.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         182.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         165.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         165.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         181.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         181.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         171.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         171.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         172.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         172.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         167.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         167.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         179.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         179.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         148.0.212.in-addr.arpa.
descr:          reverse zone for 212.0.148
admin-c:        HMO2-AFRINIC
tech-c:         HMO2-AFRINIC
zone-c:         HMO2-AFRINIC
nserver:        ns1.sudanmail.net
nserver:        ns2.sudanmail.net
notify:         ***@sudatel.net
mnt-by:         sudatel-mnt
changed:        ***@sudatel.net 20050830
source:         AFRINIC

domain:         148.0.212.in-addr.arpa
descr:          reverse zone for 212.0.148
org:            ORG-SA54-AFRINIC
admin-c:        SAC1-afrinic
tech-c:         STC1-afrinic
zone-c:         SUD1-afrinic
nserver:        ns1.sudatel.sd
nserver:        ns2.sudatel.sd
notify:         ***@sudatel.sd
mnt-by:         SUDATEL-MNT
mnt-lower:      SUDATEL-MNT
changed:        ***@sudatel.net 20050830
changed:        ***@sudatel.sd 20181016
source:         AFRINIC

domain:         176.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         176.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         183.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         183.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         144.202.196.in-addr.arpa.
descr:          reverse zone for 196.202.144
admin-c:        YAA8-AFRINIC
tech-c:         HFS22-AFRINIC
zone-c:         HFS22-AFRINIC
nserver:        ns1.sudacom.net
nserver:        ns2.sudacom.net
notify:         ***@sudatel.net
mnt-by:         sudatel-mnt
changed:        ***@sudatel.net 20050831
source:         AFRINIC

domain:         144.202.196.in-addr.arpa
descr:          reverse zone for 196.202.144
org:            ORG-SA54-AFRINIC
admin-c:        sac1-afrinic
tech-c:         stc1-afrinic
zone-c:         sud1-afrinic
nserver:        ns1.sudatel.sd
nserver:        ns2.sudatel.sd
notify:         ***@sudatel.sd
mnt-by:         SUDATEL-MNT
mnt-by:         MNT-HIBA
mnt-lower:      SUDATEL-MNT
mnt-lower:      MNT-HIBA
changed:        ***@sudatel.net 20100330
changed:        ***@afrinic.net 20130711
source:         AFRINIC

domain:         184.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         184.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         160.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         160.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         185.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         185.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         161.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         161.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         159.0.212.in-addr.arpa.
descr:          reverse zone for 212.0.159
admin-c:        HMO2-AFRINIC
tech-c:         HMO2-AFRINIC
zone-c:         HMO2-AFRINIC
nserver:        sun1.sudatel.net
notify:         ***@sudatel.net
mnt-by:         sudatel-mnt
changed:        ***@sudatel.net 20050829
source:         AFRINIC

domain:         159.0.212.in-addr.arpa
descr:          reverse zone for 212.0.159
nserver:        ns1.sudatel.sd
nserver:        ns2.sudatel.sd
org:            ORG-SA54-AFRINIC
admin-c:        SAC1-afrinic
tech-c:         STC1-afrinic
zone-c:         SUD1-afrinic
mnt-by:         SUDATEL-MNT
mnt-lower:      SUDATEL-MNT
notify:         ***@sudatel.sd
changed:        ***@sudatel.net 20050829
changed:        ***@sudatel.sd 20140211
source:         AFRINIC

domain:         188.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         188.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         162.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         162.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         169.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         169.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         177.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         177.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         166.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         166.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC

domain:         170.2.196.in-addr.arpa.
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050525
source:         AFRINIC

domain:         170.2.196.in-addr.arpa
descr:          Reverse delegation for ORG-ECA1-AFRINIC-20040424
org:            ORG-ECA1-AFRINIC
admin-c:        AG3148-AFRINIC
tech-c:         AG3148-AFRINIC
zone-c:         AG3148-AFRINIC
nserver:        ns01.eastcoast.co.za
nserver:        ns02.eastcoast.co.za
remarks:        none
notify:         ***@eastcoast.co.za
mnt-by:         ECA-AS10803
changed:        ***@afrinic.net 20050531
source:         AFRINIC




From rfg at tristatelogic.com  Thu Nov  5 15:00:24 2020
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Thu, 05 Nov 2020 07:00:24 -0800
Subject: [Community-Discuss] Yet more data base problems/inconsistancies
Message-ID: <31455.1604588424@segfault.tristatelogic.com>

In addition to the problem I have just posted about i.e. the problem of
dublicate (and inconsistant) records in the WHOIS describing various
reverse DNS delegations, I am also seeing something else that I did not
anticipate, i.e. reverse DNS delegation records that are present within
the WHOIS data base, but which, for no very obvious reason, are *not*
also represented within the set of zone files present within the
ftp://ftp.afrinic.net/pub/zones/ directory.

I here provide one example:

domain:         35.203.196.in-addr.arpa
descr:          reverse delagation for the
descr:          HEXABYTE-10 dial-UP elmanzah
org:            ORG-ATIA2-AFRINIC
admin-c:        PA1317-AFRINIC
tech-c:         LD822-AFRINIC
zone-c:         LD822-AFRINIC
nserver:        ns1.hexabyte.tn
nserver:        ns2.hexabyte.tn
remarks:        data has been transferred from RIPE Whois Database 20050221
notify:         ***@ati.tn
mnt-by:         ATI-MNT
mnt-lower:      ATI-MNT
changed:        ***@ati.tn 20040322
changed:        ***@afrinic.net 20050221
changed:        ***@ati.tn 20140520
changed:        ***@ati.tn 20181023
source:         AFRINIC

The above reverse DNS delegation record in in the WHOIS data base but it
appears to me that it has no corresponding counterpart within this file:

ftp://ftp.afrinic.net/pub/zones/196.in-addr.arpa-AFRINIC

So, either this is due to some misunderstanding I am having regarding
what shiould be persent in that zone file, or else that zone file is
incomplete.

I am looking forward to having someone in authority tell me which is
actually the case.

If in fact a record describing the delegation shown above should in fact
be represented within the zone file, and if it is improperly missing
from that file, then it would seem to have a LOT of company.   In fact,
the entire list below of some 1,952 specific delegations are all mentioned
within the WHOIS data base but as far as I can tell, none of them are
mentioned within the file in the ftp://ftp.afrinic.net/pub/zones/ directory.


196.203.0 ns4.ati.tn
196.203.0 ns6.ati.tn
217.52.0 ns.aucegypt.edu
217.52.0 ns3.aucegypt.edu
196.203.1 ns4.ati.tn
196.203.1 ns6.ati.tn
217.52.1 ns.aucegypt.edu
217.52.1 ns3.aucegypt.edu
62.139.104 ns1.nile-online.net
62.139.104 ns2.nile-online.net
62.139.105 ns1.nile-online.net
62.139.105 ns2.nile-online.net
62.139.109 ns1.nile-online.net
62.139.109 ns2.nile-online.net
62.139.130 ns1.nile-online.net
62.139.130 ns2.nile-online.net
196.203.2 ns4.ati.tn
196.203.2 ns6.ati.tn
217.52.2 ns.aucegypt.edu
217.52.2 ns3.aucegypt.edu
62.139.253 ns2.egynet.com.eg
62.139.253 ns22.egynet.com.eg
217.52.3 ns.aucegypt.edu
217.52.3 ns3.aucegypt.edu
196.203.32 ns4.ati.tn
196.203.32 ns6.ati.tn
196.203.33 ns4.ati.tn
196.203.33 ns6.ati.tn
196.203.34 ns4.ati.tn
196.203.34 ns6.ati.tn
196.203.35 ns1.hexabyte.tn
196.203.35 ns2.hexabyte.tn
196.203.36 ns4.ati.tn
196.203.36 ns6.ati.tn
217.52.4 ns.aucegypt.edu
217.52.4 ns3.aucegypt.edu
217.52.5 ns.aucegypt.edu
217.52.5 ns3.aucegypt.edu
217.52.6 ns.aucegypt.edu
217.52.6 ns3.aucegypt.edu
217.52.7 ns.aucegypt.edu
217.52.7 ns3.aucegypt.edu
217.52.8 ns.aucegypt.edu
217.52.8 ns3.aucegypt.edu
196.205.11 ns1.link.net
196.205.11 ns2.link.net
212.0.159 sun1.sudatel.net
212.0.148 ns1.sudanmail.net
212.0.148 ns2.sudanmail.net
212.0.129 main.sdn-mobitel.com
212.0.129 main.sdn-mobinet.net
196.202.144 ns1.sudacom.net
196.202.144 ns2.sudacom.net
196.202.145 ns1.sudacom.net
196.202.145 ns2.sudacom.net
212.0.138 sun1.sudanet.net
212.0.146 sun1.sudanet.net
163.196 ns1.qdata.net
163.196 ns2.qdata.net
196.25.226 igubu.saix.net
196.25.226 sangoma.saix.net
196.205.177 ns1.link.net
196.205.177 ns2.link.net
196.205.0 ns1.link.net
196.205.0 ns2.link.net
196.205.1 ns1.link.net
196.205.1 ns2.link.net
196.205.2 ns1.link.net
196.205.2 ns2.link.net
196.205.3 ns1.link.net
196.205.3 ns2.link.net
196.205.4 ns1.link.net
196.205.4 ns2.link.net
196.205.5 ns1.link.net
196.205.5 ns2.link.net
196.205.6 ns1.link.net
196.205.6 ns2.link.net
196.205.7 ns1.link.net
196.205.7 ns2.link.net
196.205.8 ns1.link.net
196.205.8 ns2.link.net
196.205.9 ns1.link.net
196.205.9 ns2.link.net
196.205.10 ns1.link.net
196.205.10 ns2.link.net
196.205.12 ns1.link.net
196.205.12 ns2.link.net
196.205.13 ns1.link.net
196.205.13 ns2.link.net
196.205.14 ns1.link.net
196.205.14 ns2.link.net
196.205.15 ns1.link.net
196.205.15 ns2.link.net
196.205.16 ns1.link.net
196.205.16 ns2.link.net
196.205.17 ns1.link.net
196.205.17 ns2.link.net
196.205.18 ns1.link.net
196.205.18 ns2.link.net
196.205.19 ns1.link.net
196.205.19 ns2.link.net
196.205.20 ns1.link.net
196.205.20 ns2.link.net
196.205.21 ns1.link.net
196.205.21 ns2.link.net
196.205.22 ns1.link.net
196.205.22 ns2.link.net
196.205.23 ns1.link.net
196.205.23 ns2.link.net
196.205.24 ns1.link.net
196.205.24 ns2.link.net
196.205.25 ns1.link.net
196.205.25 ns2.link.net
196.205.26 ns1.link.net
196.205.26 ns2.link.net
196.205.27 ns1.link.net
196.205.27 ns2.link.net
196.205.28 ns1.link.net
196.205.28 ns2.link.net
196.205.29 ns1.link.net
196.205.29 ns2.link.net
196.205.30 ns1.link.net
196.205.30 ns2.link.net
196.205.31 ns1.link.net
196.205.31 ns2.link.net
196.205.32 ns1.link.net
196.205.32 ns2.link.net
196.205.33 ns1.link.net
196.205.33 ns2.link.net
196.205.34 ns1.link.net
196.205.34 ns2.link.net
196.205.36 ns1.link.net
196.205.36 ns2.link.net
196.205.37 ns1.link.net
196.205.37 ns2.link.net
196.205.38 ns1.link.net
196.205.38 ns2.link.net
196.205.39 ns1.link.net
196.205.39 ns2.link.net
196.205.40 ns1.link.net
196.205.40 ns2.link.net
196.205.35 ns1.link.net
196.205.35 ns2.link.net
196.205.55 ns1.link.net
196.205.55 ns2.link.net
196.205.43 ns1.link.net
196.205.43 ns2.link.net
196.205.60 ns1.link.net
196.205.60 ns2.link.net
196.205.49 ns1.link.net
196.205.49 ns2.link.net
196.205.44 ns1.link.net
196.205.44 ns2.link.net
196.205.46 ns1.link.net
196.205.46 ns2.link.net
196.205.52 ns1.link.net
196.205.52 ns2.link.net
196.205.53 ns1.link.net
196.205.53 ns2.link.net
196.205.50 ns1.link.net
196.205.50 ns2.link.net
196.205.51 ns1.link.net
196.205.51 ns2.link.net
196.205.59 ns1.link.net
196.205.59 ns2.link.net
196.205.47 ns1.link.net
196.205.47 ns2.link.net
196.205.48 ns1.link.net
196.205.48 ns2.link.net
196.205.56 ns1.link.net
196.205.56 ns2.link.net
196.205.45 ns1.link.net
196.205.45 ns2.link.net
196.205.42 ns1.link.net
196.205.42 ns2.link.net
196.205.58 ns1.link.net
196.205.58 ns2.link.net
196.205.54 ns1.link.net
196.205.54 ns2.link.net
196.205.41 ns1.link.net
196.205.41 ns2.link.net
196.205.57 ns1.link.net
196.205.57 ns2.link.net
196.205.61 ns1.link.net
196.205.61 ns2.link.net
196.205.62 ns1.link.net
196.205.62 ns2.link.net
196.205.63 ns1.link.net
196.205.63 ns2.link.net
196.205.64 ns1.link.net
196.205.64 ns2.link.net
196.205.65 ns1.link.net
196.205.65 ns2.link.net
196.205.66 ns1.link.net
196.205.66 ns2.link.net
196.205.67 ns1.link.net
196.205.67 ns2.link.net
196.205.68 ns1.link.net
196.205.68 ns2.link.net
196.205.69 ns1.link.net
196.205.69 ns2.link.net
196.205.70 ns1.link.net
196.205.70 ns2.link.net
196.205.71 ns1.link.net
196.205.71 ns2.link.net
196.205.72 ns1.link.net
196.205.72 ns2.link.net
196.205.74 ns1.link.net
196.205.74 ns2.link.net
196.205.77 ns1.link.net
196.205.77 ns2.link.net
196.205.78 ns1.link.net
196.205.78 ns2.link.net
196.205.79 ns1.link.net
196.205.79 ns2.link.net
196.205.73 ns1.link.net
196.205.73 ns2.link.net
196.205.75 ns1.link.net
196.205.75 ns2.link.net
196.205.82 ns1.link.net
196.205.82 ns2.link.net
196.205.76 ns1.link.net
196.205.76 ns2.link.net
196.205.80 ns1.link.net
196.205.80 ns2.link.net
196.205.81 ns1.link.net
196.205.81 ns2.link.net
196.205.83 ns1.link.net
196.205.83 ns2.link.net
196.205.84 ns1.link.net
196.205.84 ns2.link.net
196.205.85 ns1.link.net
196.205.85 ns2.link.net
196.205.86 ns1.link.net
196.205.86 ns2.link.net
196.205.87 ns1.link.net
196.205.87 ns2.link.net
196.205.88 ns1.link.net
196.205.88 ns2.link.net
196.205.89 ns1.link.net
196.205.89 ns2.link.net
196.205.90 ns1.link.net
196.205.90 ns2.link.net
196.205.91 ns1.link.net
196.205.91 ns2.link.net
196.205.92 ns1.link.net
196.205.92 ns2.link.net
196.205.93 ns1.link.net
196.205.93 ns2.link.net
196.205.94 ns1.link.net
196.205.94 ns2.link.net
196.205.95 ns1.link.net
196.205.95 ns2.link.net
196.205.96 ns1.link.net
196.205.96 ns2.link.net
196.205.97 ns1.link.net
196.205.97 ns2.link.net
196.205.98 ns1.link.net
196.205.98 ns2.link.net
196.205.99 ns1.link.net
196.205.99 ns2.link.net
196.205.100 ns1.link.net
196.205.100 ns2.link.net
196.205.101 ns1.link.net
196.205.101 ns2.link.net
196.205.102 ns1.link.net
196.205.102 ns2.link.net
196.205.103 ns1.link.net
196.205.103 ns2.link.net
196.205.104 ns1.link.net
196.205.104 ns2.link.net
196.205.105 ns1.link.net
196.205.105 ns2.link.net
196.205.106 ns1.link.net
196.205.106 ns2.link.net
196.205.107 ns1.link.net
196.205.107 ns2.link.net
196.205.108 ns1.link.net
196.205.108 ns2.link.net
196.205.109 ns1.link.net
196.205.109 ns2.link.net
196.205.110 ns1.link.net
196.205.110 ns2.link.net
196.205.111 ns1.link.net
196.205.111 ns2.link.net
196.205.112 ns1.link.net
196.205.112 ns2.link.net
196.205.113 ns1.link.net
196.205.113 ns2.link.net
196.205.115 ns1.link.net
196.205.115 ns2.link.net
196.205.116 ns1.link.net
196.205.116 ns2.link.net
196.205.114 ns1.link.net
196.205.114 ns2.link.net
196.205.117 ns1.link.net
196.205.117 ns2.link.net
196.205.118 ns1.link.net
196.205.118 ns2.link.net
196.205.119 ns1.link.net
196.205.119 ns2.link.net
196.205.120 ns1.link.net
196.205.120 ns2.link.net
196.205.121 ns1.link.net
196.205.121 ns2.link.net
196.205.122 ns1.link.net
196.205.122 ns2.link.net
196.205.123 ns1.link.net
196.205.123 ns2.link.net
196.205.124 ns1.link.net
196.205.124 ns2.link.net
196.205.125 ns1.link.net
196.205.125 ns2.link.net
196.205.126 ns1.link.net
196.205.126 ns2.link.net
196.205.127 ns1.link.net
196.205.127 ns2.link.net
196.205.128 ns1.link.net
196.205.128 ns2.link.net
196.205.129 ns1.link.net
196.205.129 ns2.link.net
196.205.130 ns1.link.net
196.205.130 ns2.link.net
196.205.131 ns1.link.net
196.205.131 ns2.link.net
196.205.132 ns1.link.net
196.205.132 ns2.link.net
196.205.133 ns1.link.net
196.205.133 ns2.link.net
196.205.134 ns1.link.net
196.205.134 ns2.link.net
196.205.135 ns1.link.net
196.205.135 ns2.link.net
196.205.136 ns1.link.net
196.205.136 ns2.link.net
196.205.137 ns1.link.net
196.205.137 ns2.link.net
196.205.138 ns1.link.net
196.205.138 ns2.link.net
196.205.139 ns1.link.net
196.205.139 ns2.link.net
196.205.140 ns1.link.net
196.205.140 ns2.link.net
196.205.141 ns1.link.net
196.205.141 ns2.link.net
196.205.142 ns1.link.net
196.205.142 ns2.link.net
196.205.143 ns1.link.net
196.205.143 ns2.link.net
196.205.144 ns1.link.net
196.205.144 ns2.link.net
196.205.145 ns1.link.net
196.205.145 ns2.link.net
196.205.146 ns1.link.net
196.205.146 ns2.link.net
196.205.147 ns1.link.net
196.205.147 ns2.link.net
196.205.148 ns1.link.net
196.205.148 ns2.link.net
196.205.149 ns1.link.net
196.205.149 ns2.link.net
196.205.150 ns1.link.net
196.205.150 ns2.link.net
196.205.151 ns1.link.net
196.205.151 ns2.link.net
196.205.152 ns1.link.net
196.205.152 ns2.link.net
196.205.153 ns1.link.net
196.205.153 ns2.link.net
196.205.154 ns1.link.net
196.205.154 ns2.link.net
196.205.155 ns1.link.net
196.205.155 ns2.link.net
196.205.156 ns1.link.net
196.205.156 ns2.link.net
196.205.157 ns1.link.net
196.205.157 ns2.link.net
196.205.158 ns1.link.net
196.205.158 ns2.link.net
196.205.159 ns1.link.net
196.205.159 ns2.link.net
196.205.160 ns1.link.net
196.205.160 ns2.link.net
196.205.161 ns1.link.net
196.205.161 ns2.link.net
196.205.162 ns1.link.net
196.205.162 ns2.link.net
196.205.163 ns1.link.net
196.205.163 ns2.link.net
196.205.164 ns1.link.net
196.205.164 ns2.link.net
196.205.165 ns1.link.net
196.205.165 ns2.link.net
196.205.166 ns1.link.net
196.205.166 ns2.link.net
196.205.167 ns1.link.net
196.205.167 ns2.link.net
196.205.168 ns1.link.net
196.205.168 ns2.link.net
196.205.169 ns1.link.net
196.205.169 ns2.link.net
196.205.170 ns1.link.net
196.205.170 ns2.link.net
196.205.172 ns1.link.net
196.205.172 ns2.link.net
196.205.171 ns1.link.net
196.205.171 ns2.link.net
196.205.173 ns1.link.net
196.205.173 ns2.link.net
196.205.174 ns1.link.net
196.205.174 ns2.link.net
196.205.175 ns1.link.net
196.205.175 ns2.link.net
196.205.176 ns1.link.net
196.205.176 ns2.link.net
196.205.178 ns1.link.net
196.205.178 ns2.link.net
196.205.179 ns1.link.net
196.205.179 ns2.link.net
196.205.180 ns1.link.net
196.205.180 ns2.link.net
196.205.181 ns1.link.net
196.205.181 ns2.link.net
196.205.182 ns1.link.net
196.205.182 ns2.link.net
196.205.183 ns1.link.net
196.205.183 ns2.link.net
196.205.184 ns1.link.net
196.205.184 ns2.link.net
196.205.185 ns1.link.net
196.205.185 ns2.link.net
196.205.186 ns1.link.net
196.205.186 ns2.link.net
196.205.187 ns1.link.net
196.205.187 ns2.link.net
196.205.188 ns1.link.net
196.205.188 ns2.link.net
196.205.189 ns1.link.net
196.205.189 ns2.link.net
196.205.190 ns1.link.net
196.205.190 ns2.link.net
196.205.191 ns1.link.net
196.205.191 ns2.link.net
196.205.192 ns1.link.net
196.205.192 ns2.link.net
196.205.193 ns1.link.net
196.205.193 ns2.link.net
196.205.194 ns1.link.net
196.205.194 ns2.link.net
196.205.195 ns1.link.net
196.205.195 ns2.link.net
196.205.196 ns1.link.net
196.205.196 ns2.link.net
196.205.197 ns1.link.net
196.205.197 ns2.link.net
196.205.198 ns1.link.net
196.205.198 ns2.link.net
196.205.199 ns1.link.net
196.205.199 ns2.link.net
196.205.200 ns1.link.net
196.205.200 ns2.link.net
196.205.201 ns1.link.net
196.205.201 ns2.link.net
196.205.202 ns1.link.net
196.205.202 ns2.link.net
196.205.204 ns1.link.net
196.205.204 ns2.link.net
196.205.203 ns1.link.net
196.205.203 ns2.link.net
196.205.205 ns1.link.net
196.205.205 ns2.link.net
196.205.206 ns1.link.net
196.205.206 ns2.link.net
196.205.207 ns1.link.net
196.205.207 ns2.link.net
196.205.208 ns1.link.net
196.205.208 ns2.link.net
196.205.209 ns1.link.net
196.205.209 ns2.link.net
196.205.210 ns1.link.net
196.205.210 ns2.link.net
196.205.211 ns1.link.net
196.205.211 ns2.link.net
196.205.212 ns1.link.net
196.205.212 ns2.link.net
196.205.213 ns1.link.net
196.205.213 ns2.link.net
196.205.214 ns1.link.net
196.205.214 ns2.link.net
196.205.215 ns1.link.net
196.205.215 ns2.link.net
196.205.216 ns1.link.net
196.205.216 ns2.link.net
196.205.217 ns1.link.net
196.205.217 ns2.link.net
196.205.219 ns1.link.net
196.205.219 ns2.link.net
196.205.220 ns1.link.net
196.205.220 ns2.link.net
196.205.221 ns1.link.net
196.205.221 ns2.link.net
196.205.224 ns1.link.net
196.205.224 ns2.link.net
196.205.225 ns1.link.net
196.205.225 ns2.link.net
196.205.218 ns1.link.net
196.205.218 ns2.link.net
196.205.222 ns1.link.net
196.205.222 ns2.link.net
196.205.223 ns1.link.net
196.205.223 ns2.link.net
196.205.227 ns1.link.net
196.205.227 ns2.link.net
196.205.226 ns1.link.net
196.205.226 ns2.link.net
196.205.228 ns1.link.net
196.205.228 ns2.link.net
196.205.229 ns1.link.net
196.205.229 ns2.link.net
196.205.230 ns1.link.net
196.205.230 ns2.link.net
196.205.231 ns1.link.net
196.205.231 ns2.link.net
196.205.232 ns1.link.net
196.205.232 ns2.link.net
196.205.233 ns1.link.net
196.205.233 ns2.link.net
196.205.234 ns1.link.net
196.205.234 ns2.link.net
196.205.235 ns1.link.net
196.205.235 ns2.link.net
196.205.236 ns1.link.net
196.205.236 ns2.link.net
196.205.237 ns1.link.net
196.205.237 ns2.link.net
196.205.238 ns1.link.net
196.205.238 ns2.link.net
196.205.239 ns1.link.net
196.205.239 ns2.link.net
196.205.240 ns1.link.net
196.205.240 ns2.link.net
196.205.241 ns1.link.net
196.205.241 ns2.link.net
196.205.242 ns1.link.net
196.205.242 ns2.link.net
196.205.243 ns1.link.net
196.205.243 ns2.link.net
196.205.244 ns1.link.net
196.205.244 ns2.link.net
196.205.245 ns1.link.net
196.205.245 ns2.link.net
196.205.246 ns1.link.net
196.205.246 ns2.link.net
196.205.247 ns1.link.net
196.205.247 ns2.link.net
196.205.248 ns1.link.net
196.205.248 ns2.link.net
196.205.249 ns1.link.net
196.205.249 ns2.link.net
196.205.250 ns1.link.net
196.205.250 ns2.link.net
196.205.251 ns1.link.net
196.205.251 ns2.link.net
196.205.252 ns1.link.net
196.205.252 ns2.link.net
196.205.253 ns1.link.net
196.205.253 ns2.link.net
196.205.254 ns1.link.net
196.205.254 ns2.link.net
196.205.255 ns1.link.net
196.205.255 ns2.link.net
196.25.240 igubu.saix.net
196.25.240 sangoma.saix.net
196.25.240 induna.saix.net
196.25.240 sabela.saix.net
196.33.38 titan.is.co.za
196.33.38 demeter.is.co.za
196.33.38 jupiter.is.co.za
196.206.251 ns1.wanadoo.ma
196.206.251 ns2.wanadoo.ma
196.206.252 ns1.wanadoo.ma
196.206.252 ns2.wanadoo.ma
196.217.254 ns1.wanadoo.ma
196.217.254 ns2.wanadoo.ma
196.217.255 ns1.wanadoo.ma
196.217.255 ns2.wanadoo.ma
196.217.246 dns.menara.ma
196.217.246 dns1.menara.ma
196.218.254 ns1.tedata.net.jo
196.218.254 ns2.tedata.net.jo
41.194.2 ns.seychelles.net
41.194.2 ns2.seychelles.net
41.194.1 ns.seychelles.net
41.194.1 ns2.seychelles.net
41.194.3 ns.seychelles.net
41.194.3 ns2.seychelles.net
41.194.0 ns.seychelles.net
41.194.0 ns2.seychelles.net
196.206.240 ns1.wanadoo.ma
196.206.240 ns2.wanadoo.ma
217.52.64 ns1.mist-net.com
217.52.64 ns2.mist-net.com
217.52.72 ns1.mist-net.com
217.52.72 ns2.mist-net.com
217.52.26 ns1.mist-net.com
217.52.26 ns2.mist-net.com
41.249.252 dns.menara.ma
41.249.252 dns1.menara.ma
41.1.207 ns1.vodacombusiness.co.za
41.1.207 ns2.vodacombusiness.co.za
41.1.128 ns1.vodacombusiness.co.za
41.1.128 ns2.vodacombusiness.co.za
41.1.201 ns1.vodacombusiness.co.za
41.1.201 ns2.vodacombusiness.co.za
41.186.0 ns1.mtnonline.rw
41.186.0 ns2.mtnonline.rw
41.186.1 ns1.mtnonline.rw
41.186.1 ns2.mtnonline.rw
41.186.2 ns1.mtnonline.rw
41.186.2 ns2.mtnonline.rw
41.186.3 ns1.mtnonline.rw
41.186.3 ns2.mtnonline.rw
41.186.4 ns1.mtnonline.rw
41.186.4 ns2.mtnonline.rw
41.186.5 ns1.mtnonline.rw
41.186.5 ns2.mtnonline.rw
41.186.6 ns1.mtnonline.rw
41.186.6 ns2.mtnonline.rw
41.186.7 ns1.mtnonline.rw
41.186.7 ns2.mtnonline.rw
41.186.8 ns1.mtnonline.rw
41.186.8 ns2.mtnonline.rw
41.186.9 ns1.mtnonline.rw
41.186.9 ns2.mtnonline.rw
41.186.10 ns1.mtnonline.rw
41.186.10 ns2.mtnonline.rw
41.186.11 ns1.mtnonline.rw
41.186.11 ns2.mtnonline.rw
41.186.12 ns1.mtnonline.rw
41.186.12 ns2.mtnonline.rw
41.186.13 ns1.mtnonline.rw
41.186.13 ns2.mtnonline.rw
41.186.14 ns1.mtnonline.rw
41.186.14 ns2.mtnonline.rw
41.186.15 ns1.mtnonline.rw
41.186.15 ns2.mtnonline.rw
41.186.16 ns1.mtnonline.rw
41.186.16 ns2.mtnonline.rw
41.186.17 ns1.mtnonline.rw
41.186.17 ns2.mtnonline.rw
41.186.18 ns1.mtnonline.rw
41.186.18 ns2.mtnonline.rw
41.186.19 ns1.mtnonline.rw
41.186.19 ns2.mtnonline.rw
41.186.20 ns1.mtnonline.rw
41.186.20 ns2.mtnonline.rw
41.1.136 ns1.vodacombusiness.co.za
41.1.136 ns2.vodacombusiness.co.za
41.248.248 dns.menara.ma
41.248.248 dns1.menara.ma
41.251.255 dns.menara.ma
41.251.255 dns1.menara.ma
41.251.254 dns.menara.ma
41.251.254 dns1.menara.ma
41.251.250 dns.menara.ma
41.251.250 dns1.menara.ma
41.192.255 ns01.socialcode.biz
41.192.255 ns02.socialcode.biz
41.94.0 ns1.morenet.ac.mz
41.94.0 zebra.uem.mz
41.94.10 ns1.morenet.ac.mz
41.94.10 zebra.uem.mz
41.94.8 ns1.morenet.ac.mz
41.94.8 zebra.uem.mz
196.25.146 igubu.saix.net
196.25.146 sangoma.saix.net
196.25.146 induna.saix.net
196.25.146 sabela.saix.net
196.25.147 igubu.saix.net
196.25.147 sangoma.saix.net
196.25.147 induna.saix.net
196.25.147 sabela.saix.net
197.235.1 ns1.vm.co.mz
197.235.1 ns2.vm.co.mz
41.186.24 ns1.mtnonline.rw
41.186.24 ns2.mtnonline.rw
41.186.22 ns1.mtnonline.rw
41.186.22 ns2.mtnonline.rw
41.186.36 ns1.mtnonline.rw
41.186.36 ns2.mtnonline.rw
41.186.44 ns1.mtnonline.rw
41.186.44 ns1.mtnonline.rw
41.231.7 ns1.atlax.com
41.231.7 ns2.atlax.com
41.231.7 ns3.atlax.com
41.248.226 dns.menara.ma
41.248.226 dns1.menara.ma
154.120.192 217.15.112.171
154.120.192 217.15.112.170
196.49.3 196.49.3.11
41.60.1 auth1.liquidtelecom.com
41.60.1 auth2.liquidtelecom.com
41.60.10 dns1.realtime.zm
41.60.10 dns2.realtime.zm
41.60.10 dns3.realtime.zm
41.60.10 dns4.realtime.zm
41.60.14 auth1.liquidtelecom.com
41.60.14 auth2.liquidtelecom.com
41.60.129 auth1.liquidtelecom.com
41.60.129 auth2.liquidtelecom.com
41.60.130 auth1.liquidtelecom.com
41.60.130 auth2.liquidtelecom.com
105.255.128 ns1.vodacombusiness.co.za
105.255.128 ns2.vodacombusiness.co.za
105.255.209 ns1.vodacombusiness.co.za
105.255.209 ns2.vodacombusiness.co.za
105.255.127 ns1.vodacombusiness.co.za
105.255.127 ns2.vodacombusiness.co.za
105.255.130 ns1.vodacombusiness.co.za
105.255.130 ns21.vodacombusiness.co.za
105.255.131 ns1.vodacombusiness.co.za
105.255.131 ns2.vodacombusiness.co.za
105.255.132 ns1.vodacombusiness.co.za
105.255.132 ns2.vodacombusiness.co.za
105.255.133 ns1.vodacombusiness.co.za
105.255.133 ns2.vodacombusiness.co.za
105.255.134 ns1.vodacombusiness.co.za
105.255.134 ns2.vodacombusiness.co.za
105.255.135 ns1.vodacombusiness.co.za
105.255.135 ns2.vodacombusiness.co.za
105.255.136 ns1.vodacombusiness.co.za
105.255.136 ns2.vodacombusiness.co.za
105.255.137 ns1.vodacombusiness.co.za
105.255.137 ns2.vodacombusiness.co.za
105.255.138 ns1.vodacombusiness.co.za
105.255.138 ns2.vodacombusiness.co.za
105.255.141 ns1.vodacombusiness.co.za
105.255.141 ns2.vodacombusiness.co.za
105.255.145 ns1.vodacombusiness.co.za
105.255.145 ns2.vodacombusiness.co.za
105.255.152 ns1.vodacombusiness.co.za
105.255.152 ns2.vodacombusiness.co.za
105.255.153 ns1.vodacombusiness.co.za
105.255.153 ns2.vodacombusiness.co.za
105.255.165 ns1.vodacombusiness.co.za
105.255.165 ns2.vodacombusiness.co.za
105.255.192 ns1.vodacombusiness.co.za
105.255.192 ns2.vodacombusiness.co.za
105.255.216 ns1.vodacombusiness.co.za
105.255.216 ns2.vodacombusiness.co.za
105.255.217 ns1.vodacombusiness.co.za
105.255.217 ns2.vodacombusiness.co.za
105.255.237 ns1.vodacombusiness.co.za
105.255.237 ns2.vodacombusiness.co.za
105.255.146 ns1.vodacombusiness.co.za
105.255.146 ns2.vodacombusiness.co.za
105.255.129 ns1.vodacombusiness.co.za
105.255.129 ns2.vodacombusiness.co.za
105.255.139 ns1.vodacombusiness.co.za
105.255.139 ns2.vodacombusiness.co.za
105.255.140 ns1.vodacombusiness.co.za
105.255.140 ns2.vodacombusiness.co.za
105.255.142 ns1.vodacombusiness.co.za
105.255.142 ns2.vodacombusiness.co.za
105.255.143 ns1.vodacombusiness.co.za
105.255.143 ns2.vodacombusiness.co.za
105.255.144 ns1.vodacombusiness.co.za
105.255.144 ns2.vodacombusiness.co.za
105.255.147 ns1.vodacombusiness.co.za
105.255.147 ns2.vodacombusiness.co.za
105.255.148 ns1.vodacombusiness.co.za
105.255.148 ns2.vodacombusiness.co.za
105.255.149 ns1.vodacombusiness.co.za
105.255.149 ns2.vodacombusiness.co.za
105.255.150 ns1.vodacombusiness.co.za
105.255.150 ns2.vodacombusiness.co.za
105.255.151 ns1.vodacombusiness.co.za
105.255.151 ns2.vodacombusiness.co.za
105.255.154 ns1.vodacombusiness.co.za
105.255.154 ns2.vodacombusiness.co.za
105.255.155 ns1.vodacombusiness.co.za
105.255.155 ns2.vodacombusiness.co.za
105.255.160 ns1.vodacombusiness.co.za
105.255.160 ns2.vodacombusiness.co.za
105.255.161 ns1.vodacombusiness.co.za
105.255.161 ns2.vodacombusiness.co.za
105.255.164 ns1.vodacombusiness.co.za
105.255.164 ns2.vodacombusiness.co.za
105.255.176 ns1.vodacombusiness.co.za
105.255.176 ns2.vodacombusiness.co.za
105.255.177 ns1.vodacombusiness.co.za
105.255.177 ns2.vodacombusiness.co.za
105.255.184 ns1.vodacombusiness.co.za
105.255.184 ns2.vodacombusiness.co.za
105.255.193 ns1.vodacombusiness.co.za
105.255.193 ns2.vodacombusiness.co.za
105.255.194 ns1.vodacombusiness.co.za
105.255.194 ns2.vodacombusiness.co.za
105.255.195 ns1.vodacombusiness.co.za
105.255.195 ns2.vodacombusiness.co.za
105.255.200 ns1.vodacombusiness.co.za
105.255.200 ns2.vodacombusiness.co.za
105.255.206 ns1.vodacombusiness.co.za
105.255.206 ns2.vodacombusiness.co.za
105.255.208 ns1.vodacombusiness.co.za
105.255.208 ns2.vodacombusiness.co.za
105.255.218 ns1.vodacombusiness.co.za
105.255.218 ns2.vodacombusiness.co.za
105.255.219 ns1.vodacombusiness.co.za
105.255.219 ns2.vodacombusiness.co.za
129.205.80 41.161.16.132
129.205.80 41.160.80.8
129.205.81 41.161.16.132
129.205.81 41.160.80.8
41.60.131 auth1.liquidtelecom.com
41.60.131 auth2.liquidtelecom.com
41.60.22 auth1.liquidtelecom.com
41.60.22 auth2.liquidtelecom.com
41.60.230 auth1.liquidtelecom.com
41.60.230 auth2.liquidtelecom.com
41.60.3 auth1.liquidtelecom.com
41.60.3 auth2.liquidtelecom.com
41.60.231 ns1.liquidtelecom.net
41.60.231 ns2.liquidtelecom.net
41.60.137 ns1.liquidtelecom.net
41.60.137 ns2.liquidtelecom.net
41.60.208 ns1.liquidtelecom.net
41.60.208 ns2.liquidtelecom.net
41.60.209 ns1.liquidtelecom.net
41.60.209 ns2.liquidtelecom.net
41.60.210 ns1.liquidtelecom.net
41.60.210 ns2.liquidtelecom.net
41.60.211 ns1.liquidtelecom.net
41.60.211 ns2.liquidtelecom.net
41.60.212 ns1.liquidtelecom.net
41.60.212 ns2.liquidtelecom.net
41.60.213 ns1.liquidtelecom.net
41.60.213 ns2.liquidtelecom.net
41.60.214 ns1.liquidtelecom.net
41.60.214 ns2.liquidtelecom.net
41.60.215 ns1.liquidtelecom.net
41.60.215 ns2.liquidtelecom.net
41.60.216 ns1.liquidtelecom.net
41.60.216 ns2.liquidtelecom.net
41.60.217 ns1.liquidtelecom.net
41.60.217 ns2.liquidtelecom.net
41.60.218 ns1.liquidtelecom.net
41.60.218 ns2.liquidtelecom.net
41.60.219 ns1.liquidtelecom.net
41.60.219 ns2.liquidtelecom.net
41.60.220 ns1.liquidtelecom.net
41.60.220 ns2.liquidtelecom.net
41.60.221 ns1.liquidtelecom.net
41.60.221 ns2.liquidtelecom.net
41.60.222 ns1.liquidtelecom.net
41.60.222 ns2.liquidtelecom.net
41.60.223 ns1.liquidtelecom.net
41.60.223 ns2.liquidtelecom.net
41.60.224 ns1.liquidtelecom.net
41.60.224 ns2.liquidtelecom.net
41.60.200 ns1.liquidtelecom.co.zw
41.60.200 ns2.liquidtelecom.co.zw
41.60.200 ns3.liquidtelecom.co.zw
41.60.200 ns4.liquidtelecom.com
41.60.201 ns1.liquidtelecom.co.zw
41.60.201 ns2.liquidtelecom.co.zw
41.60.201 ns3.liquidtelecom.co.zw
41.60.201 ns4.liquidtelecom.com
41.60.202 ns1.liquidtelecom.co.zw
41.60.202 ns2.liquidtelecom.co.zw
41.60.202 ns3.liquidtelecom.co.zw
41.60.202 ns4.liquidtelecom.com
41.60.203 ns1.liquidtelecom.co.zw
41.60.203 ns2.liquidtelecom.co.zw
41.60.203 ns3.liquidtelecom.co.zw
41.60.203 ns4.liquidtelecom.com
41.60.204 ns1.liquidtelecom.co.zw
41.60.204 ns2.liquidtelecom.co.zw
41.60.204 ns3.liquidtelecom.co.zw
41.60.204 ns4.liquidtelecom.com
41.60.205 ns1.liquidtelecom.co.zw
41.60.205 ns2.liquidtelecom.co.zw
41.60.205 ns3.liquidtelecom.co.zw
41.60.205 ns4.liquidtelecom.com
41.60.206 ns1.liquidtelecom.co.zw
41.60.206 ns2.liquidtelecom.co.zw
41.60.206 ns3.liquidtelecom.co.zw
41.60.206 ns4.liquidtelecom.com
41.60.207 ns1.liquidtelecom.co.zw
41.60.207 ns2.liquidtelecom.co.zw
41.60.207 ns3.liquidtelecom.co.zw
41.60.207 ns4.liquidtelecom.com
105.234.0 ns1.airtel.africa
105.234.0 ns2.airtel.africa
41.60.188 ns1.liquidtelecom.net
41.60.188 ns2.liquidtelecom.net
196.179.252 ns.tunet.tn
196.179.252 ns2.tunet.tn
41.60.228 ns1.liquidtelecom.net
41.60.228 ns2.liquidtelecom.net
196.201.11 ns1.rcswimax.com
196.201.11 ns2.rcswimax.com
154.73.4 154.73.6.242
154.73.4 196.6.111.242
41.1.51 dnsinfo1-cte-pt.3g.vodacom.co.za
41.1.51 dnsinfo1-dne-pt.3g.vodacom.co.za
41.1.51 dnsinfo1-mtp-pt.3g.vodacom.co.za
41.1.51 dnsinfo1-psi-pt.3g.vodacom.co.za
41.1.51 dnsinfo1-cfo.3g.vodacom.co.za
41.1.51 dnsinfo1-dmo.3g.vodacom.co.za
41.1.51 dnsinfo1-mdp.3g.vodacom.co.za
41.1.51 dnsinfo1-prs.3g.vodacom.co.za
41.1.114 dnsinfo1-cte-pt.3g.vodacom.co.za
41.1.114 dnsinfo1-dne-pt.3g.vodacom.co.za
41.1.114 dnsinfo1-mtp-pt.3g.vodacom.co.za
41.1.114 dnsinfo1-psi-pt.3g.vodacom.co.za
41.1.114 dnsinfo1-cfo.3g.vodacom.co.za
41.1.114 dnsinfo1-dmo.3g.vodacom.co.za
41.1.114 dnsinfo1-mdp.3g.vodacom.co.za
41.1.114 dnsinfo1-prs.3g.vodacom.co.za
41.1.47 dnsinfo1-cte-pt.3g.vodacom.co.za
41.1.47 dnsinfo1-dne-pt.3g.vodacom.co.za
41.1.47 dnsinfo1-mtp-pt.3g.vodacom.co.za
41.1.47 dnsinfo1-psi-pt.3g.vodacom.co.za
41.1.47 dnsinfo1-cfo.3g.vodacom.co.za
41.1.47 dnsinfo1-dmo.3g.vodacom.co.za
41.1.47 dnsinfo1-mdp.3g.vodacom.co.za
41.1.47 dnsinfo1-prs.3g.vodacom.co.za
41.1.111 dnsinfo1-cte-pt.3g.vodacom.co.za
41.1.111 dnsinfo1-dne-pt.3g.vodacom.co.za
41.1.111 dnsinfo1-mtp-pt.3g.vodacom.co.za
41.1.111 dnsinfo1-psi-pt.3g.vodacom.co.za
41.1.111 dnsinfo1-cfo.3g.vodacom.co.za
41.1.111 dnsinfo1-dmo.3g.vodacom.co.za
41.1.111 dnsinfo1-mdp.3g.vodacom.co.za
41.1.111 dnsinfo1-prs.3g.vodacom.co.za
41.1.161 dnsinfo1-cte-pt.3g.vodacom.co.za
41.1.161 dnsinfo1-dne-pt.3g.vodacom.co.za
41.1.161 dnsinfo1-mtp-pt.3g.vodacom.co.za
41.1.161 dnsinfo1-psi-pt.3g.vodacom.co.za
41.1.161 dnsinfo1-cfo.3g.vodacom.co.za
41.1.161 dnsinfo1-dmo.3g.vodacom.co.za
41.1.161 dnsinfo1-mdp.3g.vodacom.co.za
41.1.161 dnsinfo1-prs.3g.vodacom.co.za
41.1.239 dnsinfo1-cte-pt.3g.vodacom.co.za
41.1.239 dnsinfo1-dne-pt.3g.vodacom.co.za
41.1.239 dnsinfo1-mtp-pt.3g.vodacom.co.za
41.1.239 dnsinfo1-psi-pt.3g.vodacom.co.za
41.1.239 dnsinfo1-cfo.3g.vodacom.co.za
41.1.239 dnsinfo1-dmo.3g.vodacom.co.za
41.1.239 dnsinfo1-mdp.3g.vodacom.co.za
41.1.239 dnsinfo1-prs.3g.vodacom.co.za
41.1.176 dnsinfo1-cte-pt.3g.vodacom.co.za
41.1.176 dnsinfo1-dne-pt.3g.vodacom.co.za
41.1.176 dnsinfo1-mtp-pt.3g.vodacom.co.za
41.1.176 dnsinfo1-psi-pt.3g.vodacom.co.za
41.1.176 dnsinfo1-cfo.3g.vodacom.co.za
41.1.176 dnsinfo1-dmo.3g.vodacom.co.za
41.1.176 dnsinfo1-mdp.3g.vodacom.co.za
41.1.176 dnsinfo1-prs.3g.vodacom.co.za
41.1.240 dnsinfo1-cte-pt.3g.vodacom.co.za
41.1.240 dnsinfo1-dne-pt.3g.vodacom.co.za
41.1.240 dnsinfo1-mtp-pt.3g.vodacom.co.za
41.1.240 dnsinfo1-psi-pt.3g.vodacom.co.za
41.1.240 dnsinfo1-cfo.3g.vodacom.co.za
41.1.240 dnsinfo1-dmo.3g.vodacom.co.za
41.1.240 dnsinfo1-mdp.3g.vodacom.co.za
41.1.240 dnsinfo1-prs.3g.vodacom.co.za
197.231.251 ns2
196.201.8 ns1.rcswimax.com
196.201.8 ns2.rcswimax.com
196.201.9 ns1.rcswimax.com
196.201.9 ns2.rcswimax.com
196.201.10 ns1.rcswimax.com
196.201.10 ns2.rcswimax.com
197.231.248 ns3
196.203.0 ns4.ati.tn
196.203.0 ns6.ati.tn
217.52.0 ns.aucegypt.edu
217.52.0 ns3.aucegypt.edu
196.203.1 ns4.ati.tn
196.203.1 ns6.ati.tn
217.52.1 ns.aucegypt.edu
217.52.1 ns3.aucegypt.edu
62.139.104 ns1.nile-online.net
62.139.104 ns2.nile-online.net
62.139.105 ns1.nile-online.net
62.139.105 ns2.nile-online.net
62.139.109 ns1.nile-online.net
62.139.109 ns2.nile-online.net
62.139.130 ns1.nile-online.net
62.139.130 ns2.nile-online.net
196.203.2 ns4.ati.tn
196.203.2 ns6.ati.tn
217.52.2 ns.aucegypt.edu
217.52.2 ns3.aucegypt.edu
62.139.253 ns2.egynet.com.eg
62.139.253 ns22.egynet.com.eg
217.52.3 ns.aucegypt.edu
217.52.3 ns3.aucegypt.edu
196.203.32 ns4.ati.tn
196.203.32 ns6.ati.tn
196.203.33 ns4.ati.tn
196.203.33 ns6.ati.tn
196.203.34 ns4.ati.tn
196.203.34 ns6.ati.tn
196.203.35 ns1.hexabyte.tn
196.203.35 ns2.hexabyte.tn
196.203.36 ns4.ati.tn
196.203.36 ns6.ati.tn
217.52.4 ns.aucegypt.edu
217.52.4 ns3.aucegypt.edu
217.52.5 ns.aucegypt.edu
217.52.5 ns3.aucegypt.edu
217.52.6 ns.aucegypt.edu
217.52.6 ns3.aucegypt.edu
217.52.7 ns.aucegypt.edu
217.52.7 ns3.aucegypt.edu
217.52.8 ns.aucegypt.edu
217.52.8 ns3.aucegypt.edu
196.205.11 ns1.link.net
196.205.11 ns2.link.net
212.0.159 sun1.sudatel.net
212.0.148 ns1.sudanmail.net
212.0.148 ns2.sudanmail.net
212.0.129 main.sdn-mobitel.com
212.0.129 main.sdn-mobinet.net
196.202.144 ns1.sudacom.net
196.202.144 ns2.sudacom.net
196.202.145 ns1.sudacom.net
196.202.145 ns2.sudacom.net
212.0.138 sun1.sudanet.net
212.0.146 sun1.sudanet.net
163.196 ns1.qdata.net
163.196 ns2.qdata.net
196.25.226 igubu.saix.net
196.25.226 sangoma.saix.net
196.205.177 ns1.link.net
196.205.177 ns2.link.net
196.205.0 ns1.link.net
196.205.0 ns2.link.net
196.205.1 ns1.link.net
196.205.1 ns2.link.net
196.205.2 ns1.link.net
196.205.2 ns2.link.net
196.205.3 ns1.link.net
196.205.3 ns2.link.net
196.205.4 ns1.link.net
196.205.4 ns2.link.net
196.205.5 ns1.link.net
196.205.5 ns2.link.net
196.205.6 ns1.link.net
196.205.6 ns2.link.net
196.205.7 ns1.link.net
196.205.7 ns2.link.net
196.205.8 ns1.link.net
196.205.8 ns2.link.net
196.205.9 ns1.link.net
196.205.9 ns2.link.net
196.205.10 ns1.link.net
196.205.10 ns2.link.net
196.205.12 ns1.link.net
196.205.12 ns2.link.net
196.205.13 ns1.link.net
196.205.13 ns2.link.net
196.205.14 ns1.link.net
196.205.14 ns2.link.net
196.205.15 ns1.link.net
196.205.15 ns2.link.net
196.205.16 ns1.link.net
196.205.16 ns2.link.net
196.205.17 ns1.link.net
196.205.17 ns2.link.net
196.205.18 ns1.link.net
196.205.18 ns2.link.net
196.205.19 ns1.link.net
196.205.19 ns2.link.net
196.205.20 ns1.link.net
196.205.20 ns2.link.net
196.205.21 ns1.link.net
196.205.21 ns2.link.net
196.205.22 ns1.link.net
196.205.22 ns2.link.net
196.205.23 ns1.link.net
196.205.23 ns2.link.net
196.205.24 ns1.link.net
196.205.24 ns2.link.net
196.205.25 ns1.link.net
196.205.25 ns2.link.net
196.205.26 ns1.link.net
196.205.26 ns2.link.net
196.205.27 ns1.link.net
196.205.27 ns2.link.net
196.205.28 ns1.link.net
196.205.28 ns2.link.net
196.205.29 ns1.link.net
196.205.29 ns2.link.net
196.205.30 ns1.link.net
196.205.30 ns2.link.net
196.205.31 ns1.link.net
196.205.31 ns2.link.net
196.205.32 ns1.link.net
196.205.32 ns2.link.net
196.205.33 ns1.link.net
196.205.33 ns2.link.net
196.205.34 ns1.link.net
196.205.34 ns2.link.net
196.205.36 ns1.link.net
196.205.36 ns2.link.net
196.205.37 ns1.link.net
196.205.37 ns2.link.net
196.205.38 ns1.link.net
196.205.38 ns2.link.net
196.205.39 ns1.link.net
196.205.39 ns2.link.net
196.205.40 ns1.link.net
196.205.40 ns2.link.net
196.205.35 ns1.link.net
196.205.35 ns2.link.net
196.205.55 ns1.link.net
196.205.55 ns2.link.net
196.205.43 ns1.link.net
196.205.43 ns2.link.net
196.205.60 ns1.link.net
196.205.60 ns2.link.net
196.205.49 ns1.link.net
196.205.49 ns2.link.net
196.205.44 ns1.link.net
196.205.44 ns2.link.net
196.205.46 ns1.link.net
196.205.46 ns2.link.net
196.205.52 ns1.link.net
196.205.52 ns2.link.net
196.205.53 ns1.link.net
196.205.53 ns2.link.net
196.205.50 ns1.link.net
196.205.50 ns2.link.net
196.205.51 ns1.link.net
196.205.51 ns2.link.net
196.205.59 ns1.link.net
196.205.59 ns2.link.net
196.205.47 ns1.link.net
196.205.47 ns2.link.net
196.205.48 ns1.link.net
196.205.48 ns2.link.net
196.205.56 ns1.link.net
196.205.56 ns2.link.net
196.205.45 ns1.link.net
196.205.45 ns2.link.net
196.205.42 ns1.link.net
196.205.42 ns2.link.net
196.205.58 ns1.link.net
196.205.58 ns2.link.net
196.205.54 ns1.link.net
196.205.54 ns2.link.net
196.205.41 ns1.link.net
196.205.41 ns2.link.net
196.205.57 ns1.link.net
196.205.57 ns2.link.net
196.205.61 ns1.link.net
196.205.61 ns2.link.net
196.205.62 ns1.link.net
196.205.62 ns2.link.net
196.205.63 ns1.link.net
196.205.63 ns2.link.net
196.205.64 ns1.link.net
196.205.64 ns2.link.net
196.205.65 ns1.link.net
196.205.65 ns2.link.net
196.205.66 ns1.link.net
196.205.66 ns2.link.net
196.205.67 ns1.link.net
196.205.67 ns2.link.net
196.205.68 ns1.link.net
196.205.68 ns2.link.net
196.205.69 ns1.link.net
196.205.69 ns2.link.net
196.205.70 ns1.link.net
196.205.70 ns2.link.net
196.205.71 ns1.link.net
196.205.71 ns2.link.net
196.205.72 ns1.link.net
196.205.72 ns2.link.net
196.205.74 ns1.link.net
196.205.74 ns2.link.net
196.205.77 ns1.link.net
196.205.77 ns2.link.net
196.205.78 ns1.link.net
196.205.78 ns2.link.net
196.205.79 ns1.link.net
196.205.79 ns2.link.net
196.205.73 ns1.link.net
196.205.73 ns2.link.net
196.205.75 ns1.link.net
196.205.75 ns2.link.net
196.205.82 ns1.link.net
196.205.82 ns2.link.net
196.205.76 ns1.link.net
196.205.76 ns2.link.net
196.205.80 ns1.link.net
196.205.80 ns2.link.net
196.205.81 ns1.link.net
196.205.81 ns2.link.net
196.205.83 ns1.link.net
196.205.83 ns2.link.net
196.205.84 ns1.link.net
196.205.84 ns2.link.net
196.205.85 ns1.link.net
196.205.85 ns2.link.net
196.205.86 ns1.link.net
196.205.86 ns2.link.net
196.205.87 ns1.link.net
196.205.87 ns2.link.net
196.205.88 ns1.link.net
196.205.88 ns2.link.net
196.205.89 ns1.link.net
196.205.89 ns2.link.net
196.205.90 ns1.link.net
196.205.90 ns2.link.net
196.205.91 ns1.link.net
196.205.91 ns2.link.net
196.205.92 ns1.link.net
196.205.92 ns2.link.net
196.205.93 ns1.link.net
196.205.93 ns2.link.net
196.205.94 ns1.link.net
196.205.94 ns2.link.net
196.205.95 ns1.link.net
196.205.95 ns2.link.net
196.205.96 ns1.link.net
196.205.96 ns2.link.net
196.205.97 ns1.link.net
196.205.97 ns2.link.net
196.205.98 ns1.link.net
196.205.98 ns2.link.net
196.205.99 ns1.link.net
196.205.99 ns2.link.net
196.205.100 ns1.link.net
196.205.100 ns2.link.net
196.205.101 ns1.link.net
196.205.101 ns2.link.net
196.205.102 ns1.link.net
196.205.102 ns2.link.net
196.205.103 ns1.link.net
196.205.103 ns2.link.net
196.205.104 ns1.link.net
196.205.104 ns2.link.net
196.205.105 ns1.link.net
196.205.105 ns2.link.net
196.205.106 ns1.link.net
196.205.106 ns2.link.net
196.205.107 ns1.link.net
196.205.107 ns2.link.net
196.205.108 ns1.link.net
196.205.108 ns2.link.net
196.205.109 ns1.link.net
196.205.109 ns2.link.net
196.205.110 ns1.link.net
196.205.110 ns2.link.net
196.205.111 ns1.link.net
196.205.111 ns2.link.net
196.205.112 ns1.link.net
196.205.112 ns2.link.net
196.205.113 ns1.link.net
196.205.113 ns2.link.net
196.205.115 ns1.link.net
196.205.115 ns2.link.net
196.205.116 ns1.link.net
196.205.116 ns2.link.net
196.205.114 ns1.link.net
196.205.114 ns2.link.net
196.205.117 ns1.link.net
196.205.117 ns2.link.net
196.205.118 ns1.link.net
196.205.118 ns2.link.net
196.205.119 ns1.link.net
196.205.119 ns2.link.net
196.205.120 ns1.link.net
196.205.120 ns2.link.net
196.205.121 ns1.link.net
196.205.121 ns2.link.net
196.205.122 ns1.link.net
196.205.122 ns2.link.net
196.205.123 ns1.link.net
196.205.123 ns2.link.net
196.205.124 ns1.link.net
196.205.124 ns2.link.net
196.205.125 ns1.link.net
196.205.125 ns2.link.net
196.205.126 ns1.link.net
196.205.126 ns2.link.net
196.205.127 ns1.link.net
196.205.127 ns2.link.net
196.205.128 ns1.link.net
196.205.128 ns2.link.net
196.205.129 ns1.link.net
196.205.129 ns2.link.net
196.205.130 ns1.link.net
196.205.130 ns2.link.net
196.205.131 ns1.link.net
196.205.131 ns2.link.net
196.205.132 ns1.link.net
196.205.132 ns2.link.net
196.205.133 ns1.link.net
196.205.133 ns2.link.net
196.205.134 ns1.link.net
196.205.134 ns2.link.net
196.205.135 ns1.link.net
196.205.135 ns2.link.net
196.205.136 ns1.link.net
196.205.136 ns2.link.net
196.205.137 ns1.link.net
196.205.137 ns2.link.net
196.205.138 ns1.link.net
196.205.138 ns2.link.net
196.205.139 ns1.link.net
196.205.139 ns2.link.net
196.205.140 ns1.link.net
196.205.140 ns2.link.net
196.205.141 ns1.link.net
196.205.141 ns2.link.net
196.205.142 ns1.link.net
196.205.142 ns2.link.net
196.205.143 ns1.link.net
196.205.143 ns2.link.net
196.205.144 ns1.link.net
196.205.144 ns2.link.net
196.205.145 ns1.link.net
196.205.145 ns2.link.net
196.205.146 ns1.link.net
196.205.146 ns2.link.net
196.205.147 ns1.link.net
196.205.147 ns2.link.net
196.205.148 ns1.link.net
196.205.148 ns2.link.net
196.205.149 ns1.link.net
196.205.149 ns2.link.net
196.205.150 ns1.link.net
196.205.150 ns2.link.net
196.205.151 ns1.link.net
196.205.151 ns2.link.net
196.205.152 ns1.link.net
196.205.152 ns2.link.net
196.205.153 ns1.link.net
196.205.153 ns2.link.net
196.205.154 ns1.link.net
196.205.154 ns2.link.net
196.205.155 ns1.link.net
196.205.155 ns2.link.net
196.205.156 ns1.link.net
196.205.156 ns2.link.net
196.205.157 ns1.link.net
196.205.157 ns2.link.net
196.205.158 ns1.link.net
196.205.158 ns2.link.net
196.205.159 ns1.link.net
196.205.159 ns2.link.net
196.205.160 ns1.link.net
196.205.160 ns2.link.net
196.205.161 ns1.link.net
196.205.161 ns2.link.net
196.205.162 ns1.link.net
196.205.162 ns2.link.net
196.205.163 ns1.link.net
196.205.163 ns2.link.net
196.205.164 ns1.link.net
196.205.164 ns2.link.net
196.205.165 ns1.link.net
196.205.165 ns2.link.net
196.205.166 ns1.link.net
196.205.166 ns2.link.net
196.205.167 ns1.link.net
196.205.167 ns2.link.net
196.205.168 ns1.link.net
196.205.168 ns2.link.net
196.205.169 ns1.link.net
196.205.169 ns2.link.net
196.205.170 ns1.link.net
196.205.170 ns2.link.net
196.205.172 ns1.link.net
196.205.172 ns2.link.net
196.205.171 ns1.link.net
196.205.171 ns2.link.net
196.205.173 ns1.link.net
196.205.173 ns2.link.net
196.205.174 ns1.link.net
196.205.174 ns2.link.net
196.205.175 ns1.link.net
196.205.175 ns2.link.net
196.205.176 ns1.link.net
196.205.176 ns2.link.net
196.205.178 ns1.link.net
196.205.178 ns2.link.net
196.205.179 ns1.link.net
196.205.179 ns2.link.net
196.205.180 ns1.link.net
196.205.180 ns2.link.net
196.205.181 ns1.link.net
196.205.181 ns2.link.net
196.205.182 ns1.link.net
196.205.182 ns2.link.net
196.205.183 ns1.link.net
196.205.183 ns2.link.net
196.205.184 ns1.link.net
196.205.184 ns2.link.net
196.205.185 ns1.link.net
196.205.185 ns2.link.net
196.205.186 ns1.link.net
196.205.186 ns2.link.net
196.205.187 ns1.link.net
196.205.187 ns2.link.net
196.205.188 ns1.link.net
196.205.188 ns2.link.net
196.205.189 ns1.link.net
196.205.189 ns2.link.net
196.205.190 ns1.link.net
196.205.190 ns2.link.net
196.205.191 ns1.link.net
196.205.191 ns2.link.net
196.205.192 ns1.link.net
196.205.192 ns2.link.net
196.205.193 ns1.link.net
196.205.193 ns2.link.net
196.205.194 ns1.link.net
196.205.194 ns2.link.net
196.205.195 ns1.link.net
196.205.195 ns2.link.net
196.205.196 ns1.link.net
196.205.196 ns2.link.net
196.205.197 ns1.link.net
196.205.197 ns2.link.net
196.205.198 ns1.link.net
196.205.198 ns2.link.net
196.205.199 ns1.link.net
196.205.199 ns2.link.net
196.205.200 ns1.link.net
196.205.200 ns2.link.net
196.205.201 ns1.link.net
196.205.201 ns2.link.net
196.205.202 ns1.link.net
196.205.202 ns2.link.net
196.205.204 ns1.link.net
196.205.204 ns2.link.net
196.205.203 ns1.link.net
196.205.203 ns2.link.net
196.205.205 ns1.link.net
196.205.205 ns2.link.net
196.205.206 ns1.link.net
196.205.206 ns2.link.net
196.205.207 ns1.link.net
196.205.207 ns2.link.net
196.205.208 ns1.link.net
196.205.208 ns2.link.net
196.205.209 ns1.link.net
196.205.209 ns2.link.net
196.205.210 ns1.link.net
196.205.210 ns2.link.net
196.205.211 ns1.link.net
196.205.211 ns2.link.net
196.205.212 ns1.link.net
196.205.212 ns2.link.net
196.205.213 ns1.link.net
196.205.213 ns2.link.net
196.205.214 ns1.link.net
196.205.214 ns2.link.net
196.205.215 ns1.link.net
196.205.215 ns2.link.net
196.205.216 ns1.link.net
196.205.216 ns2.link.net
196.205.217 ns1.link.net
196.205.217 ns2.link.net
196.205.219 ns1.link.net
196.205.219 ns2.link.net
196.205.220 ns1.link.net
196.205.220 ns2.link.net
196.205.221 ns1.link.net
196.205.221 ns2.link.net
196.205.224 ns1.link.net
196.205.224 ns2.link.net
196.205.225 ns1.link.net
196.205.225 ns2.link.net
196.205.218 ns1.link.net
196.205.218 ns2.link.net
196.205.222 ns1.link.net
196.205.222 ns2.link.net
196.205.223 ns1.link.net
196.205.223 ns2.link.net
196.205.227 ns1.link.net
196.205.227 ns2.link.net
196.205.226 ns1.link.net
196.205.226 ns2.link.net
196.205.228 ns1.link.net
196.205.228 ns2.link.net
196.205.229 ns1.link.net
196.205.229 ns2.link.net
196.205.230 ns1.link.net
196.205.230 ns2.link.net
196.205.231 ns1.link.net
196.205.231 ns2.link.net
196.205.232 ns1.link.net
196.205.232 ns2.link.net
196.205.233 ns1.link.net
196.205.233 ns2.link.net
196.205.234 ns1.link.net
196.205.234 ns2.link.net
196.205.235 ns1.link.net
196.205.235 ns2.link.net
196.205.236 ns1.link.net
196.205.236 ns2.link.net
196.205.237 ns1.link.net
196.205.237 ns2.link.net
196.205.238 ns1.link.net
196.205.238 ns2.link.net
196.205.239 ns1.link.net
196.205.239 ns2.link.net
196.205.240 ns1.link.net
196.205.240 ns2.link.net
196.205.241 ns1.link.net
196.205.241 ns2.link.net
196.205.242 ns1.link.net
196.205.242 ns2.link.net
196.205.243 ns1.link.net
196.205.243 ns2.link.net
196.205.244 ns1.link.net
196.205.244 ns2.link.net
196.205.245 ns1.link.net
196.205.245 ns2.link.net
196.205.246 ns1.link.net
196.205.246 ns2.link.net
196.205.247 ns1.link.net
196.205.247 ns2.link.net
196.205.248 ns1.link.net
196.205.248 ns2.link.net
196.205.249 ns1.link.net
196.205.249 ns2.link.net
196.205.250 ns1.link.net
196.205.250 ns2.link.net
196.205.251 ns1.link.net
196.205.251 ns2.link.net
196.205.252 ns1.link.net
196.205.252 ns2.link.net
196.205.253 ns1.link.net
196.205.253 ns2.link.net
196.205.254 ns1.link.net
196.205.254 ns2.link.net
196.205.255 ns1.link.net
196.205.255 ns2.link.net
196.25.240 igubu.saix.net
196.25.240 sangoma.saix.net
196.25.240 induna.saix.net
196.25.240 sabela.saix.net
196.33.38 titan.is.co.za
196.33.38 demeter.is.co.za
196.33.38 jupiter.is.co.za
196.206.251 ns1.wanadoo.ma
196.206.251 ns2.wanadoo.ma
196.206.252 ns1.wanadoo.ma
196.206.252 ns2.wanadoo.ma
196.217.254 ns1.wanadoo.ma
196.217.254 ns2.wanadoo.ma
196.217.255 ns1.wanadoo.ma
196.217.255 ns2.wanadoo.ma
196.217.246 dns.menara.ma
196.217.246 dns1.menara.ma
196.218.254 ns1.tedata.net.jo
196.218.254 ns2.tedata.net.jo
41.194.2 ns.seychelles.net
41.194.2 ns2.seychelles.net
41.194.1 ns.seychelles.net
41.194.1 ns2.seychelles.net
41.194.3 ns.seychelles.net
41.194.3 ns2.seychelles.net
41.194.0 ns.seychelles.net
41.194.0 ns2.seychelles.net
196.206.240 ns1.wanadoo.ma
196.206.240 ns2.wanadoo.ma
217.52.64 ns1.mist-net.com
217.52.64 ns2.mist-net.com
217.52.72 ns1.mist-net.com
217.52.72 ns2.mist-net.com
217.52.26 ns1.mist-net.com
217.52.26 ns2.mist-net.com
41.249.252 dns.menara.ma
41.249.252 dns1.menara.ma
41.1.207 ns1.vodacombusiness.co.za
41.1.207 ns2.vodacombusiness.co.za
41.1.128 ns1.vodacombusiness.co.za
41.1.128 ns2.vodacombusiness.co.za
41.1.201 ns1.vodacombusiness.co.za
41.1.201 ns2.vodacombusiness.co.za
41.186.0 ns1.mtnonline.rw
41.186.0 ns2.mtnonline.rw
41.186.1 ns1.mtnonline.rw
41.186.1 ns2.mtnonline.rw
41.186.2 ns1.mtnonline.rw
41.186.2 ns2.mtnonline.rw
41.186.3 ns1.mtnonline.rw
41.186.3 ns2.mtnonline.rw
41.186.4 ns1.mtnonline.rw
41.186.4 ns2.mtnonline.rw
41.186.5 ns1.mtnonline.rw
41.186.5 ns2.mtnonline.rw
41.186.6 ns1.mtnonline.rw
41.186.6 ns2.mtnonline.rw
41.186.7 ns1.mtnonline.rw
41.186.7 ns2.mtnonline.rw
41.186.8 ns1.mtnonline.rw
41.186.8 ns2.mtnonline.rw
41.186.9 ns1.mtnonline.rw
41.186.9 ns2.mtnonline.rw
41.186.10 ns1.mtnonline.rw
41.186.10 ns2.mtnonline.rw
41.186.11 ns1.mtnonline.rw
41.186.11 ns2.mtnonline.rw
41.186.12 ns1.mtnonline.rw
41.186.12 ns2.mtnonline.rw
41.186.13 ns1.mtnonline.rw
41.186.13 ns2.mtnonline.rw
41.186.14 ns1.mtnonline.rw
41.186.14 ns2.mtnonline.rw
41.186.15 ns1.mtnonline.rw
41.186.15 ns2.mtnonline.rw
41.186.16 ns1.mtnonline.rw
41.186.16 ns2.mtnonline.rw
41.186.17 ns1.mtnonline.rw
41.186.17 ns2.mtnonline.rw
41.186.18 ns1.mtnonline.rw
41.186.18 ns2.mtnonline.rw
41.186.19 ns1.mtnonline.rw
41.186.19 ns2.mtnonline.rw
41.186.20 ns1.mtnonline.rw
41.186.20 ns2.mtnonline.rw
41.1.136 ns1.vodacombusiness.co.za
41.1.136 ns2.vodacombusiness.co.za
41.248.248 dns.menara.ma
41.248.248 dns1.menara.ma
41.251.255 dns.menara.ma
41.251.255 dns1.menara.ma
41.251.254 dns.menara.ma
41.251.254 dns1.menara.ma
41.251.250 dns.menara.ma
41.251.250 dns1.menara.ma
41.192.255 ns01.socialcode.biz
41.192.255 ns02.socialcode.biz
41.94.0 ns1.morenet.ac.mz
41.94.0 zebra.uem.mz
41.94.10 ns1.morenet.ac.mz
41.94.10 zebra.uem.mz
41.94.8 ns1.morenet.ac.mz
41.94.8 zebra.uem.mz
196.25.146 igubu.saix.net
196.25.146 sangoma.saix.net
196.25.146 induna.saix.net
196.25.146 sabela.saix.net
196.25.147 igubu.saix.net
196.25.147 sangoma.saix.net
196.25.147 induna.saix.net
196.25.147 sabela.saix.net
197.235.1 ns1.vm.co.mz
197.235.1 ns2.vm.co.mz
41.186.24 ns1.mtnonline.rw
41.186.24 ns2.mtnonline.rw
41.186.22 ns1.mtnonline.rw
41.186.22 ns2.mtnonline.rw
41.186.36 ns1.mtnonline.rw
41.186.36 ns2.mtnonline.rw
41.186.44 ns1.mtnonline.rw
41.186.44 ns1.mtnonline.rw
41.231.7 ns1.atlax.com
41.231.7 ns2.atlax.com
41.231.7 ns3.atlax.com
41.248.226 dns.menara.ma
41.248.226 dns1.menara.ma
154.120.192 217.15.112.171
154.120.192 217.15.112.170
196.49.3 196.49.3.11
41.60.1 auth1.liquidtelecom.com
41.60.1 auth2.liquidtelecom.com
41.60.10 dns1.realtime.zm
41.60.10 dns2.realtime.zm
41.60.10 dns3.realtime.zm
41.60.10 dns4.realtime.zm
41.60.14 auth1.liquidtelecom.com
41.60.14 auth2.liquidtelecom.com
41.60.129 auth1.liquidtelecom.com
41.60.129 auth2.liquidtelecom.com
41.60.130 auth1.liquidtelecom.com
41.60.130 auth2.liquidtelecom.com
105.255.128 ns1.vodacombusiness.co.za
105.255.128 ns2.vodacombusiness.co.za
105.255.209 ns1.vodacombusiness.co.za
105.255.209 ns2.vodacombusiness.co.za
105.255.127 ns1.vodacombusiness.co.za
105.255.127 ns2.vodacombusiness.co.za
105.255.130 ns1.vodacombusiness.co.za
105.255.130 ns21.vodacombusiness.co.za
105.255.131 ns1.vodacombusiness.co.za
105.255.131 ns2.vodacombusiness.co.za
105.255.132 ns1.vodacombusiness.co.za
105.255.132 ns2.vodacombusiness.co.za
105.255.133 ns1.vodacombusiness.co.za
105.255.133 ns2.vodacombusiness.co.za
105.255.134 ns1.vodacombusiness.co.za
105.255.134 ns2.vodacombusiness.co.za
105.255.135 ns1.vodacombusiness.co.za
105.255.135 ns2.vodacombusiness.co.za
105.255.136 ns1.vodacombusiness.co.za
105.255.136 ns2.vodacombusiness.co.za
105.255.137 ns1.vodacombusiness.co.za
105.255.137 ns2.vodacombusiness.co.za
105.255.138 ns1.vodacombusiness.co.za
105.255.138 ns2.vodacombusiness.co.za
105.255.141 ns1.vodacombusiness.co.za
105.255.141 ns2.vodacombusiness.co.za
105.255.145 ns1.vodacombusiness.co.za
105.255.145 ns2.vodacombusiness.co.za
105.255.152 ns1.vodacombusiness.co.za
105.255.152 ns2.vodacombusiness.co.za
105.255.153 ns1.vodacombusiness.co.za
105.255.153 ns2.vodacombusiness.co.za
105.255.165 ns1.vodacombusiness.co.za
105.255.165 ns2.vodacombusiness.co.za
105.255.192 ns1.vodacombusiness.co.za
105.255.192 ns2.vodacombusiness.co.za
105.255.216 ns1.vodacombusiness.co.za
105.255.216 ns2.vodacombusiness.co.za
105.255.217 ns1.vodacombusiness.co.za
105.255.217 ns2.vodacombusiness.co.za
105.255.237 ns1.vodacombusiness.co.za
105.255.237 ns2.vodacombusiness.co.za
105.255.146 ns1.vodacombusiness.co.za
105.255.146 ns2.vodacombusiness.co.za
105.255.129 ns1.vodacombusiness.co.za
105.255.129 ns2.vodacombusiness.co.za
105.255.139 ns1.vodacombusiness.co.za
105.255.139 ns2.vodacombusiness.co.za
105.255.140 ns1.vodacombusiness.co.za
105.255.140 ns2.vodacombusiness.co.za
105.255.142 ns1.vodacombusiness.co.za
105.255.142 ns2.vodacombusiness.co.za
105.255.143 ns1.vodacombusiness.co.za
105.255.143 ns2.vodacombusiness.co.za
105.255.144 ns1.vodacombusiness.co.za
105.255.144 ns2.vodacombusiness.co.za
105.255.147 ns1.vodacombusiness.co.za
105.255.147 ns2.vodacombusiness.co.za
105.255.148 ns1.vodacombusiness.co.za
105.255.148 ns2.vodacombusiness.co.za
105.255.149 ns1.vodacombusiness.co.za
105.255.149 ns2.vodacombusiness.co.za
105.255.150 ns1.vodacombusiness.co.za
105.255.150 ns2.vodacombusiness.co.za
105.255.151 ns1.vodacombusiness.co.za
105.255.151 ns2.vodacombusiness.co.za
105.255.154 ns1.vodacombusiness.co.za
105.255.154 ns2.vodacombusiness.co.za
105.255.155 ns1.vodacombusiness.co.za
105.255.155 ns2.vodacombusiness.co.za
105.255.160 ns1.vodacombusiness.co.za
105.255.160 ns2.vodacombusiness.co.za
105.255.161 ns1.vodacombusiness.co.za
105.255.161 ns2.vodacombusiness.co.za
105.255.164 ns1.vodacombusiness.co.za
105.255.164 ns2.vodacombusiness.co.za
105.255.176 ns1.vodacombusiness.co.za
105.255.176 ns2.vodacombusiness.co.za
105.255.177 ns1.vodacombusiness.co.za
105.255.177 ns2.vodacombusiness.co.za
105.255.184 ns1.vodacombusiness.co.za
105.255.184 ns2.vodacombusiness.co.za
105.255.193 ns1.vodacombusiness.co.za
105.255.193 ns2.vodacombusiness.co.za
105.255.194 ns1.vodacombusiness.co.za
105.255.194 ns2.vodacombusiness.co.za
105.255.195 ns1.vodacombusiness.co.za
105.255.195 ns2.vodacombusiness.co.za
105.255.200 ns1.vodacombusiness.co.za
105.255.200 ns2.vodacombusiness.co.za
105.255.206 ns1.vodacombusiness.co.za
105.255.206 ns2.vodacombusiness.co.za
105.255.208 ns1.vodacombusiness.co.za
105.255.208 ns2.vodacombusiness.co.za
105.255.218 ns1.vodacombusiness.co.za
105.255.218 ns2.vodacombusiness.co.za
105.255.219 ns1.vodacombusiness.co.za
105.255.219 ns2.vodacombusiness.co.za
129.205.80 41.161.16.132
129.205.80 41.160.80.8
129.205.81 41.161.16.132
129.205.81 41.160.80.8
41.60.131 auth1.liquidtelecom.com
41.60.131 auth2.liquidtelecom.com
41.60.22 auth1.liquidtelecom.com
41.60.22 auth2.liquidtelecom.com
41.60.230 auth1.liquidtelecom.com
41.60.230 auth2.liquidtelecom.com
41.60.3 auth1.liquidtelecom.com
41.60.3 auth2.liquidtelecom.com
41.60.231 ns1.liquidtelecom.net
41.60.231 ns2.liquidtelecom.net
41.60.137 ns1.liquidtelecom.net
41.60.137 ns2.liquidtelecom.net
41.60.208 ns1.liquidtelecom.net
41.60.208 ns2.liquidtelecom.net
41.60.209 ns1.liquidtelecom.net
41.60.209 ns2.liquidtelecom.net
41.60.210 ns1.liquidtelecom.net
41.60.210 ns2.liquidtelecom.net
41.60.211 ns1.liquidtelecom.net
41.60.211 ns2.liquidtelecom.net
41.60.212 ns1.liquidtelecom.net
41.60.212 ns2.liquidtelecom.net
41.60.213 ns1.liquidtelecom.net
41.60.213 ns2.liquidtelecom.net
41.60.214 ns1.liquidtelecom.net
41.60.214 ns2.liquidtelecom.net
41.60.215 ns1.liquidtelecom.net
41.60.215 ns2.liquidtelecom.net
41.60.216 ns1.liquidtelecom.net
41.60.216 ns2.liquidtelecom.net
41.60.217 ns1.liquidtelecom.net
41.60.217 ns2.liquidtelecom.net
41.60.218 ns1.liquidtelecom.net
41.60.218 ns2.liquidtelecom.net
41.60.219 ns1.liquidtelecom.net
41.60.219 ns2.liquidtelecom.net
41.60.220 ns1.liquidtelecom.net
41.60.220 ns2.liquidtelecom.net
41.60.221 ns1.liquidtelecom.net
41.60.221 ns2.liquidtelecom.net
41.60.222 ns1.liquidtelecom.net
41.60.222 ns2.liquidtelecom.net
41.60.223 ns1.liquidtelecom.net
41.60.223 ns2.liquidtelecom.net
41.60.224 ns1.liquidtelecom.net
41.60.224 ns2.liquidtelecom.net
41.60.200 ns1.liquidtelecom.co.zw
41.60.200 ns2.liquidtelecom.co.zw
41.60.200 ns3.liquidtelecom.co.zw
41.60.200 ns4.liquidtelecom.com
41.60.201 ns1.liquidtelecom.co.zw
41.60.201 ns2.liquidtelecom.co.zw
41.60.201 ns3.liquidtelecom.co.zw
41.60.201 ns4.liquidtelecom.com
41.60.202 ns1.liquidtelecom.co.zw
41.60.202 ns2.liquidtelecom.co.zw
41.60.202 ns3.liquidtelecom.co.zw
41.60.202 ns4.liquidtelecom.com
41.60.203 ns1.liquidtelecom.co.zw
41.60.203 ns2.liquidtelecom.co.zw
41.60.203 ns3.liquidtelecom.co.zw
41.60.203 ns4.liquidtelecom.com
41.60.204 ns1.liquidtelecom.co.zw
41.60.204 ns2.liquidtelecom.co.zw
41.60.204 ns3.liquidtelecom.co.zw
41.60.204 ns4.liquidtelecom.com
41.60.205 ns1.liquidtelecom.co.zw
41.60.205 ns2.liquidtelecom.co.zw
41.60.205 ns3.liquidtelecom.co.zw
41.60.205 ns4.liquidtelecom.com
41.60.206 ns1.liquidtelecom.co.zw
41.60.206 ns2.liquidtelecom.co.zw
41.60.206 ns3.liquidtelecom.co.zw
41.60.206 ns4.liquidtelecom.com
41.60.207 ns1.liquidtelecom.co.zw
41.60.207 ns2.liquidtelecom.co.zw
41.60.207 ns3.liquidtelecom.co.zw
41.60.207 ns4.liquidtelecom.com
105.234.0 ns1.airtel.africa
105.234.0 ns2.airtel.africa
41.60.188 ns1.liquidtelecom.net
41.60.188 ns2.liquidtelecom.net
196.179.252 ns.tunet.tn
196.179.252 ns2.tunet.tn
41.60.228 ns1.liquidtelecom.net
41.60.228 ns2.liquidtelecom.net
196.201.11 ns1.rcswimax.com
196.201.11 ns2.rcswimax.com
154.73.4 154.73.6.242
154.73.4 196.6.111.242
41.1.51 dnsinfo1-cte-pt.3g.vodacom.co.za
41.1.51 dnsinfo1-dne-pt.3g.vodacom.co.za
41.1.51 dnsinfo1-mtp-pt.3g.vodacom.co.za
41.1.51 dnsinfo1-psi-pt.3g.vodacom.co.za
41.1.51 dnsinfo1-cfo.3g.vodacom.co.za
41.1.51 dnsinfo1-dmo.3g.vodacom.co.za
41.1.51 dnsinfo1-mdp.3g.vodacom.co.za
41.1.51 dnsinfo1-prs.3g.vodacom.co.za
41.1.114 dnsinfo1-cte-pt.3g.vodacom.co.za
41.1.114 dnsinfo1-dne-pt.3g.vodacom.co.za
41.1.114 dnsinfo1-mtp-pt.3g.vodacom.co.za
41.1.114 dnsinfo1-psi-pt.3g.vodacom.co.za
41.1.114 dnsinfo1-cfo.3g.vodacom.co.za
41.1.114 dnsinfo1-dmo.3g.vodacom.co.za
41.1.114 dnsinfo1-mdp.3g.vodacom.co.za
41.1.114 dnsinfo1-prs.3g.vodacom.co.za
41.1.47 dnsinfo1-cte-pt.3g.vodacom.co.za
41.1.47 dnsinfo1-dne-pt.3g.vodacom.co.za
41.1.47 dnsinfo1-mtp-pt.3g.vodacom.co.za
41.1.47 dnsinfo1-psi-pt.3g.vodacom.co.za
41.1.47 dnsinfo1-cfo.3g.vodacom.co.za
41.1.47 dnsinfo1-dmo.3g.vodacom.co.za
41.1.47 dnsinfo1-mdp.3g.vodacom.co.za
41.1.47 dnsinfo1-prs.3g.vodacom.co.za
41.1.111 dnsinfo1-cte-pt.3g.vodacom.co.za
41.1.111 dnsinfo1-dne-pt.3g.vodacom.co.za
41.1.111 dnsinfo1-mtp-pt.3g.vodacom.co.za
41.1.111 dnsinfo1-psi-pt.3g.vodacom.co.za
41.1.111 dnsinfo1-cfo.3g.vodacom.co.za
41.1.111 dnsinfo1-dmo.3g.vodacom.co.za
41.1.111 dnsinfo1-mdp.3g.vodacom.co.za
41.1.111 dnsinfo1-prs.3g.vodacom.co.za
41.1.161 dnsinfo1-cte-pt.3g.vodacom.co.za
41.1.161 dnsinfo1-dne-pt.3g.vodacom.co.za
41.1.161 dnsinfo1-mtp-pt.3g.vodacom.co.za
41.1.161 dnsinfo1-psi-pt.3g.vodacom.co.za
41.1.161 dnsinfo1-cfo.3g.vodacom.co.za
41.1.161 dnsinfo1-dmo.3g.vodacom.co.za
41.1.161 dnsinfo1-mdp.3g.vodacom.co.za
41.1.161 dnsinfo1-prs.3g.vodacom.co.za
41.1.239 dnsinfo1-cte-pt.3g.vodacom.co.za
41.1.239 dnsinfo1-dne-pt.3g.vodacom.co.za
41.1.239 dnsinfo1-mtp-pt.3g.vodacom.co.za
41.1.239 dnsinfo1-psi-pt.3g.vodacom.co.za
41.1.239 dnsinfo1-cfo.3g.vodacom.co.za
41.1.239 dnsinfo1-dmo.3g.vodacom.co.za
41.1.239 dnsinfo1-mdp.3g.vodacom.co.za
41.1.239 dnsinfo1-prs.3g.vodacom.co.za
41.1.176 dnsinfo1-cte-pt.3g.vodacom.co.za
41.1.176 dnsinfo1-dne-pt.3g.vodacom.co.za
41.1.176 dnsinfo1-mtp-pt.3g.vodacom.co.za
41.1.176 dnsinfo1-psi-pt.3g.vodacom.co.za
41.1.176 dnsinfo1-cfo.3g.vodacom.co.za
41.1.176 dnsinfo1-dmo.3g.vodacom.co.za
41.1.176 dnsinfo1-mdp.3g.vodacom.co.za
41.1.176 dnsinfo1-prs.3g.vodacom.co.za
41.1.240 dnsinfo1-cte-pt.3g.vodacom.co.za
41.1.240 dnsinfo1-dne-pt.3g.vodacom.co.za
41.1.240 dnsinfo1-mtp-pt.3g.vodacom.co.za
41.1.240 dnsinfo1-psi-pt.3g.vodacom.co.za
41.1.240 dnsinfo1-cfo.3g.vodacom.co.za
41.1.240 dnsinfo1-dmo.3g.vodacom.co.za
41.1.240 dnsinfo1-mdp.3g.vodacom.co.za
41.1.240 dnsinfo1-prs.3g.vodacom.co.za
197.231.251 ns2
196.201.8 ns1.rcswimax.com
196.201.8 ns2.rcswimax.com
196.201.9 ns1.rcswimax.com
196.201.9 ns2.rcswimax.com
196.201.10 ns1.rcswimax.com
196.201.10 ns2.rcswimax.com
197.231.248 ns3



From geier at geier.ne.tz  Thu Nov  5 16:39:41 2020
From: geier at geier.ne.tz (Frank Habicht)
Date: Thu, 5 Nov 2020 19:39:41 +0300
Subject: [Community-Discuss] Yet more data base problems/inconsistancies
In-Reply-To: <31455.1604588424@segfault.tristatelogic.com>
References: <31455.1604588424@segfault.tristatelogic.com>
Message-ID: <d3e5bb88-f09c-3eba-188f-e0ebb8107f94@geier.ne.tz>

Hi Ronald,

in the file i found:
; Source AFRINIC
203.196.in-addr.arpa.         NS        ns1.ati.tn.
203.196.in-addr.arpa.         NS        ns2.ati.tn.

if there is a delegation for the "/16 equivalent" then one can't create
a delegation for an enclosed "/24 equivalent" zone. [1]

So probably the
> domain:         35.203.196.in-addr.arpa
object shouldn't have been allowed to be created / imported from RIPE...

Frank

[1]
see Randy on RIPE-DB recently


On 05/11/2020 18:00, Ronald F. Guilmette wrote:
> In addition to the problem I have just posted about i.e. the problem of
> dublicate (and inconsistant) records in the WHOIS describing various
> reverse DNS delegations, I am also seeing something else that I did not
> anticipate, i.e. reverse DNS delegation records that are present within
> the WHOIS data base, but which, for no very obvious reason, are *not*
> also represented within the set of zone files present within the
> ftp://ftp.afrinic.net/pub/zones/ directory.
> 
> I here provide one example:
> 
> domain:         35.203.196.in-addr.arpa
> descr:          reverse delagation for the
> descr:          HEXABYTE-10 dial-UP elmanzah
> org:            ORG-ATIA2-AFRINIC
> admin-c:        PA1317-AFRINIC
> tech-c:         LD822-AFRINIC
> zone-c:         LD822-AFRINIC
> nserver:        ns1.hexabyte.tn
> nserver:        ns2.hexabyte.tn
> remarks:        data has been transferred from RIPE Whois Database 20050221
> notify:         ***@ati.tn
> mnt-by:         ATI-MNT
> mnt-lower:      ATI-MNT
> changed:        ***@ati.tn 20040322
> changed:        ***@afrinic.net 20050221
> changed:        ***@ati.tn 20140520
> changed:        ***@ati.tn 20181023
> source:         AFRINIC
> 
> The above reverse DNS delegation record in in the WHOIS data base but it
> appears to me that it has no corresponding counterpart within this file:
> 
> ftp://ftp.afrinic.net/pub/zones/196.in-addr.arpa-AFRINIC
> 
> So, either this is due to some misunderstanding I am having regarding
> what shiould be persent in that zone file, or else that zone file is
> incomplete.
> 
> I am looking forward to having someone in authority tell me which is
> actually the case.
> 
> If in fact a record describing the delegation shown above should in fact
> be represented within the zone file, and if it is improperly missing
> from that file, then it would seem to have a LOT of company.   In fact,
> the entire list below of some 1,952 specific delegations are all mentioned
> within the WHOIS data base but as far as I can tell, none of them are
> mentioned within the file in the ftp://ftp.afrinic.net/pub/zones/ directory.
> 
> 
> 196.203.0 ns4.ati.tn
> 196.203.0 ns6.ati.tn
> 217.52.0 ns.aucegypt.edu
> 217.52.0 ns3.aucegypt.edu
> 196.203.1 ns4.ati.tn
> 196.203.1 ns6.ati.tn
> 217.52.1 ns.aucegypt.edu
> 217.52.1 ns3.aucegypt.edu
> 62.139.104 ns1.nile-online.net
> 62.139.104 ns2.nile-online.net
> 62.139.105 ns1.nile-online.net
> 62.139.105 ns2.nile-online.net
> 62.139.109 ns1.nile-online.net
> 62.139.109 ns2.nile-online.net
> 62.139.130 ns1.nile-online.net
> 62.139.130 ns2.nile-online.net
> 196.203.2 ns4.ati.tn
> 196.203.2 ns6.ati.tn
> 217.52.2 ns.aucegypt.edu
> 217.52.2 ns3.aucegypt.edu
> 62.139.253 ns2.egynet.com.eg
> 62.139.253 ns22.egynet.com.eg
> 217.52.3 ns.aucegypt.edu
> 217.52.3 ns3.aucegypt.edu
> 196.203.32 ns4.ati.tn
> 196.203.32 ns6.ati.tn
> 196.203.33 ns4.ati.tn
> 196.203.33 ns6.ati.tn
> 196.203.34 ns4.ati.tn
> 196.203.34 ns6.ati.tn
> 196.203.35 ns1.hexabyte.tn
> 196.203.35 ns2.hexabyte.tn
> 196.203.36 ns4.ati.tn
> 196.203.36 ns6.ati.tn
> 217.52.4 ns.aucegypt.edu
> 217.52.4 ns3.aucegypt.edu
> 217.52.5 ns.aucegypt.edu
> 217.52.5 ns3.aucegypt.edu
> 217.52.6 ns.aucegypt.edu
> 217.52.6 ns3.aucegypt.edu
> 217.52.7 ns.aucegypt.edu
> 217.52.7 ns3.aucegypt.edu
> 217.52.8 ns.aucegypt.edu
> 217.52.8 ns3.aucegypt.edu
> 196.205.11 ns1.link.net
> 196.205.11 ns2.link.net
> 212.0.159 sun1.sudatel.net
> 212.0.148 ns1.sudanmail.net
> 212.0.148 ns2.sudanmail.net
> 212.0.129 main.sdn-mobitel.com
> 212.0.129 main.sdn-mobinet.net
> 196.202.144 ns1.sudacom.net
> 196.202.144 ns2.sudacom.net
> 196.202.145 ns1.sudacom.net
> 196.202.145 ns2.sudacom.net
> 212.0.138 sun1.sudanet.net
> 212.0.146 sun1.sudanet.net
> 163.196 ns1.qdata.net
> 163.196 ns2.qdata.net
> 196.25.226 igubu.saix.net
> 196.25.226 sangoma.saix.net
> 196.205.177 ns1.link.net
> 196.205.177 ns2.link.net
> 196.205.0 ns1.link.net
> 196.205.0 ns2.link.net
> 196.205.1 ns1.link.net
> 196.205.1 ns2.link.net
> 196.205.2 ns1.link.net
> 196.205.2 ns2.link.net
> 196.205.3 ns1.link.net
> 196.205.3 ns2.link.net
> 196.205.4 ns1.link.net
> 196.205.4 ns2.link.net
> 196.205.5 ns1.link.net
> 196.205.5 ns2.link.net
> 196.205.6 ns1.link.net
> 196.205.6 ns2.link.net
> 196.205.7 ns1.link.net
> 196.205.7 ns2.link.net
> 196.205.8 ns1.link.net
> 196.205.8 ns2.link.net
> 196.205.9 ns1.link.net
> 196.205.9 ns2.link.net
> 196.205.10 ns1.link.net
> 196.205.10 ns2.link.net
> 196.205.12 ns1.link.net
> 196.205.12 ns2.link.net
> 196.205.13 ns1.link.net
> 196.205.13 ns2.link.net
> 196.205.14 ns1.link.net
> 196.205.14 ns2.link.net
> 196.205.15 ns1.link.net
> 196.205.15 ns2.link.net
> 196.205.16 ns1.link.net
> 196.205.16 ns2.link.net
> 196.205.17 ns1.link.net
> 196.205.17 ns2.link.net
> 196.205.18 ns1.link.net
> 196.205.18 ns2.link.net
> 196.205.19 ns1.link.net
> 196.205.19 ns2.link.net
> 196.205.20 ns1.link.net
> 196.205.20 ns2.link.net
> 196.205.21 ns1.link.net
> 196.205.21 ns2.link.net
> 196.205.22 ns1.link.net
> 196.205.22 ns2.link.net
> 196.205.23 ns1.link.net
> 196.205.23 ns2.link.net
> 196.205.24 ns1.link.net
> 196.205.24 ns2.link.net
> 196.205.25 ns1.link.net
> 196.205.25 ns2.link.net
> 196.205.26 ns1.link.net
> 196.205.26 ns2.link.net
> 196.205.27 ns1.link.net
> 196.205.27 ns2.link.net
> 196.205.28 ns1.link.net
> 196.205.28 ns2.link.net
> 196.205.29 ns1.link.net
> 196.205.29 ns2.link.net
> 196.205.30 ns1.link.net
> 196.205.30 ns2.link.net
> 196.205.31 ns1.link.net
> 196.205.31 ns2.link.net
> 196.205.32 ns1.link.net
> 196.205.32 ns2.link.net
> 196.205.33 ns1.link.net
> 196.205.33 ns2.link.net
> 196.205.34 ns1.link.net
> 196.205.34 ns2.link.net
> 196.205.36 ns1.link.net
> 196.205.36 ns2.link.net
> 196.205.37 ns1.link.net
> 196.205.37 ns2.link.net
> 196.205.38 ns1.link.net
> 196.205.38 ns2.link.net
> 196.205.39 ns1.link.net
> 196.205.39 ns2.link.net
> 196.205.40 ns1.link.net
> 196.205.40 ns2.link.net
> 196.205.35 ns1.link.net
> 196.205.35 ns2.link.net
> 196.205.55 ns1.link.net
> 196.205.55 ns2.link.net
> 196.205.43 ns1.link.net
> 196.205.43 ns2.link.net
> 196.205.60 ns1.link.net
> 196.205.60 ns2.link.net
> 196.205.49 ns1.link.net
> 196.205.49 ns2.link.net
> 196.205.44 ns1.link.net
> 196.205.44 ns2.link.net
> 196.205.46 ns1.link.net
> 196.205.46 ns2.link.net
> 196.205.52 ns1.link.net
> 196.205.52 ns2.link.net
> 196.205.53 ns1.link.net
> 196.205.53 ns2.link.net
> 196.205.50 ns1.link.net
> 196.205.50 ns2.link.net
> 196.205.51 ns1.link.net
> 196.205.51 ns2.link.net
> 196.205.59 ns1.link.net
> 196.205.59 ns2.link.net
> 196.205.47 ns1.link.net
> 196.205.47 ns2.link.net
> 196.205.48 ns1.link.net
> 196.205.48 ns2.link.net
> 196.205.56 ns1.link.net
> 196.205.56 ns2.link.net
> 196.205.45 ns1.link.net
> 196.205.45 ns2.link.net
> 196.205.42 ns1.link.net
> 196.205.42 ns2.link.net
> 196.205.58 ns1.link.net
> 196.205.58 ns2.link.net
> 196.205.54 ns1.link.net
> 196.205.54 ns2.link.net
> 196.205.41 ns1.link.net
> 196.205.41 ns2.link.net
> 196.205.57 ns1.link.net
> 196.205.57 ns2.link.net
> 196.205.61 ns1.link.net
> 196.205.61 ns2.link.net
> 196.205.62 ns1.link.net
> 196.205.62 ns2.link.net
> 196.205.63 ns1.link.net
> 196.205.63 ns2.link.net
> 196.205.64 ns1.link.net
> 196.205.64 ns2.link.net
> 196.205.65 ns1.link.net
> 196.205.65 ns2.link.net
> 196.205.66 ns1.link.net
> 196.205.66 ns2.link.net
> 196.205.67 ns1.link.net
> 196.205.67 ns2.link.net
> 196.205.68 ns1.link.net
> 196.205.68 ns2.link.net
> 196.205.69 ns1.link.net
> 196.205.69 ns2.link.net
> 196.205.70 ns1.link.net
> 196.205.70 ns2.link.net
> 196.205.71 ns1.link.net
> 196.205.71 ns2.link.net
> 196.205.72 ns1.link.net
> 196.205.72 ns2.link.net
> 196.205.74 ns1.link.net
> 196.205.74 ns2.link.net
> 196.205.77 ns1.link.net
> 196.205.77 ns2.link.net
> 196.205.78 ns1.link.net
> 196.205.78 ns2.link.net
> 196.205.79 ns1.link.net
> 196.205.79 ns2.link.net
> 196.205.73 ns1.link.net
> 196.205.73 ns2.link.net
> 196.205.75 ns1.link.net
> 196.205.75 ns2.link.net
> 196.205.82 ns1.link.net
> 196.205.82 ns2.link.net
> 196.205.76 ns1.link.net
> 196.205.76 ns2.link.net
> 196.205.80 ns1.link.net
> 196.205.80 ns2.link.net
> 196.205.81 ns1.link.net
> 196.205.81 ns2.link.net
> 196.205.83 ns1.link.net
> 196.205.83 ns2.link.net
> 196.205.84 ns1.link.net
> 196.205.84 ns2.link.net
> 196.205.85 ns1.link.net
> 196.205.85 ns2.link.net
> 196.205.86 ns1.link.net
> 196.205.86 ns2.link.net
> 196.205.87 ns1.link.net
> 196.205.87 ns2.link.net
> 196.205.88 ns1.link.net
> 196.205.88 ns2.link.net
> 196.205.89 ns1.link.net
> 196.205.89 ns2.link.net
> 196.205.90 ns1.link.net
> 196.205.90 ns2.link.net
> 196.205.91 ns1.link.net
> 196.205.91 ns2.link.net
> 196.205.92 ns1.link.net
> 196.205.92 ns2.link.net
> 196.205.93 ns1.link.net
> 196.205.93 ns2.link.net
> 196.205.94 ns1.link.net
> 196.205.94 ns2.link.net
> 196.205.95 ns1.link.net
> 196.205.95 ns2.link.net
> 196.205.96 ns1.link.net
> 196.205.96 ns2.link.net
> 196.205.97 ns1.link.net
> 196.205.97 ns2.link.net
> 196.205.98 ns1.link.net
> 196.205.98 ns2.link.net
> 196.205.99 ns1.link.net
> 196.205.99 ns2.link.net
> 196.205.100 ns1.link.net
> 196.205.100 ns2.link.net
> 196.205.101 ns1.link.net
> 196.205.101 ns2.link.net
> 196.205.102 ns1.link.net
> 196.205.102 ns2.link.net
> 196.205.103 ns1.link.net
> 196.205.103 ns2.link.net
> 196.205.104 ns1.link.net
> 196.205.104 ns2.link.net
> 196.205.105 ns1.link.net
> 196.205.105 ns2.link.net
> 196.205.106 ns1.link.net
> 196.205.106 ns2.link.net
> 196.205.107 ns1.link.net
> 196.205.107 ns2.link.net
> 196.205.108 ns1.link.net
> 196.205.108 ns2.link.net
> 196.205.109 ns1.link.net
> 196.205.109 ns2.link.net
> 196.205.110 ns1.link.net
> 196.205.110 ns2.link.net
> 196.205.111 ns1.link.net
> 196.205.111 ns2.link.net
> 196.205.112 ns1.link.net
> 196.205.112 ns2.link.net
> 196.205.113 ns1.link.net
> 196.205.113 ns2.link.net
> 196.205.115 ns1.link.net
> 196.205.115 ns2.link.net
> 196.205.116 ns1.link.net
> 196.205.116 ns2.link.net
> 196.205.114 ns1.link.net
> 196.205.114 ns2.link.net
> 196.205.117 ns1.link.net
> 196.205.117 ns2.link.net
> 196.205.118 ns1.link.net
> 196.205.118 ns2.link.net
> 196.205.119 ns1.link.net
> 196.205.119 ns2.link.net
> 196.205.120 ns1.link.net
> 196.205.120 ns2.link.net
> 196.205.121 ns1.link.net
> 196.205.121 ns2.link.net
> 196.205.122 ns1.link.net
> 196.205.122 ns2.link.net
> 196.205.123 ns1.link.net
> 196.205.123 ns2.link.net
> 196.205.124 ns1.link.net
> 196.205.124 ns2.link.net
> 196.205.125 ns1.link.net
> 196.205.125 ns2.link.net
> 196.205.126 ns1.link.net
> 196.205.126 ns2.link.net
> 196.205.127 ns1.link.net
> 196.205.127 ns2.link.net
> 196.205.128 ns1.link.net
> 196.205.128 ns2.link.net
> 196.205.129 ns1.link.net
> 196.205.129 ns2.link.net
> 196.205.130 ns1.link.net
> 196.205.130 ns2.link.net
> 196.205.131 ns1.link.net
> 196.205.131 ns2.link.net
> 196.205.132 ns1.link.net
> 196.205.132 ns2.link.net
> 196.205.133 ns1.link.net
> 196.205.133 ns2.link.net
> 196.205.134 ns1.link.net
> 196.205.134 ns2.link.net
> 196.205.135 ns1.link.net
> 196.205.135 ns2.link.net
> 196.205.136 ns1.link.net
> 196.205.136 ns2.link.net
> 196.205.137 ns1.link.net
> 196.205.137 ns2.link.net
> 196.205.138 ns1.link.net
> 196.205.138 ns2.link.net
> 196.205.139 ns1.link.net
> 196.205.139 ns2.link.net
> 196.205.140 ns1.link.net
> 196.205.140 ns2.link.net
> 196.205.141 ns1.link.net
> 196.205.141 ns2.link.net
> 196.205.142 ns1.link.net
> 196.205.142 ns2.link.net
> 196.205.143 ns1.link.net
> 196.205.143 ns2.link.net
> 196.205.144 ns1.link.net
> 196.205.144 ns2.link.net
> 196.205.145 ns1.link.net
> 196.205.145 ns2.link.net
> 196.205.146 ns1.link.net
> 196.205.146 ns2.link.net
> 196.205.147 ns1.link.net
> 196.205.147 ns2.link.net
> 196.205.148 ns1.link.net
> 196.205.148 ns2.link.net
> 196.205.149 ns1.link.net
> 196.205.149 ns2.link.net
> 196.205.150 ns1.link.net
> 196.205.150 ns2.link.net
> 196.205.151 ns1.link.net
> 196.205.151 ns2.link.net
> 196.205.152 ns1.link.net
> 196.205.152 ns2.link.net
> 196.205.153 ns1.link.net
> 196.205.153 ns2.link.net
> 196.205.154 ns1.link.net
> 196.205.154 ns2.link.net
> 196.205.155 ns1.link.net
> 196.205.155 ns2.link.net
> 196.205.156 ns1.link.net
> 196.205.156 ns2.link.net
> 196.205.157 ns1.link.net
> 196.205.157 ns2.link.net
> 196.205.158 ns1.link.net
> 196.205.158 ns2.link.net
> 196.205.159 ns1.link.net
> 196.205.159 ns2.link.net
> 196.205.160 ns1.link.net
> 196.205.160 ns2.link.net
> 196.205.161 ns1.link.net
> 196.205.161 ns2.link.net
> 196.205.162 ns1.link.net
> 196.205.162 ns2.link.net
> 196.205.163 ns1.link.net
> 196.205.163 ns2.link.net
> 196.205.164 ns1.link.net
> 196.205.164 ns2.link.net
> 196.205.165 ns1.link.net
> 196.205.165 ns2.link.net
> 196.205.166 ns1.link.net
> 196.205.166 ns2.link.net
> 196.205.167 ns1.link.net
> 196.205.167 ns2.link.net
> 196.205.168 ns1.link.net
> 196.205.168 ns2.link.net
> 196.205.169 ns1.link.net
> 196.205.169 ns2.link.net
> 196.205.170 ns1.link.net
> 196.205.170 ns2.link.net
> 196.205.172 ns1.link.net
> 196.205.172 ns2.link.net
> 196.205.171 ns1.link.net
> 196.205.171 ns2.link.net
> 196.205.173 ns1.link.net
> 196.205.173 ns2.link.net
> 196.205.174 ns1.link.net
> 196.205.174 ns2.link.net
> 196.205.175 ns1.link.net
> 196.205.175 ns2.link.net
> 196.205.176 ns1.link.net
> 196.205.176 ns2.link.net
> 196.205.178 ns1.link.net
> 196.205.178 ns2.link.net
> 196.205.179 ns1.link.net
> 196.205.179 ns2.link.net
> 196.205.180 ns1.link.net
> 196.205.180 ns2.link.net
> 196.205.181 ns1.link.net
> 196.205.181 ns2.link.net
> 196.205.182 ns1.link.net
> 196.205.182 ns2.link.net
> 196.205.183 ns1.link.net
> 196.205.183 ns2.link.net
> 196.205.184 ns1.link.net
> 196.205.184 ns2.link.net
> 196.205.185 ns1.link.net
> 196.205.185 ns2.link.net
> 196.205.186 ns1.link.net
> 196.205.186 ns2.link.net
> 196.205.187 ns1.link.net
> 196.205.187 ns2.link.net
> 196.205.188 ns1.link.net
> 196.205.188 ns2.link.net
> 196.205.189 ns1.link.net
> 196.205.189 ns2.link.net
> 196.205.190 ns1.link.net
> 196.205.190 ns2.link.net
> 196.205.191 ns1.link.net
> 196.205.191 ns2.link.net
> 196.205.192 ns1.link.net
> 196.205.192 ns2.link.net
> 196.205.193 ns1.link.net
> 196.205.193 ns2.link.net
> 196.205.194 ns1.link.net
> 196.205.194 ns2.link.net
> 196.205.195 ns1.link.net
> 196.205.195 ns2.link.net
> 196.205.196 ns1.link.net
> 196.205.196 ns2.link.net
> 196.205.197 ns1.link.net
> 196.205.197 ns2.link.net
> 196.205.198 ns1.link.net
> 196.205.198 ns2.link.net
> 196.205.199 ns1.link.net
> 196.205.199 ns2.link.net
> 196.205.200 ns1.link.net
> 196.205.200 ns2.link.net
> 196.205.201 ns1.link.net
> 196.205.201 ns2.link.net
> 196.205.202 ns1.link.net
> 196.205.202 ns2.link.net
> 196.205.204 ns1.link.net
> 196.205.204 ns2.link.net
> 196.205.203 ns1.link.net
> 196.205.203 ns2.link.net
> 196.205.205 ns1.link.net
> 196.205.205 ns2.link.net
> 196.205.206 ns1.link.net
> 196.205.206 ns2.link.net
> 196.205.207 ns1.link.net
> 196.205.207 ns2.link.net
> 196.205.208 ns1.link.net
> 196.205.208 ns2.link.net
> 196.205.209 ns1.link.net
> 196.205.209 ns2.link.net
> 196.205.210 ns1.link.net
> 196.205.210 ns2.link.net
> 196.205.211 ns1.link.net
> 196.205.211 ns2.link.net
> 196.205.212 ns1.link.net
> 196.205.212 ns2.link.net
> 196.205.213 ns1.link.net
> 196.205.213 ns2.link.net
> 196.205.214 ns1.link.net
> 196.205.214 ns2.link.net
> 196.205.215 ns1.link.net
> 196.205.215 ns2.link.net
> 196.205.216 ns1.link.net
> 196.205.216 ns2.link.net
> 196.205.217 ns1.link.net
> 196.205.217 ns2.link.net
> 196.205.219 ns1.link.net
> 196.205.219 ns2.link.net
> 196.205.220 ns1.link.net
> 196.205.220 ns2.link.net
> 196.205.221 ns1.link.net
> 196.205.221 ns2.link.net
> 196.205.224 ns1.link.net
> 196.205.224 ns2.link.net
> 196.205.225 ns1.link.net
> 196.205.225 ns2.link.net
> 196.205.218 ns1.link.net
> 196.205.218 ns2.link.net
> 196.205.222 ns1.link.net
> 196.205.222 ns2.link.net
> 196.205.223 ns1.link.net
> 196.205.223 ns2.link.net
> 196.205.227 ns1.link.net
> 196.205.227 ns2.link.net
> 196.205.226 ns1.link.net
> 196.205.226 ns2.link.net
> 196.205.228 ns1.link.net
> 196.205.228 ns2.link.net
> 196.205.229 ns1.link.net
> 196.205.229 ns2.link.net
> 196.205.230 ns1.link.net
> 196.205.230 ns2.link.net
> 196.205.231 ns1.link.net
> 196.205.231 ns2.link.net
> 196.205.232 ns1.link.net
> 196.205.232 ns2.link.net
> 196.205.233 ns1.link.net
> 196.205.233 ns2.link.net
> 196.205.234 ns1.link.net
> 196.205.234 ns2.link.net
> 196.205.235 ns1.link.net
> 196.205.235 ns2.link.net
> 196.205.236 ns1.link.net
> 196.205.236 ns2.link.net
> 196.205.237 ns1.link.net
> 196.205.237 ns2.link.net
> 196.205.238 ns1.link.net
> 196.205.238 ns2.link.net
> 196.205.239 ns1.link.net
> 196.205.239 ns2.link.net
> 196.205.240 ns1.link.net
> 196.205.240 ns2.link.net
> 196.205.241 ns1.link.net
> 196.205.241 ns2.link.net
> 196.205.242 ns1.link.net
> 196.205.242 ns2.link.net
> 196.205.243 ns1.link.net
> 196.205.243 ns2.link.net
> 196.205.244 ns1.link.net
> 196.205.244 ns2.link.net
> 196.205.245 ns1.link.net
> 196.205.245 ns2.link.net
> 196.205.246 ns1.link.net
> 196.205.246 ns2.link.net
> 196.205.247 ns1.link.net
> 196.205.247 ns2.link.net
> 196.205.248 ns1.link.net
> 196.205.248 ns2.link.net
> 196.205.249 ns1.link.net
> 196.205.249 ns2.link.net
> 196.205.250 ns1.link.net
> 196.205.250 ns2.link.net
> 196.205.251 ns1.link.net
> 196.205.251 ns2.link.net
> 196.205.252 ns1.link.net
> 196.205.252 ns2.link.net
> 196.205.253 ns1.link.net
> 196.205.253 ns2.link.net
> 196.205.254 ns1.link.net
> 196.205.254 ns2.link.net
> 196.205.255 ns1.link.net
> 196.205.255 ns2.link.net
> 196.25.240 igubu.saix.net
> 196.25.240 sangoma.saix.net
> 196.25.240 induna.saix.net
> 196.25.240 sabela.saix.net
> 196.33.38 titan.is.co.za
> 196.33.38 demeter.is.co.za
> 196.33.38 jupiter.is.co.za
> 196.206.251 ns1.wanadoo.ma
> 196.206.251 ns2.wanadoo.ma
> 196.206.252 ns1.wanadoo.ma
> 196.206.252 ns2.wanadoo.ma
> 196.217.254 ns1.wanadoo.ma
> 196.217.254 ns2.wanadoo.ma
> 196.217.255 ns1.wanadoo.ma
> 196.217.255 ns2.wanadoo.ma
> 196.217.246 dns.menara.ma
> 196.217.246 dns1.menara.ma
> 196.218.254 ns1.tedata.net.jo
> 196.218.254 ns2.tedata.net.jo
> 41.194.2 ns.seychelles.net
> 41.194.2 ns2.seychelles.net
> 41.194.1 ns.seychelles.net
> 41.194.1 ns2.seychelles.net
> 41.194.3 ns.seychelles.net
> 41.194.3 ns2.seychelles.net
> 41.194.0 ns.seychelles.net
> 41.194.0 ns2.seychelles.net
> 196.206.240 ns1.wanadoo.ma
> 196.206.240 ns2.wanadoo.ma
> 217.52.64 ns1.mist-net.com
> 217.52.64 ns2.mist-net.com
> 217.52.72 ns1.mist-net.com
> 217.52.72 ns2.mist-net.com
> 217.52.26 ns1.mist-net.com
> 217.52.26 ns2.mist-net.com
> 41.249.252 dns.menara.ma
> 41.249.252 dns1.menara.ma
> 41.1.207 ns1.vodacombusiness.co.za
> 41.1.207 ns2.vodacombusiness.co.za
> 41.1.128 ns1.vodacombusiness.co.za
> 41.1.128 ns2.vodacombusiness.co.za
> 41.1.201 ns1.vodacombusiness.co.za
> 41.1.201 ns2.vodacombusiness.co.za
> 41.186.0 ns1.mtnonline.rw
> 41.186.0 ns2.mtnonline.rw
> 41.186.1 ns1.mtnonline.rw
> 41.186.1 ns2.mtnonline.rw
> 41.186.2 ns1.mtnonline.rw
> 41.186.2 ns2.mtnonline.rw
> 41.186.3 ns1.mtnonline.rw
> 41.186.3 ns2.mtnonline.rw
> 41.186.4 ns1.mtnonline.rw
> 41.186.4 ns2.mtnonline.rw
> 41.186.5 ns1.mtnonline.rw
> 41.186.5 ns2.mtnonline.rw
> 41.186.6 ns1.mtnonline.rw
> 41.186.6 ns2.mtnonline.rw
> 41.186.7 ns1.mtnonline.rw
> 41.186.7 ns2.mtnonline.rw
> 41.186.8 ns1.mtnonline.rw
> 41.186.8 ns2.mtnonline.rw
> 41.186.9 ns1.mtnonline.rw
> 41.186.9 ns2.mtnonline.rw
> 41.186.10 ns1.mtnonline.rw
> 41.186.10 ns2.mtnonline.rw
> 41.186.11 ns1.mtnonline.rw
> 41.186.11 ns2.mtnonline.rw
> 41.186.12 ns1.mtnonline.rw
> 41.186.12 ns2.mtnonline.rw
> 41.186.13 ns1.mtnonline.rw
> 41.186.13 ns2.mtnonline.rw
> 41.186.14 ns1.mtnonline.rw
> 41.186.14 ns2.mtnonline.rw
> 41.186.15 ns1.mtnonline.rw
> 41.186.15 ns2.mtnonline.rw
> 41.186.16 ns1.mtnonline.rw
> 41.186.16 ns2.mtnonline.rw
> 41.186.17 ns1.mtnonline.rw
> 41.186.17 ns2.mtnonline.rw
> 41.186.18 ns1.mtnonline.rw
> 41.186.18 ns2.mtnonline.rw
> 41.186.19 ns1.mtnonline.rw
> 41.186.19 ns2.mtnonline.rw
> 41.186.20 ns1.mtnonline.rw
> 41.186.20 ns2.mtnonline.rw
> 41.1.136 ns1.vodacombusiness.co.za
> 41.1.136 ns2.vodacombusiness.co.za
> 41.248.248 dns.menara.ma
> 41.248.248 dns1.menara.ma
> 41.251.255 dns.menara.ma
> 41.251.255 dns1.menara.ma
> 41.251.254 dns.menara.ma
> 41.251.254 dns1.menara.ma
> 41.251.250 dns.menara.ma
> 41.251.250 dns1.menara.ma
> 41.192.255 ns01.socialcode.biz
> 41.192.255 ns02.socialcode.biz
> 41.94.0 ns1.morenet.ac.mz
> 41.94.0 zebra.uem.mz
> 41.94.10 ns1.morenet.ac.mz
> 41.94.10 zebra.uem.mz
> 41.94.8 ns1.morenet.ac.mz
> 41.94.8 zebra.uem.mz
> 196.25.146 igubu.saix.net
> 196.25.146 sangoma.saix.net
> 196.25.146 induna.saix.net
> 196.25.146 sabela.saix.net
> 196.25.147 igubu.saix.net
> 196.25.147 sangoma.saix.net
> 196.25.147 induna.saix.net
> 196.25.147 sabela.saix.net
> 197.235.1 ns1.vm.co.mz
> 197.235.1 ns2.vm.co.mz
> 41.186.24 ns1.mtnonline.rw
> 41.186.24 ns2.mtnonline.rw
> 41.186.22 ns1.mtnonline.rw
> 41.186.22 ns2.mtnonline.rw
> 41.186.36 ns1.mtnonline.rw
> 41.186.36 ns2.mtnonline.rw
> 41.186.44 ns1.mtnonline.rw
> 41.186.44 ns1.mtnonline.rw
> 41.231.7 ns1.atlax.com
> 41.231.7 ns2.atlax.com
> 41.231.7 ns3.atlax.com
> 41.248.226 dns.menara.ma
> 41.248.226 dns1.menara.ma
> 154.120.192 217.15.112.171
> 154.120.192 217.15.112.170
> 196.49.3 196.49.3.11
> 41.60.1 auth1.liquidtelecom.com
> 41.60.1 auth2.liquidtelecom.com
> 41.60.10 dns1.realtime.zm
> 41.60.10 dns2.realtime.zm
> 41.60.10 dns3.realtime.zm
> 41.60.10 dns4.realtime.zm
> 41.60.14 auth1.liquidtelecom.com
> 41.60.14 auth2.liquidtelecom.com
> 41.60.129 auth1.liquidtelecom.com
> 41.60.129 auth2.liquidtelecom.com
> 41.60.130 auth1.liquidtelecom.com
> 41.60.130 auth2.liquidtelecom.com
> 105.255.128 ns1.vodacombusiness.co.za
> 105.255.128 ns2.vodacombusiness.co.za
> 105.255.209 ns1.vodacombusiness.co.za
> 105.255.209 ns2.vodacombusiness.co.za
> 105.255.127 ns1.vodacombusiness.co.za
> 105.255.127 ns2.vodacombusiness.co.za
> 105.255.130 ns1.vodacombusiness.co.za
> 105.255.130 ns21.vodacombusiness.co.za
> 105.255.131 ns1.vodacombusiness.co.za
> 105.255.131 ns2.vodacombusiness.co.za
> 105.255.132 ns1.vodacombusiness.co.za
> 105.255.132 ns2.vodacombusiness.co.za
> 105.255.133 ns1.vodacombusiness.co.za
> 105.255.133 ns2.vodacombusiness.co.za
> 105.255.134 ns1.vodacombusiness.co.za
> 105.255.134 ns2.vodacombusiness.co.za
> 105.255.135 ns1.vodacombusiness.co.za
> 105.255.135 ns2.vodacombusiness.co.za
> 105.255.136 ns1.vodacombusiness.co.za
> 105.255.136 ns2.vodacombusiness.co.za
> 105.255.137 ns1.vodacombusiness.co.za
> 105.255.137 ns2.vodacombusiness.co.za
> 105.255.138 ns1.vodacombusiness.co.za
> 105.255.138 ns2.vodacombusiness.co.za
> 105.255.141 ns1.vodacombusiness.co.za
> 105.255.141 ns2.vodacombusiness.co.za
> 105.255.145 ns1.vodacombusiness.co.za
> 105.255.145 ns2.vodacombusiness.co.za
> 105.255.152 ns1.vodacombusiness.co.za
> 105.255.152 ns2.vodacombusiness.co.za
> 105.255.153 ns1.vodacombusiness.co.za
> 105.255.153 ns2.vodacombusiness.co.za
> 105.255.165 ns1.vodacombusiness.co.za
> 105.255.165 ns2.vodacombusiness.co.za
> 105.255.192 ns1.vodacombusiness.co.za
> 105.255.192 ns2.vodacombusiness.co.za
> 105.255.216 ns1.vodacombusiness.co.za
> 105.255.216 ns2.vodacombusiness.co.za
> 105.255.217 ns1.vodacombusiness.co.za
> 105.255.217 ns2.vodacombusiness.co.za
> 105.255.237 ns1.vodacombusiness.co.za
> 105.255.237 ns2.vodacombusiness.co.za
> 105.255.146 ns1.vodacombusiness.co.za
> 105.255.146 ns2.vodacombusiness.co.za
> 105.255.129 ns1.vodacombusiness.co.za
> 105.255.129 ns2.vodacombusiness.co.za
> 105.255.139 ns1.vodacombusiness.co.za
> 105.255.139 ns2.vodacombusiness.co.za
> 105.255.140 ns1.vodacombusiness.co.za
> 105.255.140 ns2.vodacombusiness.co.za
> 105.255.142 ns1.vodacombusiness.co.za
> 105.255.142 ns2.vodacombusiness.co.za
> 105.255.143 ns1.vodacombusiness.co.za
> 105.255.143 ns2.vodacombusiness.co.za
> 105.255.144 ns1.vodacombusiness.co.za
> 105.255.144 ns2.vodacombusiness.co.za
> 105.255.147 ns1.vodacombusiness.co.za
> 105.255.147 ns2.vodacombusiness.co.za
> 105.255.148 ns1.vodacombusiness.co.za
> 105.255.148 ns2.vodacombusiness.co.za
> 105.255.149 ns1.vodacombusiness.co.za
> 105.255.149 ns2.vodacombusiness.co.za
> 105.255.150 ns1.vodacombusiness.co.za
> 105.255.150 ns2.vodacombusiness.co.za
> 105.255.151 ns1.vodacombusiness.co.za
> 105.255.151 ns2.vodacombusiness.co.za
> 105.255.154 ns1.vodacombusiness.co.za
> 105.255.154 ns2.vodacombusiness.co.za
> 105.255.155 ns1.vodacombusiness.co.za
> 105.255.155 ns2.vodacombusiness.co.za
> 105.255.160 ns1.vodacombusiness.co.za
> 105.255.160 ns2.vodacombusiness.co.za
> 105.255.161 ns1.vodacombusiness.co.za
> 105.255.161 ns2.vodacombusiness.co.za
> 105.255.164 ns1.vodacombusiness.co.za
> 105.255.164 ns2.vodacombusiness.co.za
> 105.255.176 ns1.vodacombusiness.co.za
> 105.255.176 ns2.vodacombusiness.co.za
> 105.255.177 ns1.vodacombusiness.co.za
> 105.255.177 ns2.vodacombusiness.co.za
> 105.255.184 ns1.vodacombusiness.co.za
> 105.255.184 ns2.vodacombusiness.co.za
> 105.255.193 ns1.vodacombusiness.co.za
> 105.255.193 ns2.vodacombusiness.co.za
> 105.255.194 ns1.vodacombusiness.co.za
> 105.255.194 ns2.vodacombusiness.co.za
> 105.255.195 ns1.vodacombusiness.co.za
> 105.255.195 ns2.vodacombusiness.co.za
> 105.255.200 ns1.vodacombusiness.co.za
> 105.255.200 ns2.vodacombusiness.co.za
> 105.255.206 ns1.vodacombusiness.co.za
> 105.255.206 ns2.vodacombusiness.co.za
> 105.255.208 ns1.vodacombusiness.co.za
> 105.255.208 ns2.vodacombusiness.co.za
> 105.255.218 ns1.vodacombusiness.co.za
> 105.255.218 ns2.vodacombusiness.co.za
> 105.255.219 ns1.vodacombusiness.co.za
> 105.255.219 ns2.vodacombusiness.co.za
> 129.205.80 41.161.16.132
> 129.205.80 41.160.80.8
> 129.205.81 41.161.16.132
> 129.205.81 41.160.80.8
> 41.60.131 auth1.liquidtelecom.com
> 41.60.131 auth2.liquidtelecom.com
> 41.60.22 auth1.liquidtelecom.com
> 41.60.22 auth2.liquidtelecom.com
> 41.60.230 auth1.liquidtelecom.com
> 41.60.230 auth2.liquidtelecom.com
> 41.60.3 auth1.liquidtelecom.com
> 41.60.3 auth2.liquidtelecom.com
> 41.60.231 ns1.liquidtelecom.net
> 41.60.231 ns2.liquidtelecom.net
> 41.60.137 ns1.liquidtelecom.net
> 41.60.137 ns2.liquidtelecom.net
> 41.60.208 ns1.liquidtelecom.net
> 41.60.208 ns2.liquidtelecom.net
> 41.60.209 ns1.liquidtelecom.net
> 41.60.209 ns2.liquidtelecom.net
> 41.60.210 ns1.liquidtelecom.net
> 41.60.210 ns2.liquidtelecom.net
> 41.60.211 ns1.liquidtelecom.net
> 41.60.211 ns2.liquidtelecom.net
> 41.60.212 ns1.liquidtelecom.net
> 41.60.212 ns2.liquidtelecom.net
> 41.60.213 ns1.liquidtelecom.net
> 41.60.213 ns2.liquidtelecom.net
> 41.60.214 ns1.liquidtelecom.net
> 41.60.214 ns2.liquidtelecom.net
> 41.60.215 ns1.liquidtelecom.net
> 41.60.215 ns2.liquidtelecom.net
> 41.60.216 ns1.liquidtelecom.net
> 41.60.216 ns2.liquidtelecom.net
> 41.60.217 ns1.liquidtelecom.net
> 41.60.217 ns2.liquidtelecom.net
> 41.60.218 ns1.liquidtelecom.net
> 41.60.218 ns2.liquidtelecom.net
> 41.60.219 ns1.liquidtelecom.net
> 41.60.219 ns2.liquidtelecom.net
> 41.60.220 ns1.liquidtelecom.net
> 41.60.220 ns2.liquidtelecom.net
> 41.60.221 ns1.liquidtelecom.net
> 41.60.221 ns2.liquidtelecom.net
> 41.60.222 ns1.liquidtelecom.net
> 41.60.222 ns2.liquidtelecom.net
> 41.60.223 ns1.liquidtelecom.net
> 41.60.223 ns2.liquidtelecom.net
> 41.60.224 ns1.liquidtelecom.net
> 41.60.224 ns2.liquidtelecom.net
> 41.60.200 ns1.liquidtelecom.co.zw
> 41.60.200 ns2.liquidtelecom.co.zw
> 41.60.200 ns3.liquidtelecom.co.zw
> 41.60.200 ns4.liquidtelecom.com
> 41.60.201 ns1.liquidtelecom.co.zw
> 41.60.201 ns2.liquidtelecom.co.zw
> 41.60.201 ns3.liquidtelecom.co.zw
> 41.60.201 ns4.liquidtelecom.com
> 41.60.202 ns1.liquidtelecom.co.zw
> 41.60.202 ns2.liquidtelecom.co.zw
> 41.60.202 ns3.liquidtelecom.co.zw
> 41.60.202 ns4.liquidtelecom.com
> 41.60.203 ns1.liquidtelecom.co.zw
> 41.60.203 ns2.liquidtelecom.co.zw
> 41.60.203 ns3.liquidtelecom.co.zw
> 41.60.203 ns4.liquidtelecom.com
> 41.60.204 ns1.liquidtelecom.co.zw
> 41.60.204 ns2.liquidtelecom.co.zw
> 41.60.204 ns3.liquidtelecom.co.zw
> 41.60.204 ns4.liquidtelecom.com
> 41.60.205 ns1.liquidtelecom.co.zw
> 41.60.205 ns2.liquidtelecom.co.zw
> 41.60.205 ns3.liquidtelecom.co.zw
> 41.60.205 ns4.liquidtelecom.com
> 41.60.206 ns1.liquidtelecom.co.zw
> 41.60.206 ns2.liquidtelecom.co.zw
> 41.60.206 ns3.liquidtelecom.co.zw
> 41.60.206 ns4.liquidtelecom.com
> 41.60.207 ns1.liquidtelecom.co.zw
> 41.60.207 ns2.liquidtelecom.co.zw
> 41.60.207 ns3.liquidtelecom.co.zw
> 41.60.207 ns4.liquidtelecom.com
> 105.234.0 ns1.airtel.africa
> 105.234.0 ns2.airtel.africa
> 41.60.188 ns1.liquidtelecom.net
> 41.60.188 ns2.liquidtelecom.net
> 196.179.252 ns.tunet.tn
> 196.179.252 ns2.tunet.tn
> 41.60.228 ns1.liquidtelecom.net
> 41.60.228 ns2.liquidtelecom.net
> 196.201.11 ns1.rcswimax.com
> 196.201.11 ns2.rcswimax.com
> 154.73.4 154.73.6.242
> 154.73.4 196.6.111.242
> 41.1.51 dnsinfo1-cte-pt.3g.vodacom.co.za
> 41.1.51 dnsinfo1-dne-pt.3g.vodacom.co.za
> 41.1.51 dnsinfo1-mtp-pt.3g.vodacom.co.za
> 41.1.51 dnsinfo1-psi-pt.3g.vodacom.co.za
> 41.1.51 dnsinfo1-cfo.3g.vodacom.co.za
> 41.1.51 dnsinfo1-dmo.3g.vodacom.co.za
> 41.1.51 dnsinfo1-mdp.3g.vodacom.co.za
> 41.1.51 dnsinfo1-prs.3g.vodacom.co.za
> 41.1.114 dnsinfo1-cte-pt.3g.vodacom.co.za
> 41.1.114 dnsinfo1-dne-pt.3g.vodacom.co.za
> 41.1.114 dnsinfo1-mtp-pt.3g.vodacom.co.za
> 41.1.114 dnsinfo1-psi-pt.3g.vodacom.co.za
> 41.1.114 dnsinfo1-cfo.3g.vodacom.co.za
> 41.1.114 dnsinfo1-dmo.3g.vodacom.co.za
> 41.1.114 dnsinfo1-mdp.3g.vodacom.co.za
> 41.1.114 dnsinfo1-prs.3g.vodacom.co.za
> 41.1.47 dnsinfo1-cte-pt.3g.vodacom.co.za
> 41.1.47 dnsinfo1-dne-pt.3g.vodacom.co.za
> 41.1.47 dnsinfo1-mtp-pt.3g.vodacom.co.za
> 41.1.47 dnsinfo1-psi-pt.3g.vodacom.co.za
> 41.1.47 dnsinfo1-cfo.3g.vodacom.co.za
> 41.1.47 dnsinfo1-dmo.3g.vodacom.co.za
> 41.1.47 dnsinfo1-mdp.3g.vodacom.co.za
> 41.1.47 dnsinfo1-prs.3g.vodacom.co.za
> 41.1.111 dnsinfo1-cte-pt.3g.vodacom.co.za
> 41.1.111 dnsinfo1-dne-pt.3g.vodacom.co.za
> 41.1.111 dnsinfo1-mtp-pt.3g.vodacom.co.za
> 41.1.111 dnsinfo1-psi-pt.3g.vodacom.co.za
> 41.1.111 dnsinfo1-cfo.3g.vodacom.co.za
> 41.1.111 dnsinfo1-dmo.3g.vodacom.co.za
> 41.1.111 dnsinfo1-mdp.3g.vodacom.co.za
> 41.1.111 dnsinfo1-prs.3g.vodacom.co.za
> 41.1.161 dnsinfo1-cte-pt.3g.vodacom.co.za
> 41.1.161 dnsinfo1-dne-pt.3g.vodacom.co.za
> 41.1.161 dnsinfo1-mtp-pt.3g.vodacom.co.za
> 41.1.161 dnsinfo1-psi-pt.3g.vodacom.co.za
> 41.1.161 dnsinfo1-cfo.3g.vodacom.co.za
> 41.1.161 dnsinfo1-dmo.3g.vodacom.co.za
> 41.1.161 dnsinfo1-mdp.3g.vodacom.co.za
> 41.1.161 dnsinfo1-prs.3g.vodacom.co.za
> 41.1.239 dnsinfo1-cte-pt.3g.vodacom.co.za
> 41.1.239 dnsinfo1-dne-pt.3g.vodacom.co.za
> 41.1.239 dnsinfo1-mtp-pt.3g.vodacom.co.za
> 41.1.239 dnsinfo1-psi-pt.3g.vodacom.co.za
> 41.1.239 dnsinfo1-cfo.3g.vodacom.co.za
> 41.1.239 dnsinfo1-dmo.3g.vodacom.co.za
> 41.1.239 dnsinfo1-mdp.3g.vodacom.co.za
> 41.1.239 dnsinfo1-prs.3g.vodacom.co.za
> 41.1.176 dnsinfo1-cte-pt.3g.vodacom.co.za
> 41.1.176 dnsinfo1-dne-pt.3g.vodacom.co.za
> 41.1.176 dnsinfo1-mtp-pt.3g.vodacom.co.za
> 41.1.176 dnsinfo1-psi-pt.3g.vodacom.co.za
> 41.1.176 dnsinfo1-cfo.3g.vodacom.co.za
> 41.1.176 dnsinfo1-dmo.3g.vodacom.co.za
> 41.1.176 dnsinfo1-mdp.3g.vodacom.co.za
> 41.1.176 dnsinfo1-prs.3g.vodacom.co.za
> 41.1.240 dnsinfo1-cte-pt.3g.vodacom.co.za
> 41.1.240 dnsinfo1-dne-pt.3g.vodacom.co.za
> 41.1.240 dnsinfo1-mtp-pt.3g.vodacom.co.za
> 41.1.240 dnsinfo1-psi-pt.3g.vodacom.co.za
> 41.1.240 dnsinfo1-cfo.3g.vodacom.co.za
> 41.1.240 dnsinfo1-dmo.3g.vodacom.co.za
> 41.1.240 dnsinfo1-mdp.3g.vodacom.co.za
> 41.1.240 dnsinfo1-prs.3g.vodacom.co.za
> 197.231.251 ns2
> 196.201.8 ns1.rcswimax.com
> 196.201.8 ns2.rcswimax.com
> 196.201.9 ns1.rcswimax.com
> 196.201.9 ns2.rcswimax.com
> 196.201.10 ns1.rcswimax.com
> 196.201.10 ns2.rcswimax.com
> 197.231.248 ns3
> 196.203.0 ns4.ati.tn
> 196.203.0 ns6.ati.tn
> 217.52.0 ns.aucegypt.edu
> 217.52.0 ns3.aucegypt.edu
> 196.203.1 ns4.ati.tn
> 196.203.1 ns6.ati.tn
> 217.52.1 ns.aucegypt.edu
> 217.52.1 ns3.aucegypt.edu
> 62.139.104 ns1.nile-online.net
> 62.139.104 ns2.nile-online.net
> 62.139.105 ns1.nile-online.net
> 62.139.105 ns2.nile-online.net
> 62.139.109 ns1.nile-online.net
> 62.139.109 ns2.nile-online.net
> 62.139.130 ns1.nile-online.net
> 62.139.130 ns2.nile-online.net
> 196.203.2 ns4.ati.tn
> 196.203.2 ns6.ati.tn
> 217.52.2 ns.aucegypt.edu
> 217.52.2 ns3.aucegypt.edu
> 62.139.253 ns2.egynet.com.eg
> 62.139.253 ns22.egynet.com.eg
> 217.52.3 ns.aucegypt.edu
> 217.52.3 ns3.aucegypt.edu
> 196.203.32 ns4.ati.tn
> 196.203.32 ns6.ati.tn
> 196.203.33 ns4.ati.tn
> 196.203.33 ns6.ati.tn
> 196.203.34 ns4.ati.tn
> 196.203.34 ns6.ati.tn
> 196.203.35 ns1.hexabyte.tn
> 196.203.35 ns2.hexabyte.tn
> 196.203.36 ns4.ati.tn
> 196.203.36 ns6.ati.tn
> 217.52.4 ns.aucegypt.edu
> 217.52.4 ns3.aucegypt.edu
> 217.52.5 ns.aucegypt.edu
> 217.52.5 ns3.aucegypt.edu
> 217.52.6 ns.aucegypt.edu
> 217.52.6 ns3.aucegypt.edu
> 217.52.7 ns.aucegypt.edu
> 217.52.7 ns3.aucegypt.edu
> 217.52.8 ns.aucegypt.edu
> 217.52.8 ns3.aucegypt.edu
> 196.205.11 ns1.link.net
> 196.205.11 ns2.link.net
> 212.0.159 sun1.sudatel.net
> 212.0.148 ns1.sudanmail.net
> 212.0.148 ns2.sudanmail.net
> 212.0.129 main.sdn-mobitel.com
> 212.0.129 main.sdn-mobinet.net
> 196.202.144 ns1.sudacom.net
> 196.202.144 ns2.sudacom.net
> 196.202.145 ns1.sudacom.net
> 196.202.145 ns2.sudacom.net
> 212.0.138 sun1.sudanet.net
> 212.0.146 sun1.sudanet.net
> 163.196 ns1.qdata.net
> 163.196 ns2.qdata.net
> 196.25.226 igubu.saix.net
> 196.25.226 sangoma.saix.net
> 196.205.177 ns1.link.net
> 196.205.177 ns2.link.net
> 196.205.0 ns1.link.net
> 196.205.0 ns2.link.net
> 196.205.1 ns1.link.net
> 196.205.1 ns2.link.net
> 196.205.2 ns1.link.net
> 196.205.2 ns2.link.net
> 196.205.3 ns1.link.net
> 196.205.3 ns2.link.net
> 196.205.4 ns1.link.net
> 196.205.4 ns2.link.net
> 196.205.5 ns1.link.net
> 196.205.5 ns2.link.net
> 196.205.6 ns1.link.net
> 196.205.6 ns2.link.net
> 196.205.7 ns1.link.net
> 196.205.7 ns2.link.net
> 196.205.8 ns1.link.net
> 196.205.8 ns2.link.net
> 196.205.9 ns1.link.net
> 196.205.9 ns2.link.net
> 196.205.10 ns1.link.net
> 196.205.10 ns2.link.net
> 196.205.12 ns1.link.net
> 196.205.12 ns2.link.net
> 196.205.13 ns1.link.net
> 196.205.13 ns2.link.net
> 196.205.14 ns1.link.net
> 196.205.14 ns2.link.net
> 196.205.15 ns1.link.net
> 196.205.15 ns2.link.net
> 196.205.16 ns1.link.net
> 196.205.16 ns2.link.net
> 196.205.17 ns1.link.net
> 196.205.17 ns2.link.net
> 196.205.18 ns1.link.net
> 196.205.18 ns2.link.net
> 196.205.19 ns1.link.net
> 196.205.19 ns2.link.net
> 196.205.20 ns1.link.net
> 196.205.20 ns2.link.net
> 196.205.21 ns1.link.net
> 196.205.21 ns2.link.net
> 196.205.22 ns1.link.net
> 196.205.22 ns2.link.net
> 196.205.23 ns1.link.net
> 196.205.23 ns2.link.net
> 196.205.24 ns1.link.net
> 196.205.24 ns2.link.net
> 196.205.25 ns1.link.net
> 196.205.25 ns2.link.net
> 196.205.26 ns1.link.net
> 196.205.26 ns2.link.net
> 196.205.27 ns1.link.net
> 196.205.27 ns2.link.net
> 196.205.28 ns1.link.net
> 196.205.28 ns2.link.net
> 196.205.29 ns1.link.net
> 196.205.29 ns2.link.net
> 196.205.30 ns1.link.net
> 196.205.30 ns2.link.net
> 196.205.31 ns1.link.net
> 196.205.31 ns2.link.net
> 196.205.32 ns1.link.net
> 196.205.32 ns2.link.net
> 196.205.33 ns1.link.net
> 196.205.33 ns2.link.net
> 196.205.34 ns1.link.net
> 196.205.34 ns2.link.net
> 196.205.36 ns1.link.net
> 196.205.36 ns2.link.net
> 196.205.37 ns1.link.net
> 196.205.37 ns2.link.net
> 196.205.38 ns1.link.net
> 196.205.38 ns2.link.net
> 196.205.39 ns1.link.net
> 196.205.39 ns2.link.net
> 196.205.40 ns1.link.net
> 196.205.40 ns2.link.net
> 196.205.35 ns1.link.net
> 196.205.35 ns2.link.net
> 196.205.55 ns1.link.net
> 196.205.55 ns2.link.net
> 196.205.43 ns1.link.net
> 196.205.43 ns2.link.net
> 196.205.60 ns1.link.net
> 196.205.60 ns2.link.net
> 196.205.49 ns1.link.net
> 196.205.49 ns2.link.net
> 196.205.44 ns1.link.net
> 196.205.44 ns2.link.net
> 196.205.46 ns1.link.net
> 196.205.46 ns2.link.net
> 196.205.52 ns1.link.net
> 196.205.52 ns2.link.net
> 196.205.53 ns1.link.net
> 196.205.53 ns2.link.net
> 196.205.50 ns1.link.net
> 196.205.50 ns2.link.net
> 196.205.51 ns1.link.net
> 196.205.51 ns2.link.net
> 196.205.59 ns1.link.net
> 196.205.59 ns2.link.net
> 196.205.47 ns1.link.net
> 196.205.47 ns2.link.net
> 196.205.48 ns1.link.net
> 196.205.48 ns2.link.net
> 196.205.56 ns1.link.net
> 196.205.56 ns2.link.net
> 196.205.45 ns1.link.net
> 196.205.45 ns2.link.net
> 196.205.42 ns1.link.net
> 196.205.42 ns2.link.net
> 196.205.58 ns1.link.net
> 196.205.58 ns2.link.net
> 196.205.54 ns1.link.net
> 196.205.54 ns2.link.net
> 196.205.41 ns1.link.net
> 196.205.41 ns2.link.net
> 196.205.57 ns1.link.net
> 196.205.57 ns2.link.net
> 196.205.61 ns1.link.net
> 196.205.61 ns2.link.net
> 196.205.62 ns1.link.net
> 196.205.62 ns2.link.net
> 196.205.63 ns1.link.net
> 196.205.63 ns2.link.net
> 196.205.64 ns1.link.net
> 196.205.64 ns2.link.net
> 196.205.65 ns1.link.net
> 196.205.65 ns2.link.net
> 196.205.66 ns1.link.net
> 196.205.66 ns2.link.net
> 196.205.67 ns1.link.net
> 196.205.67 ns2.link.net
> 196.205.68 ns1.link.net
> 196.205.68 ns2.link.net
> 196.205.69 ns1.link.net
> 196.205.69 ns2.link.net
> 196.205.70 ns1.link.net
> 196.205.70 ns2.link.net
> 196.205.71 ns1.link.net
> 196.205.71 ns2.link.net
> 196.205.72 ns1.link.net
> 196.205.72 ns2.link.net
> 196.205.74 ns1.link.net
> 196.205.74 ns2.link.net
> 196.205.77 ns1.link.net
> 196.205.77 ns2.link.net
> 196.205.78 ns1.link.net
> 196.205.78 ns2.link.net
> 196.205.79 ns1.link.net
> 196.205.79 ns2.link.net
> 196.205.73 ns1.link.net
> 196.205.73 ns2.link.net
> 196.205.75 ns1.link.net
> 196.205.75 ns2.link.net
> 196.205.82 ns1.link.net
> 196.205.82 ns2.link.net
> 196.205.76 ns1.link.net
> 196.205.76 ns2.link.net
> 196.205.80 ns1.link.net
> 196.205.80 ns2.link.net
> 196.205.81 ns1.link.net
> 196.205.81 ns2.link.net
> 196.205.83 ns1.link.net
> 196.205.83 ns2.link.net
> 196.205.84 ns1.link.net
> 196.205.84 ns2.link.net
> 196.205.85 ns1.link.net
> 196.205.85 ns2.link.net
> 196.205.86 ns1.link.net
> 196.205.86 ns2.link.net
> 196.205.87 ns1.link.net
> 196.205.87 ns2.link.net
> 196.205.88 ns1.link.net
> 196.205.88 ns2.link.net
> 196.205.89 ns1.link.net
> 196.205.89 ns2.link.net
> 196.205.90 ns1.link.net
> 196.205.90 ns2.link.net
> 196.205.91 ns1.link.net
> 196.205.91 ns2.link.net
> 196.205.92 ns1.link.net
> 196.205.92 ns2.link.net
> 196.205.93 ns1.link.net
> 196.205.93 ns2.link.net
> 196.205.94 ns1.link.net
> 196.205.94 ns2.link.net
> 196.205.95 ns1.link.net
> 196.205.95 ns2.link.net
> 196.205.96 ns1.link.net
> 196.205.96 ns2.link.net
> 196.205.97 ns1.link.net
> 196.205.97 ns2.link.net
> 196.205.98 ns1.link.net
> 196.205.98 ns2.link.net
> 196.205.99 ns1.link.net
> 196.205.99 ns2.link.net
> 196.205.100 ns1.link.net
> 196.205.100 ns2.link.net
> 196.205.101 ns1.link.net
> 196.205.101 ns2.link.net
> 196.205.102 ns1.link.net
> 196.205.102 ns2.link.net
> 196.205.103 ns1.link.net
> 196.205.103 ns2.link.net
> 196.205.104 ns1.link.net
> 196.205.104 ns2.link.net
> 196.205.105 ns1.link.net
> 196.205.105 ns2.link.net
> 196.205.106 ns1.link.net
> 196.205.106 ns2.link.net
> 196.205.107 ns1.link.net
> 196.205.107 ns2.link.net
> 196.205.108 ns1.link.net
> 196.205.108 ns2.link.net
> 196.205.109 ns1.link.net
> 196.205.109 ns2.link.net
> 196.205.110 ns1.link.net
> 196.205.110 ns2.link.net
> 196.205.111 ns1.link.net
> 196.205.111 ns2.link.net
> 196.205.112 ns1.link.net
> 196.205.112 ns2.link.net
> 196.205.113 ns1.link.net
> 196.205.113 ns2.link.net
> 196.205.115 ns1.link.net
> 196.205.115 ns2.link.net
> 196.205.116 ns1.link.net
> 196.205.116 ns2.link.net
> 196.205.114 ns1.link.net
> 196.205.114 ns2.link.net
> 196.205.117 ns1.link.net
> 196.205.117 ns2.link.net
> 196.205.118 ns1.link.net
> 196.205.118 ns2.link.net
> 196.205.119 ns1.link.net
> 196.205.119 ns2.link.net
> 196.205.120 ns1.link.net
> 196.205.120 ns2.link.net
> 196.205.121 ns1.link.net
> 196.205.121 ns2.link.net
> 196.205.122 ns1.link.net
> 196.205.122 ns2.link.net
> 196.205.123 ns1.link.net
> 196.205.123 ns2.link.net
> 196.205.124 ns1.link.net
> 196.205.124 ns2.link.net
> 196.205.125 ns1.link.net
> 196.205.125 ns2.link.net
> 196.205.126 ns1.link.net
> 196.205.126 ns2.link.net
> 196.205.127 ns1.link.net
> 196.205.127 ns2.link.net
> 196.205.128 ns1.link.net
> 196.205.128 ns2.link.net
> 196.205.129 ns1.link.net
> 196.205.129 ns2.link.net
> 196.205.130 ns1.link.net
> 196.205.130 ns2.link.net
> 196.205.131 ns1.link.net
> 196.205.131 ns2.link.net
> 196.205.132 ns1.link.net
> 196.205.132 ns2.link.net
> 196.205.133 ns1.link.net
> 196.205.133 ns2.link.net
> 196.205.134 ns1.link.net
> 196.205.134 ns2.link.net
> 196.205.135 ns1.link.net
> 196.205.135 ns2.link.net
> 196.205.136 ns1.link.net
> 196.205.136 ns2.link.net
> 196.205.137 ns1.link.net
> 196.205.137 ns2.link.net
> 196.205.138 ns1.link.net
> 196.205.138 ns2.link.net
> 196.205.139 ns1.link.net
> 196.205.139 ns2.link.net
> 196.205.140 ns1.link.net
> 196.205.140 ns2.link.net
> 196.205.141 ns1.link.net
> 196.205.141 ns2.link.net
> 196.205.142 ns1.link.net
> 196.205.142 ns2.link.net
> 196.205.143 ns1.link.net
> 196.205.143 ns2.link.net
> 196.205.144 ns1.link.net
> 196.205.144 ns2.link.net
> 196.205.145 ns1.link.net
> 196.205.145 ns2.link.net
> 196.205.146 ns1.link.net
> 196.205.146 ns2.link.net
> 196.205.147 ns1.link.net
> 196.205.147 ns2.link.net
> 196.205.148 ns1.link.net
> 196.205.148 ns2.link.net
> 196.205.149 ns1.link.net
> 196.205.149 ns2.link.net
> 196.205.150 ns1.link.net
> 196.205.150 ns2.link.net
> 196.205.151 ns1.link.net
> 196.205.151 ns2.link.net
> 196.205.152 ns1.link.net
> 196.205.152 ns2.link.net
> 196.205.153 ns1.link.net
> 196.205.153 ns2.link.net
> 196.205.154 ns1.link.net
> 196.205.154 ns2.link.net
> 196.205.155 ns1.link.net
> 196.205.155 ns2.link.net
> 196.205.156 ns1.link.net
> 196.205.156 ns2.link.net
> 196.205.157 ns1.link.net
> 196.205.157 ns2.link.net
> 196.205.158 ns1.link.net
> 196.205.158 ns2.link.net
> 196.205.159 ns1.link.net
> 196.205.159 ns2.link.net
> 196.205.160 ns1.link.net
> 196.205.160 ns2.link.net
> 196.205.161 ns1.link.net
> 196.205.161 ns2.link.net
> 196.205.162 ns1.link.net
> 196.205.162 ns2.link.net
> 196.205.163 ns1.link.net
> 196.205.163 ns2.link.net
> 196.205.164 ns1.link.net
> 196.205.164 ns2.link.net
> 196.205.165 ns1.link.net
> 196.205.165 ns2.link.net
> 196.205.166 ns1.link.net
> 196.205.166 ns2.link.net
> 196.205.167 ns1.link.net
> 196.205.167 ns2.link.net
> 196.205.168 ns1.link.net
> 196.205.168 ns2.link.net
> 196.205.169 ns1.link.net
> 196.205.169 ns2.link.net
> 196.205.170 ns1.link.net
> 196.205.170 ns2.link.net
> 196.205.172 ns1.link.net
> 196.205.172 ns2.link.net
> 196.205.171 ns1.link.net
> 196.205.171 ns2.link.net
> 196.205.173 ns1.link.net
> 196.205.173 ns2.link.net
> 196.205.174 ns1.link.net
> 196.205.174 ns2.link.net
> 196.205.175 ns1.link.net
> 196.205.175 ns2.link.net
> 196.205.176 ns1.link.net
> 196.205.176 ns2.link.net
> 196.205.178 ns1.link.net
> 196.205.178 ns2.link.net
> 196.205.179 ns1.link.net
> 196.205.179 ns2.link.net
> 196.205.180 ns1.link.net
> 196.205.180 ns2.link.net
> 196.205.181 ns1.link.net
> 196.205.181 ns2.link.net
> 196.205.182 ns1.link.net
> 196.205.182 ns2.link.net
> 196.205.183 ns1.link.net
> 196.205.183 ns2.link.net
> 196.205.184 ns1.link.net
> 196.205.184 ns2.link.net
> 196.205.185 ns1.link.net
> 196.205.185 ns2.link.net
> 196.205.186 ns1.link.net
> 196.205.186 ns2.link.net
> 196.205.187 ns1.link.net
> 196.205.187 ns2.link.net
> 196.205.188 ns1.link.net
> 196.205.188 ns2.link.net
> 196.205.189 ns1.link.net
> 196.205.189 ns2.link.net
> 196.205.190 ns1.link.net
> 196.205.190 ns2.link.net
> 196.205.191 ns1.link.net
> 196.205.191 ns2.link.net
> 196.205.192 ns1.link.net
> 196.205.192 ns2.link.net
> 196.205.193 ns1.link.net
> 196.205.193 ns2.link.net
> 196.205.194 ns1.link.net
> 196.205.194 ns2.link.net
> 196.205.195 ns1.link.net
> 196.205.195 ns2.link.net
> 196.205.196 ns1.link.net
> 196.205.196 ns2.link.net
> 196.205.197 ns1.link.net
> 196.205.197 ns2.link.net
> 196.205.198 ns1.link.net
> 196.205.198 ns2.link.net
> 196.205.199 ns1.link.net
> 196.205.199 ns2.link.net
> 196.205.200 ns1.link.net
> 196.205.200 ns2.link.net
> 196.205.201 ns1.link.net
> 196.205.201 ns2.link.net
> 196.205.202 ns1.link.net
> 196.205.202 ns2.link.net
> 196.205.204 ns1.link.net
> 196.205.204 ns2.link.net
> 196.205.203 ns1.link.net
> 196.205.203 ns2.link.net
> 196.205.205 ns1.link.net
> 196.205.205 ns2.link.net
> 196.205.206 ns1.link.net
> 196.205.206 ns2.link.net
> 196.205.207 ns1.link.net
> 196.205.207 ns2.link.net
> 196.205.208 ns1.link.net
> 196.205.208 ns2.link.net
> 196.205.209 ns1.link.net
> 196.205.209 ns2.link.net
> 196.205.210 ns1.link.net
> 196.205.210 ns2.link.net
> 196.205.211 ns1.link.net
> 196.205.211 ns2.link.net
> 196.205.212 ns1.link.net
> 196.205.212 ns2.link.net
> 196.205.213 ns1.link.net
> 196.205.213 ns2.link.net
> 196.205.214 ns1.link.net
> 196.205.214 ns2.link.net
> 196.205.215 ns1.link.net
> 196.205.215 ns2.link.net
> 196.205.216 ns1.link.net
> 196.205.216 ns2.link.net
> 196.205.217 ns1.link.net
> 196.205.217 ns2.link.net
> 196.205.219 ns1.link.net
> 196.205.219 ns2.link.net
> 196.205.220 ns1.link.net
> 196.205.220 ns2.link.net
> 196.205.221 ns1.link.net
> 196.205.221 ns2.link.net
> 196.205.224 ns1.link.net
> 196.205.224 ns2.link.net
> 196.205.225 ns1.link.net
> 196.205.225 ns2.link.net
> 196.205.218 ns1.link.net
> 196.205.218 ns2.link.net
> 196.205.222 ns1.link.net
> 196.205.222 ns2.link.net
> 196.205.223 ns1.link.net
> 196.205.223 ns2.link.net
> 196.205.227 ns1.link.net
> 196.205.227 ns2.link.net
> 196.205.226 ns1.link.net
> 196.205.226 ns2.link.net
> 196.205.228 ns1.link.net
> 196.205.228 ns2.link.net
> 196.205.229 ns1.link.net
> 196.205.229 ns2.link.net
> 196.205.230 ns1.link.net
> 196.205.230 ns2.link.net
> 196.205.231 ns1.link.net
> 196.205.231 ns2.link.net
> 196.205.232 ns1.link.net
> 196.205.232 ns2.link.net
> 196.205.233 ns1.link.net
> 196.205.233 ns2.link.net
> 196.205.234 ns1.link.net
> 196.205.234 ns2.link.net
> 196.205.235 ns1.link.net
> 196.205.235 ns2.link.net
> 196.205.236 ns1.link.net
> 196.205.236 ns2.link.net
> 196.205.237 ns1.link.net
> 196.205.237 ns2.link.net
> 196.205.238 ns1.link.net
> 196.205.238 ns2.link.net
> 196.205.239 ns1.link.net
> 196.205.239 ns2.link.net
> 196.205.240 ns1.link.net
> 196.205.240 ns2.link.net
> 196.205.241 ns1.link.net
> 196.205.241 ns2.link.net
> 196.205.242 ns1.link.net
> 196.205.242 ns2.link.net
> 196.205.243 ns1.link.net
> 196.205.243 ns2.link.net
> 196.205.244 ns1.link.net
> 196.205.244 ns2.link.net
> 196.205.245 ns1.link.net
> 196.205.245 ns2.link.net
> 196.205.246 ns1.link.net
> 196.205.246 ns2.link.net
> 196.205.247 ns1.link.net
> 196.205.247 ns2.link.net
> 196.205.248 ns1.link.net
> 196.205.248 ns2.link.net
> 196.205.249 ns1.link.net
> 196.205.249 ns2.link.net
> 196.205.250 ns1.link.net
> 196.205.250 ns2.link.net
> 196.205.251 ns1.link.net
> 196.205.251 ns2.link.net
> 196.205.252 ns1.link.net
> 196.205.252 ns2.link.net
> 196.205.253 ns1.link.net
> 196.205.253 ns2.link.net
> 196.205.254 ns1.link.net
> 196.205.254 ns2.link.net
> 196.205.255 ns1.link.net
> 196.205.255 ns2.link.net
> 196.25.240 igubu.saix.net
> 196.25.240 sangoma.saix.net
> 196.25.240 induna.saix.net
> 196.25.240 sabela.saix.net
> 196.33.38 titan.is.co.za
> 196.33.38 demeter.is.co.za
> 196.33.38 jupiter.is.co.za
> 196.206.251 ns1.wanadoo.ma
> 196.206.251 ns2.wanadoo.ma
> 196.206.252 ns1.wanadoo.ma
> 196.206.252 ns2.wanadoo.ma
> 196.217.254 ns1.wanadoo.ma
> 196.217.254 ns2.wanadoo.ma
> 196.217.255 ns1.wanadoo.ma
> 196.217.255 ns2.wanadoo.ma
> 196.217.246 dns.menara.ma
> 196.217.246 dns1.menara.ma
> 196.218.254 ns1.tedata.net.jo
> 196.218.254 ns2.tedata.net.jo
> 41.194.2 ns.seychelles.net
> 41.194.2 ns2.seychelles.net
> 41.194.1 ns.seychelles.net
> 41.194.1 ns2.seychelles.net
> 41.194.3 ns.seychelles.net
> 41.194.3 ns2.seychelles.net
> 41.194.0 ns.seychelles.net
> 41.194.0 ns2.seychelles.net
> 196.206.240 ns1.wanadoo.ma
> 196.206.240 ns2.wanadoo.ma
> 217.52.64 ns1.mist-net.com
> 217.52.64 ns2.mist-net.com
> 217.52.72 ns1.mist-net.com
> 217.52.72 ns2.mist-net.com
> 217.52.26 ns1.mist-net.com
> 217.52.26 ns2.mist-net.com
> 41.249.252 dns.menara.ma
> 41.249.252 dns1.menara.ma
> 41.1.207 ns1.vodacombusiness.co.za
> 41.1.207 ns2.vodacombusiness.co.za
> 41.1.128 ns1.vodacombusiness.co.za
> 41.1.128 ns2.vodacombusiness.co.za
> 41.1.201 ns1.vodacombusiness.co.za
> 41.1.201 ns2.vodacombusiness.co.za
> 41.186.0 ns1.mtnonline.rw
> 41.186.0 ns2.mtnonline.rw
> 41.186.1 ns1.mtnonline.rw
> 41.186.1 ns2.mtnonline.rw
> 41.186.2 ns1.mtnonline.rw
> 41.186.2 ns2.mtnonline.rw
> 41.186.3 ns1.mtnonline.rw
> 41.186.3 ns2.mtnonline.rw
> 41.186.4 ns1.mtnonline.rw
> 41.186.4 ns2.mtnonline.rw
> 41.186.5 ns1.mtnonline.rw
> 41.186.5 ns2.mtnonline.rw
> 41.186.6 ns1.mtnonline.rw
> 41.186.6 ns2.mtnonline.rw
> 41.186.7 ns1.mtnonline.rw
> 41.186.7 ns2.mtnonline.rw
> 41.186.8 ns1.mtnonline.rw
> 41.186.8 ns2.mtnonline.rw
> 41.186.9 ns1.mtnonline.rw
> 41.186.9 ns2.mtnonline.rw
> 41.186.10 ns1.mtnonline.rw
> 41.186.10 ns2.mtnonline.rw
> 41.186.11 ns1.mtnonline.rw
> 41.186.11 ns2.mtnonline.rw
> 41.186.12 ns1.mtnonline.rw
> 41.186.12 ns2.mtnonline.rw
> 41.186.13 ns1.mtnonline.rw
> 41.186.13 ns2.mtnonline.rw
> 41.186.14 ns1.mtnonline.rw
> 41.186.14 ns2.mtnonline.rw
> 41.186.15 ns1.mtnonline.rw
> 41.186.15 ns2.mtnonline.rw
> 41.186.16 ns1.mtnonline.rw
> 41.186.16 ns2.mtnonline.rw
> 41.186.17 ns1.mtnonline.rw
> 41.186.17 ns2.mtnonline.rw
> 41.186.18 ns1.mtnonline.rw
> 41.186.18 ns2.mtnonline.rw
> 41.186.19 ns1.mtnonline.rw
> 41.186.19 ns2.mtnonline.rw
> 41.186.20 ns1.mtnonline.rw
> 41.186.20 ns2.mtnonline.rw
> 41.1.136 ns1.vodacombusiness.co.za
> 41.1.136 ns2.vodacombusiness.co.za
> 41.248.248 dns.menara.ma
> 41.248.248 dns1.menara.ma
> 41.251.255 dns.menara.ma
> 41.251.255 dns1.menara.ma
> 41.251.254 dns.menara.ma
> 41.251.254 dns1.menara.ma
> 41.251.250 dns.menara.ma
> 41.251.250 dns1.menara.ma
> 41.192.255 ns01.socialcode.biz
> 41.192.255 ns02.socialcode.biz
> 41.94.0 ns1.morenet.ac.mz
> 41.94.0 zebra.uem.mz
> 41.94.10 ns1.morenet.ac.mz
> 41.94.10 zebra.uem.mz
> 41.94.8 ns1.morenet.ac.mz
> 41.94.8 zebra.uem.mz
> 196.25.146 igubu.saix.net
> 196.25.146 sangoma.saix.net
> 196.25.146 induna.saix.net
> 196.25.146 sabela.saix.net
> 196.25.147 igubu.saix.net
> 196.25.147 sangoma.saix.net
> 196.25.147 induna.saix.net
> 196.25.147 sabela.saix.net
> 197.235.1 ns1.vm.co.mz
> 197.235.1 ns2.vm.co.mz
> 41.186.24 ns1.mtnonline.rw
> 41.186.24 ns2.mtnonline.rw
> 41.186.22 ns1.mtnonline.rw
> 41.186.22 ns2.mtnonline.rw
> 41.186.36 ns1.mtnonline.rw
> 41.186.36 ns2.mtnonline.rw
> 41.186.44 ns1.mtnonline.rw
> 41.186.44 ns1.mtnonline.rw
> 41.231.7 ns1.atlax.com
> 41.231.7 ns2.atlax.com
> 41.231.7 ns3.atlax.com
> 41.248.226 dns.menara.ma
> 41.248.226 dns1.menara.ma
> 154.120.192 217.15.112.171
> 154.120.192 217.15.112.170
> 196.49.3 196.49.3.11
> 41.60.1 auth1.liquidtelecom.com
> 41.60.1 auth2.liquidtelecom.com
> 41.60.10 dns1.realtime.zm
> 41.60.10 dns2.realtime.zm
> 41.60.10 dns3.realtime.zm
> 41.60.10 dns4.realtime.zm
> 41.60.14 auth1.liquidtelecom.com
> 41.60.14 auth2.liquidtelecom.com
> 41.60.129 auth1.liquidtelecom.com
> 41.60.129 auth2.liquidtelecom.com
> 41.60.130 auth1.liquidtelecom.com
> 41.60.130 auth2.liquidtelecom.com
> 105.255.128 ns1.vodacombusiness.co.za
> 105.255.128 ns2.vodacombusiness.co.za
> 105.255.209 ns1.vodacombusiness.co.za
> 105.255.209 ns2.vodacombusiness.co.za
> 105.255.127 ns1.vodacombusiness.co.za
> 105.255.127 ns2.vodacombusiness.co.za
> 105.255.130 ns1.vodacombusiness.co.za
> 105.255.130 ns21.vodacombusiness.co.za
> 105.255.131 ns1.vodacombusiness.co.za
> 105.255.131 ns2.vodacombusiness.co.za
> 105.255.132 ns1.vodacombusiness.co.za
> 105.255.132 ns2.vodacombusiness.co.za
> 105.255.133 ns1.vodacombusiness.co.za
> 105.255.133 ns2.vodacombusiness.co.za
> 105.255.134 ns1.vodacombusiness.co.za
> 105.255.134 ns2.vodacombusiness.co.za
> 105.255.135 ns1.vodacombusiness.co.za
> 105.255.135 ns2.vodacombusiness.co.za
> 105.255.136 ns1.vodacombusiness.co.za
> 105.255.136 ns2.vodacombusiness.co.za
> 105.255.137 ns1.vodacombusiness.co.za
> 105.255.137 ns2.vodacombusiness.co.za
> 105.255.138 ns1.vodacombusiness.co.za
> 105.255.138 ns2.vodacombusiness.co.za
> 105.255.141 ns1.vodacombusiness.co.za
> 105.255.141 ns2.vodacombusiness.co.za
> 105.255.145 ns1.vodacombusiness.co.za
> 105.255.145 ns2.vodacombusiness.co.za
> 105.255.152 ns1.vodacombusiness.co.za
> 105.255.152 ns2.vodacombusiness.co.za
> 105.255.153 ns1.vodacombusiness.co.za
> 105.255.153 ns2.vodacombusiness.co.za
> 105.255.165 ns1.vodacombusiness.co.za
> 105.255.165 ns2.vodacombusiness.co.za
> 105.255.192 ns1.vodacombusiness.co.za
> 105.255.192 ns2.vodacombusiness.co.za
> 105.255.216 ns1.vodacombusiness.co.za
> 105.255.216 ns2.vodacombusiness.co.za
> 105.255.217 ns1.vodacombusiness.co.za
> 105.255.217 ns2.vodacombusiness.co.za
> 105.255.237 ns1.vodacombusiness.co.za
> 105.255.237 ns2.vodacombusiness.co.za
> 105.255.146 ns1.vodacombusiness.co.za
> 105.255.146 ns2.vodacombusiness.co.za
> 105.255.129 ns1.vodacombusiness.co.za
> 105.255.129 ns2.vodacombusiness.co.za
> 105.255.139 ns1.vodacombusiness.co.za
> 105.255.139 ns2.vodacombusiness.co.za
> 105.255.140 ns1.vodacombusiness.co.za
> 105.255.140 ns2.vodacombusiness.co.za
> 105.255.142 ns1.vodacombusiness.co.za
> 105.255.142 ns2.vodacombusiness.co.za
> 105.255.143 ns1.vodacombusiness.co.za
> 105.255.143 ns2.vodacombusiness.co.za
> 105.255.144 ns1.vodacombusiness.co.za
> 105.255.144 ns2.vodacombusiness.co.za
> 105.255.147 ns1.vodacombusiness.co.za
> 105.255.147 ns2.vodacombusiness.co.za
> 105.255.148 ns1.vodacombusiness.co.za
> 105.255.148 ns2.vodacombusiness.co.za
> 105.255.149 ns1.vodacombusiness.co.za
> 105.255.149 ns2.vodacombusiness.co.za
> 105.255.150 ns1.vodacombusiness.co.za
> 105.255.150 ns2.vodacombusiness.co.za
> 105.255.151 ns1.vodacombusiness.co.za
> 105.255.151 ns2.vodacombusiness.co.za
> 105.255.154 ns1.vodacombusiness.co.za
> 105.255.154 ns2.vodacombusiness.co.za
> 105.255.155 ns1.vodacombusiness.co.za
> 105.255.155 ns2.vodacombusiness.co.za
> 105.255.160 ns1.vodacombusiness.co.za
> 105.255.160 ns2.vodacombusiness.co.za
> 105.255.161 ns1.vodacombusiness.co.za
> 105.255.161 ns2.vodacombusiness.co.za
> 105.255.164 ns1.vodacombusiness.co.za
> 105.255.164 ns2.vodacombusiness.co.za
> 105.255.176 ns1.vodacombusiness.co.za
> 105.255.176 ns2.vodacombusiness.co.za
> 105.255.177 ns1.vodacombusiness.co.za
> 105.255.177 ns2.vodacombusiness.co.za
> 105.255.184 ns1.vodacombusiness.co.za
> 105.255.184 ns2.vodacombusiness.co.za
> 105.255.193 ns1.vodacombusiness.co.za
> 105.255.193 ns2.vodacombusiness.co.za
> 105.255.194 ns1.vodacombusiness.co.za
> 105.255.194 ns2.vodacombusiness.co.za
> 105.255.195 ns1.vodacombusiness.co.za
> 105.255.195 ns2.vodacombusiness.co.za
> 105.255.200 ns1.vodacombusiness.co.za
> 105.255.200 ns2.vodacombusiness.co.za
> 105.255.206 ns1.vodacombusiness.co.za
> 105.255.206 ns2.vodacombusiness.co.za
> 105.255.208 ns1.vodacombusiness.co.za
> 105.255.208 ns2.vodacombusiness.co.za
> 105.255.218 ns1.vodacombusiness.co.za
> 105.255.218 ns2.vodacombusiness.co.za
> 105.255.219 ns1.vodacombusiness.co.za
> 105.255.219 ns2.vodacombusiness.co.za
> 129.205.80 41.161.16.132
> 129.205.80 41.160.80.8
> 129.205.81 41.161.16.132
> 129.205.81 41.160.80.8
> 41.60.131 auth1.liquidtelecom.com
> 41.60.131 auth2.liquidtelecom.com
> 41.60.22 auth1.liquidtelecom.com
> 41.60.22 auth2.liquidtelecom.com
> 41.60.230 auth1.liquidtelecom.com
> 41.60.230 auth2.liquidtelecom.com
> 41.60.3 auth1.liquidtelecom.com
> 41.60.3 auth2.liquidtelecom.com
> 41.60.231 ns1.liquidtelecom.net
> 41.60.231 ns2.liquidtelecom.net
> 41.60.137 ns1.liquidtelecom.net
> 41.60.137 ns2.liquidtelecom.net
> 41.60.208 ns1.liquidtelecom.net
> 41.60.208 ns2.liquidtelecom.net
> 41.60.209 ns1.liquidtelecom.net
> 41.60.209 ns2.liquidtelecom.net
> 41.60.210 ns1.liquidtelecom.net
> 41.60.210 ns2.liquidtelecom.net
> 41.60.211 ns1.liquidtelecom.net
> 41.60.211 ns2.liquidtelecom.net
> 41.60.212 ns1.liquidtelecom.net
> 41.60.212 ns2.liquidtelecom.net
> 41.60.213 ns1.liquidtelecom.net
> 41.60.213 ns2.liquidtelecom.net
> 41.60.214 ns1.liquidtelecom.net
> 41.60.214 ns2.liquidtelecom.net
> 41.60.215 ns1.liquidtelecom.net
> 41.60.215 ns2.liquidtelecom.net
> 41.60.216 ns1.liquidtelecom.net
> 41.60.216 ns2.liquidtelecom.net
> 41.60.217 ns1.liquidtelecom.net
> 41.60.217 ns2.liquidtelecom.net
> 41.60.218 ns1.liquidtelecom.net
> 41.60.218 ns2.liquidtelecom.net
> 41.60.219 ns1.liquidtelecom.net
> 41.60.219 ns2.liquidtelecom.net
> 41.60.220 ns1.liquidtelecom.net
> 41.60.220 ns2.liquidtelecom.net
> 41.60.221 ns1.liquidtelecom.net
> 41.60.221 ns2.liquidtelecom.net
> 41.60.222 ns1.liquidtelecom.net
> 41.60.222 ns2.liquidtelecom.net
> 41.60.223 ns1.liquidtelecom.net
> 41.60.223 ns2.liquidtelecom.net
> 41.60.224 ns1.liquidtelecom.net
> 41.60.224 ns2.liquidtelecom.net
> 41.60.200 ns1.liquidtelecom.co.zw
> 41.60.200 ns2.liquidtelecom.co.zw
> 41.60.200 ns3.liquidtelecom.co.zw
> 41.60.200 ns4.liquidtelecom.com
> 41.60.201 ns1.liquidtelecom.co.zw
> 41.60.201 ns2.liquidtelecom.co.zw
> 41.60.201 ns3.liquidtelecom.co.zw
> 41.60.201 ns4.liquidtelecom.com
> 41.60.202 ns1.liquidtelecom.co.zw
> 41.60.202 ns2.liquidtelecom.co.zw
> 41.60.202 ns3.liquidtelecom.co.zw
> 41.60.202 ns4.liquidtelecom.com
> 41.60.203 ns1.liquidtelecom.co.zw
> 41.60.203 ns2.liquidtelecom.co.zw
> 41.60.203 ns3.liquidtelecom.co.zw
> 41.60.203 ns4.liquidtelecom.com
> 41.60.204 ns1.liquidtelecom.co.zw
> 41.60.204 ns2.liquidtelecom.co.zw
> 41.60.204 ns3.liquidtelecom.co.zw
> 41.60.204 ns4.liquidtelecom.com
> 41.60.205 ns1.liquidtelecom.co.zw
> 41.60.205 ns2.liquidtelecom.co.zw
> 41.60.205 ns3.liquidtelecom.co.zw
> 41.60.205 ns4.liquidtelecom.com
> 41.60.206 ns1.liquidtelecom.co.zw
> 41.60.206 ns2.liquidtelecom.co.zw
> 41.60.206 ns3.liquidtelecom.co.zw
> 41.60.206 ns4.liquidtelecom.com
> 41.60.207 ns1.liquidtelecom.co.zw
> 41.60.207 ns2.liquidtelecom.co.zw
> 41.60.207 ns3.liquidtelecom.co.zw
> 41.60.207 ns4.liquidtelecom.com
> 105.234.0 ns1.airtel.africa
> 105.234.0 ns2.airtel.africa
> 41.60.188 ns1.liquidtelecom.net
> 41.60.188 ns2.liquidtelecom.net
> 196.179.252 ns.tunet.tn
> 196.179.252 ns2.tunet.tn
> 41.60.228 ns1.liquidtelecom.net
> 41.60.228 ns2.liquidtelecom.net
> 196.201.11 ns1.rcswimax.com
> 196.201.11 ns2.rcswimax.com
> 154.73.4 154.73.6.242
> 154.73.4 196.6.111.242
> 41.1.51 dnsinfo1-cte-pt.3g.vodacom.co.za
> 41.1.51 dnsinfo1-dne-pt.3g.vodacom.co.za
> 41.1.51 dnsinfo1-mtp-pt.3g.vodacom.co.za
> 41.1.51 dnsinfo1-psi-pt.3g.vodacom.co.za
> 41.1.51 dnsinfo1-cfo.3g.vodacom.co.za
> 41.1.51 dnsinfo1-dmo.3g.vodacom.co.za
> 41.1.51 dnsinfo1-mdp.3g.vodacom.co.za
> 41.1.51 dnsinfo1-prs.3g.vodacom.co.za
> 41.1.114 dnsinfo1-cte-pt.3g.vodacom.co.za
> 41.1.114 dnsinfo1-dne-pt.3g.vodacom.co.za
> 41.1.114 dnsinfo1-mtp-pt.3g.vodacom.co.za
> 41.1.114 dnsinfo1-psi-pt.3g.vodacom.co.za
> 41.1.114 dnsinfo1-cfo.3g.vodacom.co.za
> 41.1.114 dnsinfo1-dmo.3g.vodacom.co.za
> 41.1.114 dnsinfo1-mdp.3g.vodacom.co.za
> 41.1.114 dnsinfo1-prs.3g.vodacom.co.za
> 41.1.47 dnsinfo1-cte-pt.3g.vodacom.co.za
> 41.1.47 dnsinfo1-dne-pt.3g.vodacom.co.za
> 41.1.47 dnsinfo1-mtp-pt.3g.vodacom.co.za
> 41.1.47 dnsinfo1-psi-pt.3g.vodacom.co.za
> 41.1.47 dnsinfo1-cfo.3g.vodacom.co.za
> 41.1.47 dnsinfo1-dmo.3g.vodacom.co.za
> 41.1.47 dnsinfo1-mdp.3g.vodacom.co.za
> 41.1.47 dnsinfo1-prs.3g.vodacom.co.za
> 41.1.111 dnsinfo1-cte-pt.3g.vodacom.co.za
> 41.1.111 dnsinfo1-dne-pt.3g.vodacom.co.za
> 41.1.111 dnsinfo1-mtp-pt.3g.vodacom.co.za
> 41.1.111 dnsinfo1-psi-pt.3g.vodacom.co.za
> 41.1.111 dnsinfo1-cfo.3g.vodacom.co.za
> 41.1.111 dnsinfo1-dmo.3g.vodacom.co.za
> 41.1.111 dnsinfo1-mdp.3g.vodacom.co.za
> 41.1.111 dnsinfo1-prs.3g.vodacom.co.za
> 41.1.161 dnsinfo1-cte-pt.3g.vodacom.co.za
> 41.1.161 dnsinfo1-dne-pt.3g.vodacom.co.za
> 41.1.161 dnsinfo1-mtp-pt.3g.vodacom.co.za
> 41.1.161 dnsinfo1-psi-pt.3g.vodacom.co.za
> 41.1.161 dnsinfo1-cfo.3g.vodacom.co.za
> 41.1.161 dnsinfo1-dmo.3g.vodacom.co.za
> 41.1.161 dnsinfo1-mdp.3g.vodacom.co.za
> 41.1.161 dnsinfo1-prs.3g.vodacom.co.za
> 41.1.239 dnsinfo1-cte-pt.3g.vodacom.co.za
> 41.1.239 dnsinfo1-dne-pt.3g.vodacom.co.za
> 41.1.239 dnsinfo1-mtp-pt.3g.vodacom.co.za
> 41.1.239 dnsinfo1-psi-pt.3g.vodacom.co.za
> 41.1.239 dnsinfo1-cfo.3g.vodacom.co.za
> 41.1.239 dnsinfo1-dmo.3g.vodacom.co.za
> 41.1.239 dnsinfo1-mdp.3g.vodacom.co.za
> 41.1.239 dnsinfo1-prs.3g.vodacom.co.za
> 41.1.176 dnsinfo1-cte-pt.3g.vodacom.co.za
> 41.1.176 dnsinfo1-dne-pt.3g.vodacom.co.za
> 41.1.176 dnsinfo1-mtp-pt.3g.vodacom.co.za
> 41.1.176 dnsinfo1-psi-pt.3g.vodacom.co.za
> 41.1.176 dnsinfo1-cfo.3g.vodacom.co.za
> 41.1.176 dnsinfo1-dmo.3g.vodacom.co.za
> 41.1.176 dnsinfo1-mdp.3g.vodacom.co.za
> 41.1.176 dnsinfo1-prs.3g.vodacom.co.za
> 41.1.240 dnsinfo1-cte-pt.3g.vodacom.co.za
> 41.1.240 dnsinfo1-dne-pt.3g.vodacom.co.za
> 41.1.240 dnsinfo1-mtp-pt.3g.vodacom.co.za
> 41.1.240 dnsinfo1-psi-pt.3g.vodacom.co.za
> 41.1.240 dnsinfo1-cfo.3g.vodacom.co.za
> 41.1.240 dnsinfo1-dmo.3g.vodacom.co.za
> 41.1.240 dnsinfo1-mdp.3g.vodacom.co.za
> 41.1.240 dnsinfo1-prs.3g.vodacom.co.za
> 197.231.251 ns2
> 196.201.8 ns1.rcswimax.com
> 196.201.8 ns2.rcswimax.com
> 196.201.9 ns1.rcswimax.com
> 196.201.9 ns2.rcswimax.com
> 196.201.10 ns1.rcswimax.com
> 196.201.10 ns2.rcswimax.com
> 197.231.248 ns3
> 
> _______________________________________________
> Community-Discuss mailing list
> Community-Discuss at afrinic.net
> https://lists.afrinic.net/mailman/listinfo/community-discuss
> 



From portia.rabonda at safnog.net  Thu Nov  5 18:16:14 2020
From: portia.rabonda at safnog.net (Portia Rabonda)
Date: Thu, 5 Nov 2020 18:16:14 +0000
Subject: [Community-Discuss] SAFNOG + ZANOG Virtual Conference - Thank You!
Message-ID: <5F1A5C18-BDE5-4F4D-ACD2-32A05B2C0917@safnog.net>

Dear All

Just a week ago, SAFNOG, together  with ZANOG hosted the SAFNOG + ZANOG Virtual Conference. We would like to extend our gratitude to everyone who made the event possible, from our speakers and panelists, our event sponsor, Teraco, and each of you who joined us to make the conference a success. Thank you!


SAFNOG + ZANOG Virtual Conference Quick Stats

 130 registered, 77 watched the webinar from 19 countries.


Presentations and Video

We had 4 speakers and 3 presentations, and a panel discussion.

Presentation slides can be accessed on the SAFNOG website on the following link:

http://www.safnog.org/virtual-meetings/presentations.html

The conference recording is available on the SAFNOG YouTube channel: SAFNOG ?_  on the following link: https://youtu.be/679Cpj5-nHY


Connect with us

We would like to continue to engage with you in discussions relevant to the community and as such, we invite you to join our mailing lists and connect with us on our social media channels.

Mailing lists:
SAFNOG:  http://lists.safnog.org/listinfo/safnog
ZANOG: zanog-discuss at lists.nog.net.za<mailto:zanog-discuss at lists.nog.net.za>
http://lists.nog.net.za/cgi-bin/mailman/listinfo/zanog-discuss

Social Media:
SAFNOG
Facebook: @SAFNOG
Twitter: @SAFNOG
Instagram: @safnog_

ZANOG
Facebook: ZA Network Operators Group
Twitter: @ZA_NOG


We look forward to engaging with you again on the above platforms.

Until the next event, keep well and stay safe.

Regards,

Portia Rabonda
On behalf of SAFNOG and ZANOG
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/community-discuss/attachments/20201105/78ecae78/attachment.html>

From noah at neo.co.tz  Thu Nov  5 22:09:15 2020
From: noah at neo.co.tz (Noah)
Date: Fri, 6 Nov 2020 01:09:15 +0300
Subject: [Community-Discuss] Notice to all the legacy netblocks holders
	in AfriNIC
In-Reply-To: <53767.1604146852@segfault.tristatelogic.com>
References: <CAEqgTWYqYddNikKzswv+RA18bBfe3or=aW0wv8Q_Z_yYPFbtrw@mail.gmail.com>
 <53767.1604146852@segfault.tristatelogic.com>
Message-ID: <CAEqgTWZcQ2O_nV_qMXXPOormSEuv9uJYZW5f3j7dgfKjoC3fSw@mail.gmail.com>

On Sat, Oct 31, 2020 at 3:26 PM Ronald F. Guilmette <rfg at tristatelogic.com>
wrote:

> In message <CAEqgTWYqYddNikKzswv+RA18bBfe3or=
> aW0wv8Q_Z_yYPFbtrw at mail.gmail.com>
> Noah <noah at neo.co.tz> wrote:
>
> >> Mr. Cohen has declared war on AFRINIC.  He is currently pursuing that
> war,
> >> with no signs of retreating or giving up.
> >
> >AFRINIC is an institution and not someone's property even though some of
> >these folks think AFRINIC should just be a bookkeeper hence their
> arrogance.
>
> Not to quibble with you,


No biggy...


> but actually, as I understand it, the charter
> of AFRINIC says that the whole of AFRINIC, including but not limited to
> the vast and valuable set of -all- IP addresses that it has assigned
> to various members since its inception, as well as, of course, its
> current remaining free pool, are in fact the legal property of the
> AFRINIC board.
>

Here is the deal and I beg to be corrected by folks to that end.

The company is limited by guarantee. Resource members elect directors
across different regions that AFRINIC servers across AFRICA and its those
elected directors who are then registered as guarantors (registered
members) on behalf of the resource members. Therefore, the members are the
main shareholders and if you will in business terms, the real investors as
per the constitutions which we refer to as the bylaws. Like any other
entity there must be governance and the board of directors role is exactly
that and the members have elected different director over the years to take
care of AFRINIC Ltd fudiciary duties.



>
> Perhaps I have been misinformed about this.  If so I would be happy to
> be educated on this point.
>
>
I hope I tried above.


> (I tried once to calculate the total current market value of all of the
> IPv4 address space that AFRINIC had been gifted with at its inception.
> The final esitimate I arrived at was something in excess of a quarter
> of a billion dollars, USD.  But I think that I may have left out a extra
> zero someplace, because a single AFRINIC member currently owns over $150
> million USD worth of non-legacy AFRINIC IPv4 address space.)
>

The very reason we must be conservative about how we manage those small
ammounts of limited numbers IANA allocated to the region so as to advance
internet infrastructure here.


>
> >> The institution that is AFRINIC is being besieged, via lawsuit, by
> >> Mr. Cohen.  And on what basis?  For what crime?  We still have no
> >> idea what this is even all about, or what Mr. Cohen's actual claims are.
> >>
> >
> >Didn't he claim that he bought some IPs from some members in our region. I
> >assume those must be some of the IP's that have since been recovered by
> >AFRINIC based on your dossier.  Perhaps the recovery is his motivation for
> >the pupported lawsuit.
>
> Perhaps.  The whole matter is shrouded in what I feel is unfortunate
> and actually ridiculous secrecy.  It seems that neither the AFRINIC
> board, nor Eddy, nor the Governance Counsel... whose purpose apart
> from the Board is still an utter mystery to me... nor even Mr. Cohen
> himself feel in the least bit obliged to let anyone else in on the
> Big Secret.
>

I wont comment much here since the issue is before court and I have limited
knowledge of the proceedings but I trust that the CEO and his team are
working this.


>
> (I am being neither rude nor insulting to repeat these widely known
> facts here.  The status of both Mauritius and Seychelles as safe
> havens for all manner of crooked international dealings is something
> that anyone with a web browser can easily verify for himself or herself.)
>

In your humble opinion ofcourse :-) since I havent done my homework to that
effect.


>
> >AFRINIC doesn't have a policy for buying and selling IPs as Cohen claims
> >but until recently the community enacted an Intra-RIR policy to allow IPv4
> >transfers within the region with AFRINIC continuing to handle the
> >management of these resource transfers based in need-basis.
>
> Legacy blocks are special.  They were assigned before AFRINIC or the
> RIR system even existed, and they are thus not legally subject to its
> decisions or edicts.
>
> Mr. Cohen seems to be of the opinion that any -abandoned- legacy
> blocks thus have a legal status similar to abandoned sea vessels under
> international maritime law, i.e. as we here would say it "finders
> keepers".  Just as one might claim an abandoned sandwich sitting alone
> on a park bench, he believes that AFRINIC has no legal authority to
> prevent him from enjoying the various free meals he thinks he has
> found, or perhaps purchased, from other Intetrnet sharks who have
> also been on the lookout for free meals.
>
> I personally disagree with this view, and believe that it has no basis
> in law, anywhere.
>

The only way to fix this historical mistake especially for the AFRINIC
region is for us to ensure that legacy space looses the legacy status after
all the holders enjoy RIR services to the cost of resource members.


>
> >> I could and should perhaps also
> >> have mentioned the case of the City of Cape Town's /16 block, and/or
> >> the fact that Mr. Cohen, in -another- show of force and stupidity...
> >
> >  equally as brazen and ill-considered as his present vicious and baseless
> >> legal attack on AFRINIC... also hired legal council in South Africa in a
> >> vain and short-lived attempt to browbeat, harass, and extort the City
> >> of Cape Town into giving him -their- rightful property (165.25.0.0/16).
> >
> >Since we dont have purview if these litigations, we can only imagine the
> >amount of fraud that has been going on under the carpet.
>
> To be clear, I have *not* asserted that Mr. Cohen has actually undertaken
> litigation per se against the City of Cape Town.
>

I Ack...


>
> As regards to your comment about what may be going on "under the carpet",
> I can only agree that the near total opacity of the evaluation processes
> that AFRINIC (and the other RIRs also) undertake when deciding to make
> or not make awards of valuable IP address space is quite obviously a
> wide open invitation to mischief and corruption... on the part of AFRINIC
> staff, AFRINIC management, and the AFRINIC Board.
>
> We have a saying in this country: "Sunlight is the best disinfectant."
>
> I firmly believe that -all- RIRs are, as we speak, hiding a whole lot
> of insider profiteering and other mischief, both past and present,
> behind a convenient wall of "corporate confidentiality" rules that
> insure that only the insiders know, or will ever know, why certain
> parties are rewwarded with valuable IP space while others are not
> so fortunate.
>

Some believe the RIR system should just be some book keeper while they
profit from leasing resources that are meant to be put to use based on
need-basis to build the net which goes of to affects lives positively.


>
> >By the way, Cohen was wonderibg why you dont also talk about some other
> >AFRINIC net blocks...
>
> I will have to address this is a separate email.  This one is already
> too long.
>

By all means....

Noah
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/community-discuss/attachments/20201106/26f6c284/attachment.html>

From rfg at tristatelogic.com  Thu Nov  5 22:55:55 2020
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Thu, 05 Nov 2020 14:55:55 -0800
Subject: [Community-Discuss] Yet more data base problems/inconsistancies
In-Reply-To: <d3e5bb88-f09c-3eba-188f-e0ebb8107f94@geier.ne.tz>
Message-ID: <33617.1604616955@segfault.tristatelogic.com>

In message <d3e5bb88-f09c-3eba-188f-e0ebb8107f94 at geier.ne.tz>, 
Frank Habicht <geier at geier.ne.tz> wrote:

>in the file i found:
>; Source AFRINIC
>203.196.in-addr.arpa.         NS        ns1.ati.tn.
>203.196.in-addr.arpa.         NS        ns2.ati.tn.
>
>if there is a delegation for the "/16 equivalent" then one can't create
>a delegation for an enclosed "/24 equivalent" zone. [1]
>
>So probably the
>> domain:         35.203.196.in-addr.arpa
>object shouldn't have been allowed to be created / imported from RIPE...

Let me just say at the outset that I may perhaps not be on entirely
solid ground here... I may need to drag out my Cricket book and double
check this... but my belief at the moment is that what you just said
is not actually correct, that DNS is a bit like routing, where a more
specific can effectively override a less specific, and that there is
nothing to prevent separate and different delegations to both a
containing /16 and also to a /24 within that /16.

Regardless of whether that is correct or not, as I have already noted,
there is clearly a mismatch between what is present in the AFRINIC
WHOIS data base and the data that is present within the various files
within ftp://ftp.afrinic.net/pub/zones/ and this mismatch, this
anomaly, should be addressed in some manner, either by removing invalid
entries from the WHOIS or by adding entries to the zone files.


Regards,
rfg



From rfg at tristatelogic.com  Fri Nov  6 00:55:37 2020
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Thu, 05 Nov 2020 16:55:37 -0800
Subject: [Community-Discuss] Notice to all the legacy netblocks holders
	in AfriNIC
In-Reply-To: <CAEqgTWZcQ2O_nV_qMXXPOormSEuv9uJYZW5f3j7dgfKjoC3fSw@mail.gmail.com>
Message-ID: <34045.1604624137@segfault.tristatelogic.com>

In message <CAEqgTWZcQ2O_nV_qMXXPOormSEuv9uJYZW5f3j7dgfKjoC3fSw at mail.gmail
.com> Noah <noah at neo.co.tz> wrote:

>Here is the deal and I beg to be corrected by folks to that end.
>
>>{... stuff about AFRINIC legal ownership snipped...}

I am not qualified to comment on any of this, as I have not read the
relevant documents, nor am I an attorney.  I can only repeat what
I already said about the ownership, which was the impression I was
given by other knowledgable sources.  (It may have been just plain
wrong.)

>> (I tried once to calculate the total current market value of all of the
>> IPv4 address space that AFRINIC had been gifted with at its inception.
>> The final esitimate I arrived at was something in excess of a quarter
>> of a billion dollars, USD.  But I think that I may have left out a extra
>> zero someplace, because a single AFRINIC member currently owns over $150
>> million USD worth of non-legacy AFRINIC IPv4 address space.)
>
>The very reason we must be conservative about how we manage those small
>ammounts of limited numbers IANA allocated to the region so as to advance
>internet infrastructure here.

There are many reasons to be "conservative" about the world's dwindling
supply of IPv4 addresses.  Like petrochemicals extracted from the earth,
the stuff may flow freely and abundantly now, even to the point where
we all feel free to squander what remains, but someday our profligate
human nature will, I'm sure, come back to haunt us, and we will wake up
with a hell of a hangover.

Ardent proponents of IPv6 will no doubt disagree with this view, but I do
believe that their views are still influenced more by hope than by current
day-to-day reality on the ground.  The proof of IPv4's ongoing importance
is visible everwhere, for those that would but look for it.  Speaking from
my own direct experience, of which I have a great deal, 99 spammers out
of 100 still to this day rely exclusively on IPv4 for the simple and
obvious reason that this maximizes their connectivity to the places they
wish to spam.  Also, Mr. Cohen, Mr. Uerlings, Mr. Byaruhanga and an
assortment of other Internet miscreants and ne'er-do-wells, who shall
for the time being remain nameless, have not gone to the extraordinary
lengths they have all gone to in order to gather unto themselves, by hook
or by crook, large hunks of IPv4 space just for their health.  For many
purposes, IPv4 is still the only game in town.

And by the way, yes, I do believe that I slipped a digit when I was trying
to calculate the total value of all of the IPv4 address space that was
gifted to AFRINIC by the other RIRs at the time of its inception, and
that a more accurate assesment of the total current open market value of
these assets likely exceeds $2.5 billion USD.  And rather humorously, the
various RIRs, including but not limited to AFRINIC have somehow persuaded,
and continue to persuade their respective financial auditors to simply
close their eyes and look the other way whenever the subject of these most
valuable assets comes up.  You can see this for yourself in past AFRINIC
auditor-generated financial statments, e.g. the one I looked at from 2015.
Nowhere are these most valuable assets of AFRINIC or the other RIRs ever
even considered to be assets... a most astonishing example of what would
appear on the face of it to be gross professional malpractice on the part
of the auditors, the size of which dwarfs even the national budgets of
several entire non-trivial countries.

Arguably, it is this sort of "fantasy accounting" that is at the heart of
many issues, both the AFRINIC thefts, which went on for years without any
of the accountants even noticing, and also the self-evident problem of
the well-connected in each region being granted valuable IPv4 allocations.=
..
sometimes huge ones... all via an entirely opaque process, while other
deserving candidates for that same space must go begging in the streets
for even small IPv4 allocations.

This sort of quiet and behind the scenes favoritism would have been both
fine and unremarkable in the old Soviet Union, but if we consider
ourselves to be capitalists, then this system cannot be viewed as anything
other than a quasi-governmental invitation to graft and influence peddling=
.
(And despite the selective blindness of the audittors, there is a LOT of
money at stake.)

But I digress.

>> Perhaps.  The whole matter is shrouded in what I feel is unfortunate
>> and actually ridiculous secrecy.  It seems that neither the AFRINIC
>> board, nor Eddy, nor the Governance Counsel... whose purpose apart
>> from the Board is still an utter mystery to me... nor even Mr. Cohen
>> himself feel in the least bit obliged to let anyone else in on the
>> Big Secret.
>
>I wont comment much here since the issue is before court and I have limit=
ed
>knowledge of the proceedings but I trust that the CEO and his team are
>working this.

Very nearly everyone has "limited knowledge of the proceedings'.  That
was my point.  One would think that the goals and purposes of one side
or the other in this epic conflict would be served by going public with
the relevant legal filings, but apparently they themselves do not feel
that to be the case.  To say that this arouses some deep suspicions for
me personally would be an understatement.  At the end of the day, will
AFRINIC elect to cut a secret backroom deal with Cohen, e.g. to let him
keep some portion of what he has stolen?  Or will they do as ARIN did
back in 2008, make the thief give up what he has stolen, but then find
a different way to reward him, like say, giving him an amount of
legitimately allocated IPv4 space equivalent to 1/4th of the total of
what he stole?  That is, as I understand it, what happened in this case
back in 2008, because ARIN was too afraid to litigate the matter against
the thief:

http://voices.washingtonpost.com/securityfix/2008/04/a_case_of_network_identity_the_1.html

>> (I am being neither rude nor insulting to repeat these widely known
>> facts here.  The status of both Mauritius and Seychelles as safe
>> havens for all manner of crooked international dealings is something
>> that anyone with a web browser can easily verify for himself or herself=
.)
>
>In your humble opinion ofcourse :-) since I havent done my homework to that
>effect.

I invite you to do so.  The ongiong status of both Mauritius and Seychelles
as safe havens for all manner of financial chicanery and skullduggery is
in no sense a secret.  If google doesn't get you there let me know, and
I will be more than happy to provide numerous links to authoritativeo
material, all of it entirely public.

>> Mr. Cohen seems to be of the opinion that any -abandoned- legacy
>> blocks thus have a legal status similar to abandoned sea vessels under
>> international maritime law,...
>>
>> I personally disagree with this view, and believe that it has no basis
>> in law, anywhere.
>
>The only way to fix this historical mistake especially for the AFRINIC
>region is for us to ensure that legacy space looses the legacy status after
>all the holders enjoy RIR services to the cost of resource members.

This notion has been discussed and even litigated in other regions, most
notabley in the ARIN region.  It is *not* legally tenable, so you should
forget about it.  Legacy blocks are legacy blocks, and evermore shall
remain so.

What is less clear is the legal authority of Regional Internet Registries
to simply stop providing support services, specifically WHOIS entries and
reverse DNS delegation, in exchange for exactly zero dollars and zero
cents, which is the current going rate in all regions for keeping either /
both abandoned legacy blocks and live legacy blocks in the WHOIS and in
the reverse DNS zone files, even if those two forms of ongoing upkeep
only amount to the Internet equivalent of life support.

In this sense, the RIRs are effectively being asked and/or expected to
operate as charities, and although this may have all been part of the
plan at the time the various RIRs were formed, times change, and I
personally am not aware of any legal impediment that would prevent any
RIR from requiring some maintenance fees... perhaps minimal, perhaps
astronomical... from the legacy holders in exchange for ongoing WHOIS
and reverse DNS delegation.

It all comes back again to money, and the deliberate and selective
blindness upon which this whole (RIR) system has been built over the
past 23 years.  The cracks in this delusional fantasy are staring to
show, and like pretty much everything else in this capitalist world,
sooner or later, everything will, in the end, end up, as we say here
"on a paying basis", i.e. no more freebies.  This is the inevitable
and unavoidable end-game.

The now self-evident problems generated by the "attractive nuisances" that
are abandoned legacy blocks would have all worked theselves out long ago
if the purported legal block owners had simply been asked to pay an
annual fee of a mere ten cents (USD) for annual upkeep (of the WHOIS).
Some of these companies have been dead for 25+ years!  Thus, in those
cases, where there is no one who even lays a claim (and thus no one who
is even willing to pay the ten cent annual fee), after say, 3 years
or so, then the block should be reclaimed.  This is not rocket science,
and everyone who knows anything about "keepalive" packets should have
no trouble understanding the simple concept here.  The ten cent annual
fee is, in this context, simply a proxy for a sort of liveness check.
No new contracts need be involved... just annual payment of ten cents.

>> I firmly believe that -all- RIRs are, as we speak, hiding a whole lot
>> of insider profiteering and other mischief, both past and present,
>> behind a convenient wall of "corporate confidentiality" rules that
>> insure that only the insiders know, or will ever know, why certain
>> parties are rewwarded with valuable IP space while others are not
>> so fortunate.
>
>Some believe the RIR system should just be some book keeper while they
>profit from leasing resources that are meant to be put to use based on
>need-basis to build the net which goes of to affects lives positively.

See above regarding accounting.

All of history shows that the best way to insure that something will be
well used is to put a price on it.  (And this is why, even thouugh I tend
strongly towards the liberal end of the spectrum, I am against the
proposal by our Senator Bernie Sanders to make college tuition free.
Doing do would make a college degree essentially worthless, which it
already alomost is due to the fact that even intelligent doorstops are
currently able to get government grants and loans to attend college here
in the U.S.)

The only way to -actually- insure that IPv4 addresses will go to those
who will make the most serious and thoughtful use of them is to auction
them all off to the higest bidder.  Every other appoach is just a cover
story for favoritism, nepotism, and insider trading.   (And this statement
is by no means a selective criticism, on my part, of just AFRINIC.  I
have long held the same opinion also with respect to all five of the
Regional Internet Registries.)

If it is desired, for political and/or social reasons, that AFRINIC IPv4
addresses should actually be awarded to African entities and individuals.
an idea that I myself support even more than most Africans, it seems...
then fine... add that geographic restriction as a requirement on all
bidders.  Problem solved!

(Funny fact:  Conducting a geographically restricted auction of AFRINIC
IPv4 addresses would result in substantially *more* of these valuable
resources going to serve the needs of the continent than is currently the
case, because at present, nobody is even patying attention to, let alone
enforcing, *any* geographic restrictions relative to the holders or new
recipients of "AFRINIC" addresses... a sad commentary on the single most
glaring failure of AFRINIC to date, i.e. its inability and/or unwillingness
to do anything specific to insure that it is actually serving *African*
needs, specifically, rather than serving the needs of fast-buck interlopers,
carpetbaggers, and profiteers from other regions.)


Regards,
rfg



From geier at geier.ne.tz  Fri Nov  6 04:47:31 2020
From: geier at geier.ne.tz (Frank Habicht)
Date: Fri, 6 Nov 2020 07:47:31 +0300
Subject: [Community-Discuss] Yet more data base problems/inconsistancies
In-Reply-To: <33617.1604616955@segfault.tristatelogic.com>
References: <33617.1604616955@segfault.tristatelogic.com>
Message-ID: <26aae75f-9047-85d9-efa6-21319369619c@geier.ne.tz>

Hi,

On 06/11/2020 01:55, Ronald F. Guilmette wrote:
> In message <d3e5bb88-f09c-3eba-188f-e0ebb8107f94 at geier.ne.tz>, 
> Frank Habicht <geier at geier.ne.tz> wrote:
> 
>> in the file i found:
>> ; Source AFRINIC
>> 203.196.in-addr.arpa.         NS        ns1.ati.tn.
>> 203.196.in-addr.arpa.         NS        ns2.ati.tn.
>>
>> if there is a delegation for the "/16 equivalent" then one can't create
>> a delegation for an enclosed "/24 equivalent" zone. [1]
>>
>> So probably the
>>> domain:         35.203.196.in-addr.arpa
>> object shouldn't have been allowed to be created / imported from RIPE...
> 
> Let me just say at the outset that I may perhaps not be on entirely
> solid ground here... I may need to drag out my Cricket book and double
> check this... but my belief at the moment is that what you just said
> is not actually correct, that DNS is a bit like routing, where a more
> specific can effectively override a less specific, and that there is
> nothing to prevent separate and different delegations to both a
> containing /16 and also to a /24 within that /16.

I have no idea why Cricket ....   ;-)
But have to say I agree.
I was writing what I was writing based on the 2nd paragraph from Anand in
https://www.ripe.net/ripe/mail/archives/db-wg/2020-October/006687.html
which maybe I have misinterpreted.


> Regardless of whether that is correct or not, as I have already noted,
> there is clearly a mismatch between what is present in the AFRINIC
> WHOIS data base and the data that is present within the various files
> within ftp://ftp.afrinic.net/pub/zones/ and this mismatch, this
> anomaly, should be addressed in some manner, either by removing invalid
> entries from the WHOIS or by adding entries to the zone files.

Completely agree.

Frank




From rfg at tristatelogic.com  Fri Nov  6 05:09:53 2020
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Thu, 05 Nov 2020 21:09:53 -0800
Subject: [Community-Discuss] Yet more data base problems/inconsistancies
In-Reply-To: <26aae75f-9047-85d9-efa6-21319369619c@geier.ne.tz>
Message-ID: <35293.1604639393@segfault.tristatelogic.com>

In message <26aae75f-9047-85d9-efa6-21319369619c at geier.ne.tz>, 
Frank Habicht <geier at geier.ne.tz> wrote:

>>> So probably the
>>>> domain:         35.203.196.in-addr.arpa
>>> object shouldn't have been allowed to be created / imported from RIPE...
>> 
>> Let me just say at the outset that I may perhaps not be on entirely
>> solid ground here... I may need to drag out my Cricket book and double
>> check this... but my belief at the moment is that what you just said
>> is not actually correct, that DNS is a bit like routing, where a more
>> specific can effectively override a less specific, and that there is
>> nothing to prevent separate and different delegations to both a
>> containing /16 and also to a /24 within that /16.
>
>I have no idea why Cricket ....   ;-)

Cricket Liu co-wrote the (famous?) O'Reilly book titled "DNS and Bind":

https://www.oreilly.com/library/view/dns-and-bind/0596100574/

In the O'Reilly tradition, the book has a woodcut print of an animal on
the front cover, in this case a grasshopper, which is a close relative
of the cricket species... an image that most folks consider to be a sort
of backhanded tribute to the co-author.

Old school geeks tend to refer to O'Reilly technical books just by the
names of the animals on their respective covers, for example the dreaded
O'Reilly "Bat Book", which can easily double as counterbalance to a small
child on any playground seesaw.  (The book may also serve to secure a
car or a small bus from flying off during any tornado.)

>But have to say I agree.
>I was writing what I was writing based on the 2nd paragraph from Anand in
>https://www.ripe.net/ripe/mail/archives/db-wg/2020-October/006687.html
>which maybe I have misinterpreted.

I will go with the more authoritative information source, i.e. the "Cricket
Book".



From comms at afrinic.net  Fri Nov  6 14:45:08 2020
From: comms at afrinic.net (AFRINIC Communication)
Date: Fri, 6 Nov 2020 18:45:08 +0400
Subject: [Community-Discuss] Yet more data base problems/inconsistancies
In-Reply-To: <35293.1604639393@segfault.tristatelogic.com>
References: <35293.1604639393@segfault.tristatelogic.com>
Message-ID: <A1A60763-83F7-4073-B20B-F2CAE4D23D72@afrinic.net>

Dear Community members,

We appreciate your concern around the duplicate domain object in the AFRINIC whois Database. The same was raised and discussed on the DBWG mailing list <https://lists.afrinic.net/pipermail/dbwg/2020-September/000269.html>  

We have been working on this when it came to our attention and we hope to have this resolved and deployed soon. We shall keep the community updated as soon as this has been done.

The domain objects with the trailing dot were previously possible according to RFC 1034. The AFRINIC whois Database however does not allow the creation of this type of domains.

The objects in question cannot be queried via port 43 as the Whois Database automatically removes any trailing dot from the object key.

Regarding the issue with the zone files, we are still investigating and an update will be provided to the community as soon as it is resolved.

Regards,

Ashil Oogarah

On behalf of AFRINIC's IT and Engineering Team


> On 6 Nov 2020, at 09:09, Ronald F. Guilmette <rfg at tristatelogic.com> wrote:
> 
> In message <26aae75f-9047-85d9-efa6-21319369619c at geier.ne.tz>, 
> Frank Habicht <geier at geier.ne.tz> wrote:
> 
>>>> So probably the
>>>>> domain:         35.203.196.in-addr.arpa
>>>> object shouldn't have been allowed to be created / imported from RIPE...
>>> 
>>> Let me just say at the outset that I may perhaps not be on entirely
>>> solid ground here... I may need to drag out my Cricket book and double
>>> check this... but my belief at the moment is that what you just said
>>> is not actually correct, that DNS is a bit like routing, where a more
>>> specific can effectively override a less specific, and that there is
>>> nothing to prevent separate and different delegations to both a
>>> containing /16 and also to a /24 within that /16.
>> 
>> I have no idea why Cricket ....   ;-)
> 
> Cricket Liu co-wrote the (famous?) O'Reilly book titled "DNS and Bind":
> 
> https://www.oreilly.com/library/view/dns-and-bind/0596100574/
> 
> In the O'Reilly tradition, the book has a woodcut print of an animal on
> the front cover, in this case a grasshopper, which is a close relative
> of the cricket species... an image that most folks consider to be a sort
> of backhanded tribute to the co-author.
> 
> Old school geeks tend to refer to O'Reilly technical books just by the
> names of the animals on their respective covers, for example the dreaded
> O'Reilly "Bat Book", which can easily double as counterbalance to a small
> child on any playground seesaw.  (The book may also serve to secure a
> car or a small bus from flying off during any tornado.)
> 
>> But have to say I agree.
>> I was writing what I was writing based on the 2nd paragraph from Anand in
>> https://www.ripe.net/ripe/mail/archives/db-wg/2020-October/006687.html
>> which maybe I have misinterpreted.
> 
> I will go with the more authoritative information source, i.e. the "Cricket
> Book".
> 
> _______________________________________________
> Community-Discuss mailing list
> Community-Discuss at afrinic.net
> https://lists.afrinic.net/mailman/listinfo/community-discuss




From rfg at tristatelogic.com  Sat Nov  7 02:24:35 2020
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Fri, 06 Nov 2020 18:24:35 -0800
Subject: [Community-Discuss] Yet more data base problems/inconsistancies
In-Reply-To: <A1A60763-83F7-4073-B20B-F2CAE4D23D72@afrinic.net>
Message-ID: <55860.1604715875@segfault.tristatelogic.com>

In message <A1A60763-83F7-4073-B20B-F2CAE4D23D72 at afrinic.net>, 
AFRINIC Communication <comms at afrinic.net> wrote:

>We appreciate your concern around the duplicate domain object in the 
>AFRINIC whois Database. The same was raised and discussed on the DBWG 
>mailing list 
><https://lists.afrinic.net/pipermail/dbwg/2020-September/000269.html> 

Just to be sure we are clear, there is not just one duplicate.  By my
count, there are 40 of them.

>We have been working on this when it came to our attention and we hope 
>to have this resolved and deployed soon. We shall keep the community 
>updated as soon as this has been done.
>
>The domain objects with the trailing dot were previously possible 
>according to RFC 1034. The AFRINIC whois Database however does not allow 
>the creation of this type of domains.
>
>The objects in question cannot be queried via port 43 as the Whois 
>Database automatically removes any trailing dot from the object key.
>
>Regarding the issue with the zone files, we are still investigating and 
>an update will be provided to the community as soon as it is resolved.

Thank you for the update.

The apparent differences between the data present in the zone files and
the data present in the published WHOIS with respect to reverse DNS
delegations are most certainly things that I will be happy to know
the cause of, whenever that information becomes available.


Regards,
rfg



From noah at neo.co.tz  Mon Nov  9 08:09:34 2020
From: noah at neo.co.tz (Noah)
Date: Mon, 9 Nov 2020 11:09:34 +0300
Subject: [Community-Discuss] Fwd: [AFRINIC-Announce] Reminder: ASO AC Calls
 For Nominations for Seat 9 on the ICANN Board of Directors
In-Reply-To: <35DA9A6A-B004-4A41-8A11-91B8B64123BE@afrinic.net>
References: <35DA9A6A-B004-4A41-8A11-91B8B64123BE@afrinic.net>
Message-ID: <CAEqgTWbjkpxyByxtqLpB0o5E=gVJc36WDzH=RW9OF+T=Od5RKw@mail.gmail.com>

FYI

---------- Forwarded message ---------
From: AFRINIC Communication <comms at afrinic.net>
Date: Mon, 9 Nov 2020, 11:01
Subject: [AFRINIC-Announce] Reminder: ASO AC Calls For Nominations for Seat
9 on the ICANN Board of Directors
To: <announce at afrinic.net>


Dear colleagues,

In line with the ICANN Address Supporting Organization (ASO) Memorandum of
Understanding (MoU) [1] and the ICANN Bylaws [2], the Address Supporting
Organization Address Council (ASO AC) has issued a call for nominations for
Seat 9 of the ICANN Board of Directors:
https://aso.icann.org/icann-board/icann-board-elections/2021-icann-board-of-directors-seat-9-elections/


The selected candidate will serve for a three-year term, which will begin
at the conclusion of the ICANN Annual General Assembly at the ICANN 72
Meeting, scheduled from 23-28 October 2021 in Seattle, USA.

Eligibility Requirements
------------------------

All nominated candidates must meet the selection criteria and conflict of
interest requirements as outlined in Article 7 of the ICANN Bylaws. The
nominated candidates will undergo a due diligence review by an independent
ICANN contractor.

Nomination Process
------------------

Community members are invited to submit nominations by email to nominations
[at] aso [dot] icann [dot] org by Sunday, 15 November 2020 at 23:59 UTC.

Nominations must include the following information:

- The full name of the person being nominated
- Contact email address of the person being nominated
- Contact telephone number of the person being nominated
- The full name of the person making the nomination
- Contact email address for the person making the nomination
- Contact telephone number of the person making the nomination

Regional Restrictions
---------------------

The ICANN Bylaws state that the Directors selected by a Supporting
Organization (SO) for its assigned Board seat(s) cannot reside in the same
geographic region (see Section 7.2:c). The current ASO AC selection for
Seat 10, Maemura Akinori, resides in the APNIC region. Therefore, no
nominations for Seat 9 can be accepted from candidates residing in the
APNIC region.

Important Dates
---------------

- Nomination Phase: 15 September 2020 ? 15 November 2020
- Comment Phase: 21 December 2020 ? 17 January 2021
- ICANN Due Diligence for nominated candidates
- Interview Phase: 25 January 2021 ? 30 March 2021
- Selection Phase (deliberation): 1 ? 16 April 2021
- Selection Phase (voting): 19 ? 25 April 2021
- Announcement of selected candidate: around 30 April 2021

Further Information
-------------------

More information and updated announcements will be added to to the
dedicated 2021 Seat 9 elections page on the ASO website:
https://aso.icann.org/icann-board/icann-board-elections/2021-icann-board-of-directors-seat-9-elections/


Detailed procedures for election of individuals to the ICANN Board of
Directors by the ASO AC can be found in Section 9 of the ASO AC Operating
Procedures:

https://aso.icann.org/documents/operational-documents/aso-ac-icann-board-selection-procedures/


If you have any questions about the elections or the election process,
please contact secretariat [at] nro [dot] net.


[1] Address Supporting Organization (ASO) Memorandum of Understanding 2019:
https://aso.icann.org/documents/memorandums-of-understanding/

[2] ICANN Bylaws:
https://www.icann.org/resources/pages/governance/bylaws-en

On behalf of the ASO AC
_______________________________________________
Announce mailing list
Announce at afrinic.net
https://lists.afrinic.net/mailman/listinfo/announce
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/community-discuss/attachments/20201109/22cfb304/attachment.html>

From comms at afrinic.net  Mon Nov  9 12:06:04 2020
From: comms at afrinic.net (AFRINIC Communication)
Date: Mon, 9 Nov 2020 16:06:04 +0400
Subject: [Community-Discuss] Participate in the upcoming webinar on DNS Abuse
Message-ID: <8426D56D-6A01-438B-B195-4F4D52C707FA@afrinic.net>

Dear colleagues,

AFRINIC and ICANN have partnered to bring you another informative webinar on DNS Abuse, focusing on the various threats and how to mitigate them.

DNS abuse has evolved to become a security risk affecting the trust end-users have on the Internet.

This webinar will help you understand activities that are categorised as abuse towards the DNS ecosystem. You will also get guidance on how to report and mitigate DNS abuse.

By the end of the session, you should be able to:

	? Understand the activities considered abusive to the Domain Name System
	? Identify solutions and recommendations to mitigate DNS abuse
	? Understand what ICANN  is doing to tackle DNS abuse

Use the following link to register, and don't forget to add the event to your calendar: http://bit.ly/AFRINICWebinar-DNSAbuse

Date: Thursday 12th November 2020

Time:

	? 12:30 UTC (Ghana, Cote D'Ivoire)
	? 13:30 WAT (Nigeria, Cameroon)
	? 14:30 SAST (South Africa, Eswatini, Lesotho)
	? 15:30 EAT (Kenya, Uganda)
	? 16:30 GST (Mauritius, Seychelles)

This webinar will be in English, and a French edition of the webinar will be organised in due course.

We encourage you to share this information with your peers who might be interested or would find this webinar beneficial.

See you at the webinar!

Regards

Ashil Oogarah,

On behalf of AFRINIC IP Academy


From comms at afrinic.net  Fri Nov 13 08:38:11 2020
From: comms at afrinic.net (AFRINIC Communication)
Date: Fri, 13 Nov 2020 12:38:11 +0400
Subject: [Community-Discuss] =?utf-8?q?Participate_in_AFRINIC=27s_next_web?=
 =?utf-8?q?inar_on_=27=27Proceedings_at_AGMMs_=26_Appointment=2C_Removal_a?=
 =?utf-8?q?nd_Powers_of_Directors=E2=80=99=27?=
Message-ID: <F72E8A1C-FC3B-468B-8B6F-483451738F36@afrinic.net>

Dear colleagues,

AFRINIC is pleased to announce its next webinar on ''Proceedings at AGMMs & Appointment, Removal and Powers of Directors?'.

This is the fifth webinar in our series on AFRINIC's Ecosystem and Governance.

Date: Wednesday 18 November 2020

Time:

	? 12:30 UTC (Ghana, Cote D'Ivoire)
	? 13:30 WAT (Nigeria, Cameroon)
	? 14:30 SAST (South Africa, Eswatini, Lesotho)
	? 15:30 EAT (Kenya, Uganda)
	? 16:30 GST (Mauritius, Seychelles)

Language: English

Target: AFRINIC community members and any other person interested in how AFRINIC manages Internet Number Resources in its service region.


At the end of this session participants will be able to:

1- Know about the role of the AGMM chairperson and how he(she) is appointed
2- Understand the why of the AGMM notice
3- Understand the quorum
4- Tell the different ways for voting and who can do so
5- Explain what are proxies and when to use them
6- Know about the eligibility criteria
7- Explain how AFRINIC?s director is appointed
8- Describe the conditions and circumstances for removing a director
9- Identify the powers of the director


Register here: https://bit.ly/AFRINICWebinar-18thNov-Registration <https://us02web.zoom.us/meeting/register/tZcscumrrzMiHdPNPQ1OcQn5FrWFYffmVwl5>

See you at the webinar!


Ashil Oogarah

On behalf of AFRINIC?s Stakeholder?s Engagement Team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/community-discuss/attachments/20201113/6fbad531/attachment.html>

From mark.tinka at seacom.com  Thu Nov 12 15:37:24 2020
From: mark.tinka at seacom.com (Mark Tinka)
Date: Thu, 12 Nov 2020 17:37:24 +0200
Subject: [Community-Discuss] Fwd: [apnic-talk] APRICOT 2021 PC call for
	volunteers
In-Reply-To: <ff231284-362d-c077-8548-60141ced1d15@gmail.com>
References: <ff231284-362d-c077-8548-60141ced1d15@gmail.com>
Message-ID: <a2060ac6-c7e4-6fbb-ec54-10b1e62de4e9@seacom.com>

FYI.

Mark.


-------- Forwarded Message --------
Subject: 	[apnic-talk] APRICOT 2021 PC call for volunteers
Date: 	Thu, 12 Nov 2020 20:37:10 +1000
From: 	Philip Smith <pfsinoz at gmail.com>
Reply-To: 	APRICOT PC Chairs <pc-chairs at apricot.net>
Organization: 	PFS Internet Development Pty Ltd
To: 	apnic-talk at lists.apnic.net
CC: 	APRICOT PC Chairs <pc-chairs at apricot.net>



Hi everyone,

As you will no doubt be aware, due to the COVID-19 pandemic, APRICOT 
2021 has moved on-line.? It will still be hosted, as planned, by PhNOG, 
the Philippine Network Operator Group. The new format means a reduction 
in the schedule but retaining the high quality and high relevancy of the 
content offered over the years.

The APRICOT 2021 Programme Committee is responsible for the solicitation 
and selection of suitable presentation and tutorial content for the 
APRICOT 2021 conference (https://2021.apricot.net/).

The APRICOT PC Chairs are now seeking nominations from the community to 
join the APRICOT 2021 PC to assist with the development of the programme 
for APRICOT 2021.

Eligible PC candidates are those who have attended APRICOT conferences 
in the recent past, have broad technical knowledge of Internet 
operations, and have reasonable familiarity with the format of APRICOT 
conferences.? Having constructive opinions and ideas about how the 
programme content might be improved is of high value too.? PC members 
are expected to work actively to solicit content and review submissions 
for technical merit.? The PC meets by conference call, weekly in 
frequency during the three months prior to APRICOT.

If you are interested in joining the PC and meet the above eligibility 
criteria, please send a brief note to "pc-chairs at apricot.net".? The 
note should include affiliation (if any) and contact details (including 
e-mail address), and a brief description of why you would make a good 
addition to the PC.

The PC Chairs will accept nominations received by 17:00 UTC+8 on Monday 
23rd November 2020, and will announce the new PC shortly thereafter.

Many thanks!

Mark Tinka, Marijana Novakovic & Philip Smith
APRICOT 2021 PC Chairs
-- 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/community-discuss/attachments/20201112/a03e9253/attachment.html>
-------------- next part --------------
_______________________________________________
apnic-talk mailing list
apnic-talk at lists.apnic.net
https://mailman.apnic.net/mailman/listinfo/apnic-talk

From comms at afrinic.net  Fri Nov 13 12:59:16 2020
From: comms at afrinic.net (AFRINIC Communication)
Date: Fri, 13 Nov 2020 16:59:16 +0400
Subject: [Community-Discuss] AFRINIC Blog
Message-ID: <09D3D468-294A-48C6-948C-8BA85EF8FD0A@afrinic.net>

Dear Colleagues,

In this week?s blog, we would like to share a recap of the activities and meetings we have participated and collaborated in regionally since the beginning of the year. 

Enjoy new stories on the AFRINIC Blog here>> https://bit.ly/AFRINICBlog-Collaborations-in-2020

We wish you a pleasant read!

Ashil Oogarah










 





From rfg at tristatelogic.com  Mon Nov 16 03:52:37 2020
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Sun, 15 Nov 2020 19:52:37 -0800
Subject: [Community-Discuss] AFRINIC IP Block Thefts -- The Saga Continues
Message-ID: <28734.1605498757@segfault.tristatelogic.com>

Jan Vermeulen has written a new chapter in this ongoing saga of greed,
theft, and skulduggery.

EXECUTIVE SUMMARY: Maikel Uerlings and Elad Cohen registered a bunch of
new domain names as part of their overall scheme to steal AFRINIC legacy
blocks by fiddling the AFRINIC WHOIS records for the contact persons for
each legacy block that they wanted to steal.  The domain names themselves
were deliberately chosen and tailored to try to minimize suspicion
relating to their numerous legacy block thefts.

https://mybroadband.co.za/news/security/367188-the-great-african-ip-address-heist-south-african-internet-resources-worth-r558-million-usurped-with-shady-domains.html

How exactly these two gentlemen managed to gain the kind of read/write
access to the AFRINIC WHOIS data base which allowed them to fiddle so
many WHOIS records for so many AFRINIC legacy IPv4 blocks is something
that AFRINIC has yet to offer any explanation for, even a full year
after these thefts came to light.


NOTE:  As of the present moment AFRINIC is *still* delegating authority
for reverse DNS for many of the stolen legacy blocks detailed in Jan's
most recent article to name servers that are owned and controled by
Maikel Uerlings and/or Elad Cohen.  In particular, Uerlings and/or Cohen
are still in control of the reverse DNS for all of the stolen legacy
blocks listed in the table below, as well as the reverse DNS for the
very valuable 196.16.0.0/14 block, worth well over $5 million USD.

There is no reasonable excuse for this ongoing inaction by AFRINIC.  As
things stand, it appears that AFRINIC is still refusing to do even the
minimum amount necessary to stop the profiteering of Uerlings and Cohen,
EVEN THOUGH every additional dollar, every additional sheckel, and every
additional ruble that they earn from these ongoing thefts is being used
to fund Cohen's ongoing lawsuit against AFRINIC.

AFRINIC has known about these legacy block thefts for well over a year
now, and yet in all this time AFRINIC has done absolutely nothing to
remediate the fradulent entries in their WHOIS data base, or to remove
the reverse DNS relegations for the 196.16.0.0/14 block and the several
stolen blocks listed below.  Reasonable people can and should ask why.

One theory, currently circulating among people I know is that Mr. Uerlings
and/or Mr. Cohen are in possession of some confidential information that
AFRINIC really hopes will never see the light of day, and that AFRINIC
is being blackmailed into inaction.  Whatever the reason, AFRINIC's
continuing inaction is effectively providing funding for Mr. Cohen's
ongoing lawsuit against AFRINIC.  How this makes any sense at all is
something that remains for AFRINIC to explain.


#------------------------------------------------------------------------
# ORG: (SC) ORG-AISL1-AFRINIC "AECI Information Services (Pty) Ltd"
#------------------------------------------------------------------------
168.80.0.0/15
#------------------------------------------------------------------------
# ORG: (ZA) ORG-AA79-AFRINIC "Agrihold"
#------------------------------------------------------------------------
163.198.0.0/16
#------------------------------------------------------------------------
# ORG: (ZA) ORG-ACSL2-AFRINIC "Affiliated Computing Services (Pty) Ltd"
#------------------------------------------------------------------------
160.116.0.0/16
#------------------------------------------------------------------------
# ORG: (ZA) ORG-FSED1-AFRINIC "Free State Education Department"
#------------------------------------------------------------------------
168.76.0.0/19
168.76.36.0/24
168.76.128.0/20
168.76.144.0/22
168.76.148.0/24
168.76.228.0/22
168.76.232.0/21
168.76.240.0/20
#------------------------------------------------------------------------
# ORG: (ZA) ORG-SCS1-AFRINIC "Safren Computer Services"
#------------------------------------------------------------------------
155.159.0.0/16



From comms at afrinic.net  Mon Nov 16 09:59:55 2020
From: comms at afrinic.net (AFRINIC Communication)
Date: Mon, 16 Nov 2020 13:59:55 +0400
Subject: [Community-Discuss] =?utf-8?q?Reminder=3A_Participate_in_AFRINIC?=
 =?utf-8?q?=27s_next_webinar_on_=27=27Proceedings_at_AGMMs_=26_Appointment?=
 =?utf-8?q?=2C_Removal_and_Powers_of_Directors=E2=80=99=27?=
Message-ID: <11B6D3E1-3F38-420E-9EA5-156C27CF3B08@afrinic.net>

Dear colleagues,

AFRINIC is pleased to announce its next webinar on ''Proceedings at AGMMs & Appointment, Removal and Powers of Directors?'.

This is the fifth webinar in our series on AFRINIC's Ecosystem and Governance.

Date: Wednesday 18 November 2020

Time:

	? 12:30 UTC (Ghana, Cote D'Ivoire)
	? 13:30 WAT (Nigeria, Cameroon)
	? 14:30 SAST (South Africa, Eswatini, Lesotho)
	? 15:30 EAT (Kenya, Uganda)
	? 16:30 GST (Mauritius, Seychelles)

Language: English

Target: AFRINIC community members and any other person interested in how AFRINIC manages Internet Number Resources in its service region.


At the end of this session participants will be able to:

1- Know about the role of the AGMM chairperson and how he(she) is appointed
2- Understand the why of the AGMM notice
3- Understand the quorum
4- Tell the different ways for voting and who can do so
5- Explain what are proxies and when to use them
6- Know about the eligibility criteria
7- Explain how AFRINIC?s director is appointed
8- Describe the conditions and circumstances for removing a director
9- Identify the powers of the director


Register here: https://bit.ly/AFRINICWebinar-18thNov-Registration <https://us02web.zoom.us/meeting/register/tZcscumrrzMiHdPNPQ1OcQn5FrWFYffmVwl5>

See you at the webinar!


Ashil Oogarah

On behalf of AFRINIC?s Stakeholder?s Engagement Team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/community-discuss/attachments/20201116/7e8255b7/attachment.html>

From comms at afrinic.net  Thu Nov 19 06:47:25 2020
From: comms at afrinic.net (AFRINIC Communication)
Date: Thu, 19 Nov 2020 10:47:25 +0400
Subject: [Community-Discuss] Nomination Period Extended - ASO AC Call for
 Nominations for Seat 9 on the ICANN Board of Directors
Message-ID: <F5EE6D73-6B71-47B7-950D-5799056FB0B5@afrinic.net>

[On behalf of the ASO AC]

Dear Colleagues,

The ASO AC has announced today it has extended its deadline for the nomination period for the selection of Seat 9 on the ICANN Board of Directors.

Nominations will now close on Sunday 22 November at 23:59 UTC.

The selected candidate will serve for a three-year term, which will begin at the conclusion of the ICANN Annual General Assembly at the ICANN 72 Meeting, scheduled from 23-28 October 2021.

The election process is described below.

Eligibility Requirements 
------------------------ 

All nominated candidates must meet the selection criteria and conflict of interest requirements as outlined in Article 7 of the ICANN Bylaws[1]. The nominated candidates will undergo a due diligence review by an independent ICANN contractor. 

Nomination Process 
------------------ 

Community members are invited to submit nominations by email to nominations [at] aso [dot] icann [dot] org by Sunday, 22 November 2020 at 23:59 UTC. 

Nominations must include the following information: 

- The full name of the person being nominated 
- Contact email address of the person being nominated 
- Contact telephone number of the person being nominated 
- The full name of the person making the nomination 
- Contact email address for the person making the nomination 
- Contact telephone number of the person making the nomination 

Regional Restrictions 
--------------------- 

The ICANN Bylaws state that the Directors selected by a Supporting Organization (SO) for its assigned Board seat(s) cannot reside in the same geographic region (see Section 7.2:c). The current ASO AC selection for Seat 10, Maemura Akinori, resides in the APNIC region. Therefore, no nominations for Seat 9 can be accepted from candidates residing in the APNIC region. 

Important Dates 
--------------- 

- Nomination Phase: 15 September 2020 ? 22 November 2020 
- Comment Phase: 21 December 2020 ? 17 January 2021 
- ICANN Due Diligence for nominated candidates 
- Interview Phase: 25 January 2021 ? 30 March 2021 
- Selection Phase (deliberation): 1 ? 16 April 2021 
- Selection Phase (voting): 19 ? 25 April 2021 
- Announcement of selected candidate: around 30 April 2021 

Further Information 
------------------- 

More information and updated announcements will be added to the dedicated 2021 Seat 9 elections page on the ASO website: 
https://aso.icann.org/icann-board/icann-board-elections/2021-icann-board-of-directors-seat-9-elections/ <https://aso.icann.org/icann-board/icann-board-elections/2021-icann-board-of-directors-seat-9-elections/> 

Detailed procedures for election of individuals to the ICANN Board of Directors by the ASO AC can be found in Section 9 of the ASO AC Operating Procedures: 
https://aso.icann.org/documents/operational-documents/aso-ac-icann-board-selection-procedures/ <https://aso.icann.org/documents/operational-documents/aso-ac-icann-board-selection-procedures/> 

If you have any questions about the elections or the election process, please contact secretariat [at] nro [dot] net. 

[1] ICANN Bylaws:
https://www.icann.org/resources/pages/governance/bylaws-en <https://www.icann.org/resources/pages/governance/bylaws-en>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/community-discuss/attachments/20201119/a4da6095/attachment.html>

From comms at afrinic.net  Thu Nov 19 11:43:14 2020
From: comms at afrinic.net (AFRINIC Communication)
Date: Thu, 19 Nov 2020 15:43:14 +0400
Subject: [Community-Discuss] Call for Volunteers on the ASO AC/NRO NC
Message-ID: <A709A686-DFAC-4B08-B57F-F851394654EB@afrinic.net>


[French, Arabic and Portuguese versions below]

Dear AFRINIC members and community,

The AFRINIC Board hereby calls for volunteers who wish to be considered for appointment to the ASO AC/NRO NC.
One of the three AFRINIC representatives in the NRO NC is appointed by the AFRINIC Board, and the Board intends to appoint one community volunteer for a one-year term, from 1 January 2021 to 31 December 2021. The current Board Appointee to the NRO NC / ASO AC is Mrs Wafa Dahmani and her term is due to end on 31 December 2020.

The responsibilities for the ASO AC/NRO NC include:

	? Overseeing the Global Policy Development Process (GPDP).
	? Providing recommendations to the ICANN Board concerning the recognition of new RIRs.
	? Defining procedures to appoint Directors to serve in the ASO?s two seats (Seat 9 and Seat 10) on the ICANN Board of Directors and to serve on other ICANN bodies.
	? Providing advice to the ICANN Board on Internet number resource allocation policy, in conjunction with the RIRs.
	? Developing procedures for conducting business in support of their responsibilities, in particular for the appointment of an ASO AC Chair and definition of the Chair?s responsibilities.

Volunteers for the NRO NC/ASO AC seat are invited to send a brief biography, and their reasons for seeking appointment, to legal at afrinic.net <http://afrinic.net/>, no later than 23:59 UTC on 18 December 2020. Existing appointees for the NRO NC/ASO AC seats are eligible to volunteer for re-appointment.


Subramanian Moonesamy

AFRINIC Board Chairman

??????????????????.

Chers membres et communaut? AFRINIC,

Le conseil d'administration de l'AFRINIC lance un appel aux volontaires qui souhaitent ?tre pris en consid?ration pour une nomination ? l'ASO AC/NRO NC.

Un des trois repr?sentants de l'AFRINIC au sein du NRO NC est nomm? par le conseil d'administration de l'AFRINIC, et le conseil d'administration a l'intention de nommer un volontaire de la communaut? pour un mandat d'un an, du 1er janvier 2021 au 31 d?cembre 2021. La personne actuellement nomm?e au conseil d'administration du NRO NC / ASO AC est Mme Wafa Dahmani et son mandat doit prendre fin le 31 d?cembre 2020.

Les responsabilit?s du Comit? consultatif de l'ASO et du Comit? national de l'ORN sont les suivantes:

	- Superviser le processus d'?laboration des politiques mondiales (GPDP).
	- Fournir des recommandations au conseil d'administration de l'ICANN concernant la reconnaissance des nouveaux RIR.
	- D?finir les proc?dures de nomination des directeurs pour les deux si?ges de l'ASO (si?ge 9 et si?ge 10) au conseil d'administration de l'ICANN et pour les autres organes de l'ICANN.
	- Fournir des conseils au conseil d'administration de l'ICANN sur la politique d'attribution des ressources de num?ros Internet, en liaison avec les RIR.
	- D?velopper des proc?dures pour la conduite des affaires ? l`appui de leurs responsabilit?s, en particulier pour la nomination d`un pr?sident de l`ASO AC et la d?finition des responsabilit?s du pr?sident.

Les volontaires pour le si?ge du NRO NC/ASO AC sont invit?s ? envoyer une br?ve biographie, ainsi que les raisons de leur candidature, ? legal at afrinic.net <http://afrinic.net/>, au plus tard ? 23:59 UTC le 18 d?cembre 2020. Les personnes d?j? nomm?es pour les si?ges du NRO NC/ASO AC peuvent se porter volontaires pour un nouveau mandat.

Subramanian Moonesamy

AFRINIC Board Chairman

??????????????????????????

?????? ????? ?????? AFRINIC ?

???? ???? AFRINIC ????? ??? ????????? ????? ?????? ?? ????? ?? ??????? ?? ASO AC / NRO NC.
??? ????? ??? ????? AFRINIC ??????? ?? NRO NC ?? ??? ???? ????? AFRINIC ? ?????? ?????? ????? ????? ???? ?? ??????? ???? ??? ???? ? ?? 1 ????? 2021 ??? 31 ?????? 2021. ??? ???? ??????? ?????? ?????? ?? NRO NC / ASO AC ?? ?????? ???? ???????? ?????? ??????? ?? 31 ?????? 2020.

???? ???????? ASO AC / NRO NC ?? ???:

? ??????? ??? ????? ????? ??????? ???????? (GPDP).
? ????? ?????? ??? ???? ????? ICANN ???? ????? ????????? ?????? ???????? ????????? ???????.
? ????? ??????? ????? ???????? ????? ?? ????? ASO (?????? 9 ??????? 10) ?? ???? ????? ICANN ?????? ?? ????? ICANN ??????.
? ????? ??????? ??? ???? ????? ICANN ???? ????? ????? ????? ??? ???????? ? ???????? ?? RIRs.
? ????? ??????? ??????? ??????? ???? ?????????? ? ??? ???? ?????? ???? ASO AC ?????? ???????? ??????.

??? ???? ????????? ?? ???? NRO NC / ASO AC ?????? ???? ????? ????? ? ?????? ????? ??????? ? ??? ??????? ???????? ?? ???? afrinic.net <http://afrinic.net/> ? ?? ???? ?? ?????? 23:59 ???????? ??????? ?????? ?? 18 ?????? 2020. ???????? ???????? ?? NRO NC / ????? ASO AC ????? ?????? ?????? ???????.

Subramanian Moonesamy

AFRINIC Board Chairman

??????????????????????????.


Caros membros e comunidade AFRINIC,

O Conselho AFRINIC convoca por este meio os volunt?rios que desejem ser considerados para nomea??o para a ASO AC/NRO NC.
Um dos tr?s representantes da AFRINIC no NRO NC ? nomeado pelo Conselho da AFRINIC, e o Conselho pretende nomear um volunt?rio comunit?rio para um mandato de um ano, de 1 de Janeiro de 2021 a 31 de Dezembro de 2021. A actual nomeada para o NRO NC / ASO AC ? a Sra. Wafa Dahmani e o seu mandato termina a 31 de Dezembro de 2020.

As responsabilidades para a ASO AC/NRO NC incluem:

	- Supervisionar o Processo de Desenvolvimento de Pol?ticas Globais (GPDP).
	- Fornecer recomenda??es ? junta da ICANN relativamente ao reconhecimento de novos RIRs.
	- Definir procedimentos para nomear Directores para servirem nos dois lugares da ASO (Sede 9 e Sede 10) na Junta de Directores de ICANN e para servirem em outros ?rg?os de ICANN.
	- Prestar aconselhamento ? Junta de ICANN sobre a pol?tica de atribui??o de recursos de n?meros da Internet, em conjunto com os RIRs.
	- Desenvolver procedimentos para a realiza??o de neg?cios de apoio ?s suas responsabilidades, em particular para a nomea??o de um Presidente da ASO AC e defini??o das responsabilidades do Presidente.

Os volunt?rios para a sede da NRO NC/ASO AC s?o convidados a enviar uma breve biografia, e as suas raz?es para procurar nomea??o, para o endere?o legal afrinic.net <http://afrinic.net/>, at? ?s 23:59 UTC de 18 de Dezembro de 2020. Os actuais nomeados para os lugares da NRO NC/ASO AC s?o eleg?veis para se voluntariarem para uma nova nomea??o.

Subramanian Moonesamy

AFRINIC Board Chairman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/community-discuss/attachments/20201119/cfe0f093/attachment.html>

From comms at afrinic.net  Thu Nov 19 12:42:31 2020
From: comms at afrinic.net (AFRINIC Communication)
Date: Thu, 19 Nov 2020 16:42:31 +0400
Subject: [Community-Discuss] Call for Volunteers on the Governance Committee
Message-ID: <FE79E480-DB5D-4F76-B92B-A0539A5ABDA9@afrinic.net>

[French, Arabic and Portuguese versions below]

Dear AFRINIC Members and Community,

The AFRINIC Governance Committee advises the AFRINIC Board, AFRINIC Membership and the community on matters of corporate governance. For more information, see <https://afrinic.net/committees/governance-committee <https://afrinic.net/committees/governance-committee>>. 

Two of the five voting members of the Governance Committee are appointed by the Board, and one of those seats has a term that expires on 31 December 2020. The Board intends to fill the seat by appointing a community volunteer for a two-year term from 1 January 2021 to 31 December 2022. The current Board Appointee to the Governance Committee whose term is due to expire on the 31 December 2020 is Mr Justin Rugondihene.

Volunteers are invited to send a brief biography, and their reasons for seeking appointment, to legal at afrinic.net <http://afrinic.net/>, no later than 23:59 UTC on 18 December 2020. Existing appointees are eligible to volunteer for re-appointment.


Subramanian Moonesamy

AFRINIC Board Chairman

??????????????????

Chers membres de l'AFRINIC et de la Communaut?,

Le comit? de gouvernance AFRINIC conseille le conseil d'administration, les membres de l'AFRINIC et la communaut? sur les questions de gouvernance d'entreprise. Pour plus d'informations, voir <https://afrinic.net/committees/governance-committee <https://afrinic.net/committees/governance-committee>>. 

Deux des cinq membres votants du comit? de gouvernance sont nomm?s par le conseil d'administration, et l'un de ces si?ges a un mandat qui expire le 31 d?cembre 2020. Le conseil d'administration a l'intention de pourvoir ce si?ge en nommant un b?n?vole de la communaut? pour un mandat de deux ans, du 1er janvier 2021 au 31 d?cembre 2022. L'actuel membre nomm? au comit? de gouvernance dont le mandat doit expirer le 31 d?cembre 2020 est M. Justin Rugondihene.

Les volontaires sont invit?s ? envoyer une br?ve biographie, ainsi que les raisons pour lesquelles ils souhaitent ?tre nomm?s, ? legal at afrinic.net <http://afrinic.net/>, au plus tard ? 23h59 UTC le 18 d?cembre 2020. Les personnes d?j? nomm?es peuvent se porter volontaires pour une nouvelle nomination.

Subramanian Moonesamy

AFRINIC Board Chairman

????????????

?????? ????? ?????? AFRINIC ?

???? ???? ??????? AFRINIC ??????? ????? ????? AFRINIC ?????? AFRINIC ???????? ???? ????? ????? ???????. ????? ?? ????????? ? ???? <https://afrinic.net/committee/governance-committee <https://afrinic.net/committee/governance-committee>>.

??? ????? ????? ?? ??????? ?????? ???????? ?? ???? ??????? ?? ??? ???? ??????? ? ?????? ??? ??? ??? ??????? ?? 31 ?????? 2020. ????? ???? ??????? ??? ?????? ?? ???? ????? ????? ?????? ???? ????? ?? ?? 1 ????? 2021 ??? 31 ?????? 2022. ????? ?????? ?????????? ?? ????? ?????? ?????? ?? ???? ??????? ?? ???? ??????? ????? ?? ?????? ?? ????? ???? ?? 31 ?????? 2020.

????????? ?????? ?????? ???? ????? ????? ? ?????? ????? ??????? ? ??? ??????? ???????? ??? ???? afrinic.net <http://afrinic.net/> ? ?? ???? ?? ?????? ?????? 23:59 ???????? ??????? ?????? ?? 18 ?????? 2020. ???????? ???????? ?????? ?????? ?????? ???????.

Subramanian Moonesamy

AFRINIC Board Chairman

????????????..

Caros Membros AFRINIC e Comunidade,

O Comit? de Governa??o AFRINIC aconselha o Conselho AFRINIC, os membros AFRINIC e a comunidade em quest?es de governa??o empresarial. Para mais informa??es, ver <https://afrinic.net/committees/governance-committee <https://afrinic.net/committees/governance-committee>>. 

Dois dos cinco membros votantes da Comiss?o de Governa??o s?o nomeados pelo Conselho de Administra??o, e um desses lugares tem um mandato que termina a 31 de Dezembro de 2020. O Conselho de Administra??o pretende preencher o lugar nomeando um volunt?rio da comunidade para um mandato de dois anos, de 1 de Janeiro de 2021 a 31 de Dezembro de 2022. O actual nomeado do Conselho de Administra??o para a Comiss?o de Governa??o cujo mandato expira a 31 de Dezembro de 2020 ? o Sr. Justin Rugondihene.

Os volunt?rios s?o convidados a enviar uma breve biografia, e as suas raz?es para procurar nomea??o, legal at afrinic.net <http://afrinic.net/>, o mais tardar at? ?s 23:59 UTC de 18 de Dezembro de 2020. Os nomeados j? existentes s?o eleg?veis para se voluntariarem para uma nova nomea??o.

Subramanian Moonesamy

AFRINIC Board Chairman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/community-discuss/attachments/20201119/2a5369c0/attachment.html>

From comms at afrinic.net  Thu Nov 19 14:06:07 2020
From: comms at afrinic.net (AFRINIC Communication)
Date: Thu, 19 Nov 2020 18:06:07 +0400
Subject: [Community-Discuss] Call for Volunteers on the Nomination Committee
	(NomCom) 2021
Message-ID: <C100F115-C6CC-4D81-BD06-8D6E17DD77BE@afrinic.net>

[French, Arabic and Portuguese versions below]

Dear AFRINIC members and community,

The AFRINIC Board is required to appoint a Nomination Committee (NomCom) every year, in terms of article 9 of the Bylaws <https://afrinic.net/bylaws#nomcom>>.

On behalf of the Board, I hereby call for volunteers from the community to fill three open positions on the 2021 NomCom. If you are interested in serving on the 2021 NomCom, then please send your expression of interest, including a short biography, by email to legal at afrinic dot net by 18 December 2020 (23:59 UTC).

However, as per Article 9.1 of the Bylaws, no person domiciled in a region whose Board seat is open for renewal may be a member of the Nomcom.

The duties of the NomCom, and the elections to be held are described below.

Election process and guidelines

The current version of the Board election process and guidelines are published at  <https://afrinic.net/election-process/board/2020>>. It provides additional information about NomCom responsibilities, the election process, and timelines.

Nomcom Composition and Responsibilities:

According to Section 9 of the AFRINIC by-laws, a Nominations Committee (NomCom) appointed by the Board must work to ensure that appropriate candidates are nominated to contest for open seats and that all elections are successfully conducted according to current procedures.

The AFRINIC Bylaws state that NomCom must have four members, appointed by the Board. The Board?s practice is to appoint the four members as follows;

- One member selected from within the AFRINIC Board;
- Three members selected by the AFRINIC Board from the community.

In terms of section 9.1 of the Bylaws:
- No candidate for election to the Board may be a member of the NomCom;
- No person domiciled in a region whose Board seat is open for renewal may be a member of the NomCom; this means that the 2021 NomCom may not include people who reside in the Southern Africa region.

Responsibilities of the NomCom are defined in section 9 of the AFRINIC Bylaws and include the following:

- Report to the Board and follow guidelines set by the Board;
- Call for candidates for all open positions;
- Prescribe criteria and qualifications for eligibility to stand for election;
- Interview candidates, if appropriate, prior to finalising the slate of candidates;
- Finalise the list of candidates for every election;
- Supervise the conduct of the polls by the Election Committee on election day.

The Board further expects NomCom members to:

- be neutral; to have no interest in the results of the elections;
- be trusted members of the AFRINIC community;
- have good knowledge of the AFRINIC business environment;
- preferably possess prior NomCom experience in the I* ecosystem;
- do their best to fulfil their responsibilities.

NomCom members do not receive any remuneration.

AFRINIC staff will provide logistical support to the NomCom throughout their mandate. Such support includes publication of the list of nominees, a compilation of comments, mailing list moderation, website update, communication with nominees and other duties pertaining to the roles and responsibilities of the NomCom. Travel support will be provided for the NomCom Chair to attend the AGMM at which the elections are held.

Election to be held at the AGMM 2021:

AFRINIC Board of Directors elections:

The following Board seat is up for election by the AFRINIC Membership in 2021:

? Seat 5 (Southern Africa), to serve a three-year term from mid-2021 to mid-2024. This seat is currently held by Mr Vika William Mpisane

Policy Development Working Group (PDWG):
One PDWG co-chair position is up for election by the Policy Development Working Group.The seat is currently filled by Mr 
Moses Serugo. Terms begin and end during the public policy meeting where the election is held.

Governance Committee:
One Governance Committee position is up for election by the AFRINIC Membership, to serve a three-year term from 1 January 2022 to 31 December 2024. The seat is currently held by Dr Alioune Badara Traore.


How to Volunteer:

If  you are interested in serving on the 2021 NomCom, then please send your expression of interest, including a short biography, by email to legal at afrinic dot net by 18 December 2020 (23:59 UTC). 


Subramanian Moonesamy

AFRINIC Board Chairman

????????????????????????????????????.


Chers membres et communaut? AFRINIC,

Le conseil d'administration de l'AFRINIC est tenu de nommer chaque ann?e un comit? de nomination (NomCom), conform?ment ? l'article 9 des statuts <https://afrinic.net/bylaws#nomcom>>.

Au nom du conseil d'administration, je lance un appel ? des volontaires de la communaut? pour remplir trois postes vacants au sein du NomCom 2021. Si vous ?tes int?ress? ? servir au NomCom 2021, veuillez envoyer votre manifestation d'int?r?t, y compris une courte biographie, par courriel ? legal at afrinic dot net au plus tard le 18 d?cembre 2020 (23:59 UTC).

Toutefois, conform?ment ? l'article 9.1 des statuts, aucune personne domicili?e dans une r?gion dont le si?ge au conseil d'administration est ouvert au renouvellement ne peut ?tre membre du Nomcom.

Les fonctions de la NomCom et les ?lections ? tenir sont d?crites ci-dessous.

Processus d'?lection et directives

La version actuelle du processus d'?lection du conseil d'administration et les lignes directrices sont publi?es sur <https://afrinic.net/election-process/board/2020>>. Elle fournit des informations suppl?mentaires sur les responsabilit?s du NomCom, le processus d'?lection et les d?lais.

Composition et responsabilit?s du NomCom :

Conform?ment ? la section 9 des statuts d'AFRINIC, un comit? de nomination (NomCom) nomm? par le conseil d'administration doit veiller ? ce que des candidats appropri?s soient propos?s pour les si?ges vacants et que toutes les ?lections soient men?es ? bien conform?ment aux proc?dures en vigueur.

Les statuts de l'AFRINIC stipulent que le NomCom doit ?tre compos? de quatre membres, nomm?s par le Conseil d'administration. La pratique du Conseil d'administration est de nommer les quatre membres comme suit ;

- Un membre choisi au sein du conseil d'administration d'AFRINIC ;
- Trois membres choisis par le conseil d'administration de l'AFRINIC parmi la communaut?.

En vertu de la section 9.1 des statuts :
- Aucun candidat ? l'?lection au conseil d'administration ne peut ?tre membre du NomCom ;
- Aucune personne domicili?e dans une r?gion dont le si?ge au Conseil d'administration est ouvert au renouvellement ne peut ?tre membre de la NomCom ; cela signifie que la NomCom 2021 ne peut pas inclure des personnes r?sidant dans la r?gion de l'Afrique australe.

Les responsabilit?s du NomCom sont d?finies dans la section 9 des statuts de l'AFRINIC et comprennent ce qui suit :

- Rendre compte au conseil d'administration et suivre les directives fix?es par ce dernier ;
- Lancer un appel ? candidatures pour tous les postes ouverts ;
- Prescrire les crit?res et les qualifications pour l'?ligibilit? aux ?lections ;
- Interviewer les candidats, le cas ?ch?ant, avant de finaliser la liste des candidats ;
- Finaliser la liste des candidats pour chaque ?lection ;
- Superviser le d?roulement du scrutin par la commission ?lectorale le jour de l'?lection.

Le conseil d'administration attend en outre des membres de la NomCom qu'ils

- soient neutres ; n'aient aucun int?r?t dans les r?sultats des ?lections ;
- soient des membres de confiance de la communaut? AFRINIC ;
- aient une bonne connaissance de l'environnement commercial de l'AFRINIC ;
- poss?der de pr?f?rence une exp?rience pr?alable du NomCom dans l'?cosyst?me I* ;
- faire de leur mieux pour assumer leurs responsabilit?s.

Les membres de la NomCom ne re?oivent aucune r?mun?ration.

Le personnel d'AFRINIC fournira un soutien logistique au NomCom tout au long de son mandat. Ce soutien comprend la publication de la liste des candidats, une compilation des commentaires, la mod?ration de la liste de diffusion, la mise ? jour du site web, la communication avec les candidats et d'autres t?ches relatives aux r?les et responsabilit?s du NomCom. Une aide au d?placement sera fournie au pr?sident du NomCom pour lui permettre d'assister ? l'assembl?e g?n?rale annuelle au cours de laquelle les ?lections auront lieu.

L'?lection aura lieu lors de l'AGA 2021 :

?lections du conseil d'administration de l'AFRINIC :

Les si?ge suivant du Conseil d'administration est ? ?lire par les membres de l'AFRINIC en 2021 :

- Si?ge 5 (Afrique australe), pour un mandat de trois ans, de la mi-2021 ? la mi-2024. Ce si?ge est actuellement occup? par M. Vika William Mpisane

Groupe de travail sur l'?laboration des politiques (PDWG) :
Un poste de copr?sident du PDWG est ? pourvoir par le groupe de travail sur l'?laboration des politiques. 
Le si?ge est actuellement occup? par M. Moses Serugo.. Les mandats commencent et se terminent pendant la r?union de politique publique o? se tient l'?lection.

Comit? de gouvernance :
Un poste du Comit? de gouvernance est soumis ? l'?lection des membres de l'AFRINIC, pour un mandat de trois ans, du 1er janvier 2022 au 31 d?cembre 2024. Le si?ge est actuellement occup? par le Dr Alioune Badara Traor?.

Comment devenir volontaire :

Si vous ?tes int?ress? ? si?ger au NomCom 2021, veuillez envoyer votre manifestation d'int?r?t, accompagn?e d'une courte biographie, par courriel ? legal at afrinic dot net au plus tard le 18 d?cembre 2020 (23:59 UTC).


Subramanian Moonesamy

AFRINIC Board Chairman

??????????????????????.

?????? ????? ?????? AFRINIC ?

????? ??? ???? ????? AFRINIC ????? ???? ????? (NomCom) ?? ??? ? ????? ?????? 9 ?? ??????? ???????? <https://afrinic.net/bylaws#nomcom >>.

???????? ?? ???? ??????? ? ???? ????????? ?? ??????? ???? ????? ????? ????? ?? ???? ??????? 2021. ??? ??? ?????? ??????? ?? NomCom 2021 ? ??????? ????? ?????? ?? ???????? ? ??? ?? ??? ???? ????? ????? ? ??? ?????? ?????????? ??? legal at afrinic dot net ????? 18 ?????? 2020.

??? ??? ? ????? ?????? 9.1 ?? ??????? ???????? ? ?? ???? ??? ??? ???? ?? ????? ???? ???? ???? ??????? ??????? ??????? ?? ???? ????? ?? Nomcom.

???? ???? ??????? ??????????? ???? ????? ????? ?????.

????? ?????????? ???????? ?????????

??? ??? ??????? ?????? ?? ????? ?????? ???? ??????? ???????? ????????? ??? <https://afrinic.net/election-process/board/2020 >>. ???? ??????? ?????? ??? ???????? NomCom ?????? ???????? ???????? ???????.

????? Nomcom ???????????:

????? ????? 9 ?? ??????? ???????? ?? AFRINIC ? ??? ?? ???? ???? ????????? (NomCom) ??????? ?? ??? ???? ??????? ??? ???? ????? ???????? ????????? ??????? ??? ??????? ???????? ??? ???? ?????????? ??? ????? ????? ????????? ???????.

??? ????? AFRINIC ???????? ??? ?? ???? ??? NomCom ????? ????? ? ??? ??????? ?? ??? ???? ???????. ????? ?????? ?????? ?? ????? ??????? ??????? ??? ????? ?????? ?

- ??? ???? ??? ??????? ?? ???? ???? ????? AFRINIC.
- ????? ????? ??????? ???? AFRINIC ?? ???????.

???? ????? ?????? 9.1 ?? ???????:
- ?? ???? ??? ???? ??????? ?????? ?? ???? ????? ?? NomCom ?
- ?? ???? ??? ??? ???? ?? ????? ???? ???? ???? ??????? ??????? ??????? ?? ???? ????? ?? NomCom ? ??? ???? ?? 2021 NomCom ?? ?? ???? ??????? ?????? ?? ????? ???? ???????.

?? ????? ???????? ???? ??????? ?? ????? 9 ?? ????? AFRINIC ?????? ?? ???:

- ????? ????? ??? ???? ??????? ?????? ????????? ???? ????? ?????? ?
- ???? ???????? ????? ??????? ???????.
- ????? ?????? ??????? ??????? ?????? ??????????.
- ?????? ???????? ? ??? ??? ??? ??????? ? ??? ???????? ?? ????? ???????? ?
- ??????? ????? ???????? ??? ????????.
- ??????? ??? ??? ???????? ?? ??? ???? ?????????? ??? ??????????.

????? ???? ??????? ???? ?? ????? NomCom:

- ?? ?????? ? ??? ???????? ?????? ?????????? ?
- ?? ?????? ????? ??????? ?? ????? AFRINIC ?
- ????? ????? ???? ????? ??????? AFRINIC ?
- ???? ?????? ???? ????? ?? NomCom ?? ?????? ?????? I * ?
- ??? ????? ????? ?????? ???????????.

?? ????? ????? NomCom ?? ??????.

????? ????? AFRINIC ????? ???????? ????? ??????? ???? ???? ???????. ????? ??? ????? ??? ????? ???????? ? ?????? ????????? ? ?????? ??????? ???????? ? ?????? ???? ????? ? ???????? ?? ???????? ????????? ?????? ???????? ?????? ????????? ???? ???????. ???? ????? ??? ????? ????? NomCom ????? ?????? AGMM ???? ????? ??? ??????????.

?????????? ???? ????? ?? AGMM 2021:

???????? ???? ????? AFRINIC:

????? ???? ??????? ??????? ???? ???????? ?? ??? ????? AFRINIC ?? ??? 2021:

? ?????? 5 (???? ???????) ? ???? ???? ????? ?? ????? 2021 ??? ????? 2024. ???? ??? ?????? ?????? ????? ???? ?????? ??????

?????? ??? ????? ???????? (PDWG):
???? ???? ???? ????? ?? PDWG ??? ???????? ?? ??? ?????? ??? ????? ????????
???? ??????. ???? ?????? ?????? ???? ?????? ??????? ?????? ??? ??? ????? ??????????.

???? ???????:
???? ???? ???? ?? ???? ??????? ??? ???????? ?? ??? ????? AFRINIC ???? ???? ????? ?? 1 ????? 2022 ??? 31 ?????? 2024. ????? ?????? ?????? ??????? ????? ????? ??????.


??? ?????:

??? ??? ?????? ??????? ?? NomCom 2021 ? ??????? ????? ?????? ?? ???????? ? ??? ?? ??? ???? ????? ????? ? ??? ?????? ?????????? ??? legal ?? afrinic dot net ????? 18 ?????? 2020.


Subramanian Moonesamy

AFRINIC Board Chairman

??????????????..


Caros membros e comunidade AFRINIC,

O Conselho AFRINIC deve nomear anualmente um Comit? de Nomea??o (NomCom), nos termos do artigo 9 dos Estatutos <https://afrinic.net/bylaws#nomcom>>>.

Em nome do Conselho, convido os volunt?rios da comunidade a preencher tr?s vagas em aberto no NomCom de 2021. Se estiver interessado em servir no NomCom 2021, envie por favor a sua manifesta??o de interesse, incluindo uma breve biografia, por e-mail para o endere?o legal afrinic dot net at? 18 de Dezembro de 2020 (23:59 UTC).

Contudo, de acordo com o artigo 9.1 dos Estatutos, nenhuma pessoa domiciliada numa regi?o cujo lugar no Conselho de Administra??o esteja aberto para renova??o pode ser membro do Nomcom.

Os deveres do NomCom, e as elei??es a realizar, s?o descritos abaixo.

Processo eleitoral e orienta??es

A vers?o actual do processo eleitoral do Conselho de Administra??o e as directrizes s?o publicadas em <https://afrinic.net/election-process/board/2020>>>. Fornece informa??o adicional sobre as responsabilidades do NomCom, o processo eleitoral, e os prazos.

Composi??o e Responsabilidades do Nomcom:

De acordo com a Sec??o 9 dos estatutos da AFRINIC, um Comit? de Nomea??es (NomCom) nomeado pelo Conselho de Administra??o deve trabalhar para assegurar que os candidatos apropriados sejam nomeados para concorrer a lugares abertos e que todas as elei??es sejam conduzidas com sucesso, de acordo com os procedimentos actuais.

Os estatutos da AFRINIC estabelecem que o NomCom deve ter quatro membros, nomeados pelo Conselho de Administra??o. A pr?tica do Conselho ? a de nomear os quatro membros da seguinte forma;

- Um membro seleccionado no seio do Conselho AFRINIC;
- Tr?s membros seleccionados pelo Conselho de AFRINIC da comunidade.

Nos termos da sec??o 9.1 dos Estatutos:
- Nenhum candidato ? elei??o para o Conselho de Administra??o pode ser membro do NomCom;
- Nenhuma pessoa domiciliada numa regi?o cujo lugar no Conselho de Administra??o esteja aberto para renova??o pode ser membro do NomCom; isto significa que o NomCom 2021 n?o pode incluir pessoas que residam na regi?o da ?frica Austral.

As responsabilidades do NomCom s?o definidas na sec??o 9 dos Estatutos da AFRINIC e incluem o seguinte:

- Reportar ao Conselho de Administra??o e seguir as orienta??es estabelecidas pelo Conselho de Administra??o;
- Convoca??o de candidatos para todos os cargos em aberto;
- Prescrever crit?rios e qualifica??es de elegibilidade para se candidatar a elei??es;
- Entrevistar os candidatos, se for caso disso, antes de finalizar a lista de candidatos;
- Concluir a lista de candidatos para cada elei??o;
- Supervisionar a condu??o das sondagens pela Comiss?o Eleitoral no dia das elei??es.

A Direc??o espera ainda que os membros do NomCom o fa?am:

- sejam neutros; n?o tenham qualquer interesse nos resultados das elei??es;
- Sejam membros de confian?a da comunidade AFRINIC;
- tenham um bom conhecimento do ambiente empresarial da AFRINIC;
- possuam de prefer?ncia experi?ncia anterior do NomCom no ecossistema I*;
- fazer o seu melhor para cumprir as suas responsabilidades.

Os membros do NomCom n?o recebem qualquer remunera??o.

O pessoal da AFRINIC prestar? apoio log?stico ao NomCom ao longo de todo o seu mandato. Tal apoio inclui a publica??o da lista de nomeados, uma compila??o de coment?rios, modera??o da lista de correio, actualiza??o do website, comunica??o com os nomeados e outros deveres relacionados com as fun??es e responsabilidades do NomCom. Ser? fornecido apoio em viagem para o Presidente do NomCom assistir ? AGMM em que se realizam as elei??es.

Elei??o a ter lugar na AGMM 2021:

Elei??es para o Conselho de Administra??o da AFRINIC:

Os seguintes lugares no Conselho de Administra??o est?o prontos para elei??o pelos membros da AFRINIC em 2021:

- Lugar 5 (?frica Austral), para um mandato de tr?s anos, de meados de 2021 a meados de 2024. Este lugar ? actualmente ocupado pelo Sr. Vika William Mpisane

Grupo de Trabalho para o Desenvolvimento de Pol?ticas (PDWG):
Um lugar de co-presidente do PDWG est? pronto para elei??o pelo Grupo de Trabalho de Desenvolvimento de Pol?ticas, actualmente ocupado pelo Sr. 
Mois?s Serugo. Os termos come?am e terminam durante a reuni?o de pol?tica p?blica onde a elei??o ? realizada.

Comiss?o de Governa??o:
Uma posi??o da Comiss?o de Governa??o ? para elei??o pelos membros da AFRINIC, para um mandato de tr?s anos, de 1 de Janeiro de 2022 a 31 de Dezembro de 2024. A sede ? actualmente ocupada pelo Dr. Alioune Badara Traore.


Como ser volunt?rio:

Se estiver interessado em servir no NomCom 2021, envie por favor a sua manifesta??o de interesse, incluindo uma pequena biografia, por e-mail para o endere?o legal at afrinic dot net at? 18 de Dezembro de 2020 (23:59 UTC).


Subramanian Moonesamy

AFRINIC Board Chairman




From eddy at afrinic.net  Thu Nov 19 17:17:46 2020
From: eddy at afrinic.net (Eddy Kayihura)
Date: Thu, 19 Nov 2020 21:17:46 +0400
Subject: [Community-Discuss] Monthly Update November 2020
Message-ID: <3eac9b1e-f4ce-6465-eca8-0c59d5ddc427@afrinic.net>

[French, Arabic and Portuguese versions below]

Dear Colleagues,

I hope that you are all keeping well. It is that time that I share with
you the monthly updates.

AFRINIC Strategic Plan 2021-2023

I am glad to announce the launch of the AFRINIC Strategic Plan
2021-2023. This had been in the works since October 2019. It was a
collaborative process of our community and members where we received
valuable feedback. Thank you to all who contributed your ideas and
expertise to help us come up with this plan that looks into our journey
towards fulfilling our objectives for the next three years. The document
is available for download here>>
https://bit.ly/AFRINIC-Strategic-Plan-2021-2023
<https://bit.ly/AFRINIC-Strategic-Plan-2021-2023>

Agile Transformation?

As mentioned in my previous updates, much is happening in AFRINIC- most
of which might have not caught your attention. Early this month, AFRINIC
staff were taken through the agile transformation training. This
approach will help us swiftly adjust in an ever-changing environment
while creating incremental value for our customers. We foresee more
fruitful interactions with our members and our community as we strive to
serve you better.?

Database Accuracy

We are still committed to meet our Database accuracy report deadline
that we had set for next month. The report covers the work that has been
done during this year around improving the accuracy of our WHOIS database.?

We once again appreciate all the contributions from people being in
possession of elements that will support us in this project. As stated
previously, we are aware that each action ?may be disputed in court
which makes it is key that we take all necessary precautions and due
diligence before taking any action or releasing any data publicly.

Reflections

It is now one year since I joined AFRINIC as the Chief Executive
Officer. Our Communications team recently interviewed me, and they have
penned down my reflections of the last one-year in AFRINIC. Please have
a read on the AFRINIC Blog Here>>
https://afrinic.net/20201119-interview-with-ceo
<https://afrinic.net/20201119-interview-with-ceo>

I wish you good health and happiness as we pursue our common goals and
aspirations.

Kind Regards,

Eddy Kayihura

????????????????

Chers coll?gues,

J'esp?re que vous vous portez tous bien. C'est ? cette p?riode-l? que je
partage avec vous les mises ? jour mensuelles.

Plan strat?gique AFRINIC 2021-2023

Je suis heureux d'annoncer le lancement du plan strat?gique AFRINIC
2021-2023. Ce plan ?tait en cours d'?laboration depuis octobre 2019. Il
s'agit d'un processus de collaboration entre notre communaut? et nos
membres, qui nous a permis de recueillir des informations tr?s utiles.
Merci ? tous ceux qui ont apport? leurs id?es et leur expertise pour
nous aider ? ?laborer ce plan qui s'inscrit dans notre d?marche visant ?
atteindre nos objectifs pour les trois prochaines ann?es. Le document
est disponible ici>> https://bit.ly/AFRINIC-Strategic-Plan-2021-2023
<https://bit.ly/AFRINIC-Strategic-Plan-2021-2023>

Transformation agile?

Comme je l'ai mentionn? dans mes pr?c?dentes mises ? jour, beaucoup de
projets sont en cours ? l'AFRINIC - dont la plupart n'ont peut-?tre pas
attir? votre attention. Au d?but de ce mois, le personnel de l'AFRINIC a
suivi une formation sur la transformation agile. Cette approche nous
aidera ? nous adapter rapidement dans un environnement en constante
?volution tout en cr?ant une valeur ajout?e pour nos clients. Nous
pr?voyons des interactions plus fructueuses avec nos membres et notre
communaut? alors que nous nous engageons ? mieux vous servir.

Mise ? jour sur l'exactitude du WHOIS

Nous sommes toujours d?termin?s ? respecter la date limite que nous
avions fix?e au mois prochain pour le rapport sur l'exactitude du WHOIS.
Le rapport porte sur le travail qui a ?t? effectu? cette ann?e pour
am?liorer la pr?cision de notre base de donn?es WHOIS.?

Nous appr?cions une fois de plus toutes les contributions des personnes
qui sont en possession d'?l?ments qui nous soutiendront dans ce projet.
Comme indiqu? pr?c?demment, nous sommes conscients que chaque action
peut ?tre contest?e devant les tribunaux, ce qui fait qu'il est
essentiel que nous prenions toutes les pr?cautions n?cessaires et que
nous fassions preuve de diligence raisonnable avant d'entreprendre toute
action ou de publier toute donn?e.

R?flexions

Cela fait maintenant un an que j'ai rejoint l'AFRINIC en tant que
directeur g?n?ral. Notre ?quipe de communication m'a r?cemment
interview?, et elle a recueilli mes r?flexions sur l'ann?e ?coul?e au
sein de l'AFRINIC. Veuillez lire le blog d'AFRINIC ici>>
https://afrinic.net/20201119-interview-with-ceo
<https://afrinic.net/20201119-interview-with-ceo>

Je vous souhaite bonne sant? et bonheur dans la poursuite de nos
objectifs et aspirations communs.

Cordialement,

Eddy Kayihura

????????????????????.

?????? ????????

????? ?? ???? ?????? ??? ?? ????. ??? ????? ???? ????? ??? ????
????????? ???????.

??? ???????? ???????????? ????-????

?????? ??????? ?? ????? ??? ???????? ???????????? ????-????. ??? ?????
??? ?????? ????. ??? ???? ????? ??????? ???????? ???????? ??? ??????
??????? ????. ????? ??? ?? ???? ??????? ??????? ????????? ??? ?????? ???
??? ????? ???? ???? ?? ?????? ??? ????? ??????? ??????? ?????? ???????.
??????? ????? ??????? ??? >>
https://bit.ly/AFRINIC-Strategic-Plan-2021-2023
<https://bit.ly/AFRINIC-Strategic-Plan-2021-2023>

????? ?????? ??????

??? ???? ?? ???????? ??????? ? ???? ?????? ?? ???????? - ???? ?? ????
??????? ??????. ?? ??? ???? ?? ??? ????? ? ??? ????? ???????? ??????
?????? ??????. ???????? ??? ????? ??? ?????? ????? ?? ???? ????? ??????
?? ??? ???? ?????? ????????. ????? ?????? ?? ????????? ??????? ??
??????? ???????? ??? ???? ?????? ?????? ???? ????.

??? ????? ????????

?? ???? ??????? ??????? ??????? ??????? ?????? ??? ????? ???????? ????
?????? ????? ??????. ???? ??????? ????? ???? ?? ?????? ???? ??? ?????
??? ????? ??? ????? ????????? ?????? ???.

???? ??? ???? ???? ????????? ?? ??????? ????? ??????? ??????? ????
??????? ?? ??? ???????. ??? ????? ?????? ? ??? ???? ?? ???? ????? ??
???? ??? ???? ?? ??????? ??? ???? ?? ?????? ????? ???? ??????????
??????? ???????? ??????? ??? ????? ?? ????? ?? ??????? ?? ?? ?????? ?????.

?????

?? ???? ??? ???? ??? ?? ?????? ??? ???????? ????? ??????. ???? ????
????????? ????? ?????? ??? ?????? ? ?????? ?????? ??????? ?? ?????
?????? ?? ????????. ???? ??????? ??? ????? ???????? ??? >>
https://afrinic.net/20201119-interview-with-ceo
<https://afrinic.net/20201119-interview-with-ceo>


????? ??? ????? ????? ???????? ???? ???? ?????? ??????? ????????? ????????.

?????????????????.

Caros Colegas,

Espero que se mantenham todos bem. ? nessa altura que partilho convosco
as actualiza??es mensais.

Plano Estrat?gico AFRINIC 2021-2023

Tenho o prazer de anunciar o lan?amento do Plano Estrat?gico AFRINIC
2021-2023. Este estava em obras desde Outubro de 2019. Foi um processo
de colabora??o da nossa comunidade e dos nossos membros, onde recebemos
um valioso feedback. Obrigado a todos os que contribu?ram com as suas
ideias e conhecimentos para nos ajudar a elaborar este plano que analisa
a nossa viagem rumo ao cumprimento dos nossos objectivos para os
pr?ximos tr?s anos. O documento est? dispon?vel para download aqui>>
https://bit.ly/AFRINIC-Strategic-Plan-2021-2023
<https://bit.ly/AFRINIC-Strategic-Plan-2021-2023>

Transforma??o ?gil?

Como mencionado nas minhas actualiza??es anteriores, muito est? a
acontecer em AFRINIC - a maioria das quais pode n?o ter chamado a vossa
aten??o. No in?cio deste m?s, o pessoal da AFRINIC foi levado atrav?s da
forma??o de transforma??o ?gil. Esta abordagem ir? ajudar-nos a
ajustar-nos rapidamente num ambiente em constante mudan?a, ao mesmo
tempo que cria valor incremental para os nossos clientes. Prevemos
interac??es mais frutuosas com os nossos membros e a nossa comunidade ?
medida que nos esfor?amos por servi-lo melhor.?

Precis?o da Base de Dados

Ainda estamos empenhados em cumprir o nosso prazo de relat?rio de
exactid?o da base de dados que t?nhamos fixado para o pr?ximo m?s. O
relat?rio abrange o trabalho que foi feito durante este ano em torno da
melhoria da exactid?o da nossa base de dados WHOIS.?

Agradecemos mais uma vez todas as contribui??es das pessoas que est?o na
posse de elementos que nos ir?o apoiar neste projecto. Como foi dito
anteriormente, estamos conscientes de que cada ac??o pode ser contestada
em tribunal, o que faz com que seja fundamental que tomemos todas as
precau??es necess?rias e a devida dilig?ncia antes de tomarmos qualquer
ac??o ou divulgarmos publicamente quaisquer dados.

Reflex?es

Passou um ano desde que entrei para a AFRINIC como Chefe do Executivo. A
nossa equipa de Comunica??o entrevistou-me recentemente, e eles
escreveram as minhas reflex?es sobre o ?ltimo ano na AFRINIC. Por favor,
leia no Blog AFRINIC Aqui>>
https://afrinic.net/20201119-interview-with-ceo
<https://afrinic.net/20201119-interview-with-ceo>

Desejo-vos boa sa?de e felicidade enquanto perseguimos os nossos
objectivos e aspira??es comuns.

Cordiais cumprimentos,

Eddy Kayihura

-- 
----

Eddy Kayihura

Chief Executive Officer

African Network Information Centre (AFRINIC)

t:  +230 403 5100 | tt: @afrinic | w: www.afrinic.net <http://www.afrinic.net>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/community-discuss/attachments/20201119/7154a2a2/attachment.html>

From comms at afrinic.net  Mon Nov 23 12:54:45 2020
From: comms at afrinic.net (AFRINIC Communication)
Date: Mon, 23 Nov 2020 16:54:45 +0400
Subject: [Community-Discuss] Erratum to the message on the Call for
 volunteers on the Govcom and ASO AC/NRO-NC
Message-ID: <AAA02836-0FCA-41E5-A1FE-E59037462AA6@afrinic.net>

[Erratum]

Dear  colleagues,

Please read the deadline for the call for volunteers on the Govcom and ASO AC/NRO-NC as 3 December 2020 instead of 18 December 2020.

We apologise for this error and inconvenience.

AFRINIC Communications

???????????????????.

Chers coll?gues,

Merci de lire que la date limite pour l'appel ? volontaires sur le Govcom et l'ASO AC/NRO-NC, est le 3 d?cembre 2020 au lieu du 18 d?cembre 2020.

Nous vous prions de bien vouloir nous excuser pour l?erreur et le d?sagr?ment occasionn?.

Communications AFRINIC

????????????????????

?????? ????????

???? ????? ?????? ??????? ????? ????????? ?? Govcom ? ASO AC / NRO-NC ???????? ?? 3 ?????? 2020 ????? ?? 18 ?????? 2020.

????? ?? ??? ????? ????????.

AFRINIC ????????? ?????????

??????????????????

Caros colegas,

Por favor, leia o prazo para o convite para volunt?rios no Govcom e ASO AC/NRO-NC at? 3 de Dezembro de 2020 em vez de 18 de Dezembro de 2020.

Pedimos desculpa por este erro e inconveni?ncia.

Comunica??es AFRINIC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/community-discuss/attachments/20201123/4f47b3d5/attachment.html>

From comms at afrinic.net  Mon Nov 23 12:58:45 2020
From: comms at afrinic.net (AFRINIC Communication)
Date: Mon, 23 Nov 2020 16:58:45 +0400
Subject: [Community-Discuss] =?utf-8?q?Participez_au_webinaire_sur_les_abu?=
 =?utf-8?q?s_du_Syst=C3=A8me_des_Noms_de_Domaine_=28DNS=29_et_les_actions_?=
 =?utf-8?q?pour_les_r=C3=A9duire?=
Message-ID: <364F106F-7E78-43FC-9CA4-2DBE34C9FCAF@afrinic.net>

Chers coll?gues,

AFRINIC et ICANN s'associent pour vous d?livrer un nouveau webinaire informatif sur les abus du Syst?me des Noms de Domaine (DNS) et les actions pour les r?duire.

Les abus du DNS ont ?volu? ? travers le temps et constituent aujourd'hui un risque de s?curit? consid?rable affectant la confiance des utilisateurs finaux sur Internet.

Ce webinaire vise ? informer les participants sur les activit?s qualifi?es d'abus dans l'?cosyst?me du DNS et fournira ?galement des conseils sur les mesures de signalement et d'att?nuation des abus DNS.

A la fin de cette session, vous serez capable de:

? Comprendre les activit?s consid?r?es comme des abus au Syst?me des Noms de Domaine.

? Identifier les solutions et recommandations pour r?duire ces abus.

? D?couvrir et comprendre les actions d'ICANN pour palier ces abus du DNS.

Utilisez le lien suivant pour vous inscrire, et n'oubliez pas d'ajouter l'?v?nement ? votre calendrier: 

https://bit.ly/AFRINICWebinar-DNS-FR

Date: 26 Novembre 2020

Langue: Fran?ais

Heure:

? 12:30 UTC (Senegal, Cote D'Ivoire)

? 13:30 WAT (Cameroun, Tunisie)

? 14:30 CAT (Burundi)

? 16:30 GST (Maurice, Seychelles)


Rendez-vous au webinaire!


From comms at afrinic.net  Mon Nov 23 15:23:43 2020
From: comms at afrinic.net (AFRINIC Communication)
Date: Mon, 23 Nov 2020 19:23:43 +0400
Subject: [Community-Discuss] Yet more data base problems/inconsistancies
In-Reply-To: <55860.1604715875@segfault.tristatelogic.com>
References: <55860.1604715875@segfault.tristatelogic.com>
Message-ID: <9E14BB14-159B-4877-A1F6-3B436FF8832D@afrinic.net>

Dear Community,

Following your inquiry regarding the existence of inconsistencies between reverse DNS delegation records within the WHOIS Database and the published RDNS zone files at ftp://ftp.afrinic.net/pub/zones/ directory, we have carried out further analysis and below are the findings.  

1.     This situation is a result of the presence of overlapping records in the WHOIS Database. The script that picks and publishes to the ftp picks only the reverse DNS domain covering the less specific prefix, for instance with reference to the example provided, the ftp file contains the record for 203.196.in-addr.arpa and not any other more specific reverse DNS records such as  35.203.196.in-addr.arpa

2.     These overlapping records are historical and date back to the period between 2004 - 2007 and the whois at that time did not have the checks that guard against creation of these overlaps.

The issue regarding the existence of these overlaps in the WHOIS Database was raised by staff during the first database working group session at AIS-19 in Kampala, for the best way forward on resolving this and the consensus was that nothing should be done. The DBWG session report is available here:

https://lists.afrinic.net/pipermail/dbwg/2019-June/000140.html

Going forward, we intend to ensure that these overlapping records are cleared and no longer present inconsistencies. We shall therefore proceed as follows:

1.Initiate contact with the respective resource holders and assist them to fix their records accordingly.

2.For resource holders that are unreachable or unresponsive after a period of 90 days, we shall proceed to remove the more specific reverse DNS record from the WHOIS Database.

Please note that the issue of duplicate domain objects in the database was resolved last week.

 On behalf of the IT and Engineering Team


 

> On 7 Nov 2020, at 06:24, Ronald F. Guilmette <rfg at tristatelogic.com> wrote:
> 
> In message <A1A60763-83F7-4073-B20B-F2CAE4D23D72 at afrinic.net>, 
> AFRINIC Communication <comms at afrinic.net> wrote:
> 
>> We appreciate your concern around the duplicate domain object in the 
>> AFRINIC whois Database. The same was raised and discussed on the DBWG 
>> mailing list 
>> <https://lists.afrinic.net/pipermail/dbwg/2020-September/000269.html> 
> 
> Just to be sure we are clear, there is not just one duplicate.  By my
> count, there are 40 of them.
> 
>> We have been working on this when it came to our attention and we hope 
>> to have this resolved and deployed soon. We shall keep the community 
>> updated as soon as this has been done.
>> 
>> The domain objects with the trailing dot were previously possible 
>> according to RFC 1034. The AFRINIC whois Database however does not allow 
>> the creation of this type of domains.
>> 
>> The objects in question cannot be queried via port 43 as the Whois 
>> Database automatically removes any trailing dot from the object key.
>> 
>> Regarding the issue with the zone files, we are still investigating and 
>> an update will be provided to the community as soon as it is resolved.
> 
> Thank you for the update.
> 
> The apparent differences between the data present in the zone files and
> the data present in the published WHOIS with respect to reverse DNS
> delegations are most certainly things that I will be happy to know
> the cause of, whenever that information becomes available.
> 
> 
> Regards,
> rfg
> 
> _______________________________________________
> Community-Discuss mailing list
> Community-Discuss at afrinic.net
> https://lists.afrinic.net/mailman/listinfo/community-discuss




From comms at afrinic.net  Thu Nov 26 09:15:26 2020
From: comms at afrinic.net (AFRINIC Communication)
Date: Thu, 26 Nov 2020 13:15:26 +0400
Subject: [Community-Discuss] Participez au prochain webinaire de l'AFRINIC |
 Mercredi 02 Decembre 2020
Message-ID: <67A601C2-2EF0-415F-95EF-622659287593@afrinic.net>


Chers coll?gues,

AFRINIC a le plaisir de vous inviter ? son prochain webinaire sur ' l'AG de l'AFRINIC, la nomination, la r?vocation et les pouvoirs des administrateurs'.

Ceci est le cinqui?me webinaire de notre s?rie sur l'?cosyst?me et la gouvernance de l'AFRINIC.

Date: Mercredi 02 D?cembre 2020

Heure: 12h30 GMT / UTC

? 12:30 UTC (Ghana, Cote D'Ivoire)
? 13:30 WAT (Nigeria, Cameroon)
? 14:30 SAST (Afrique du sud, Lesotho)
? 15:30 EAT (Kenya, Uganda)
? 16:30 GST (Maurice, Seychelles)

Inscription: https://bit.ly/AFRINICWebinar-December-FR

Langue: Fran?ais

Audience:
Les membres de la communaut? AFRINIC et toute autre personne int?ress?e par
gestion les ressources de num?riques Internet dans la r?gion de service
d'AFRINIC.

Objectifs:

? la fin de cette session, les participants pourront:

# Conna?tre le r?le du pr?sident de l'AG des membres et comment il (elle) est
nomm?(e)
# Comprendre le r?le de la convocation l'AG des membres
# Comprendre le quorum
# Conna?tre les diff?rents mode de votes et qui peut voter
# Expliquer le r?le des proxys et quand les utiliser
# Conna?tre les crit?res d'?ligibilit?
# Expliquer comment le directeur d?AFRINIC est nomm?
# D?crire les conditions et les circonstances de r?vocation d'un administrateur
# Conna?tre les pouvoirs des membres du conseil d'administration

Pr?sentateurs:
Kishna Dhondee - Juriste
Arthur Nguessan - HoD - Engagement des parties prenantes
Brice Abba - Responsable du d?veloppement communautaire

Rendez-vous au webinaire!

Ashil Oogarah
De la part du d?partement Stakehoders Engagement d'AFRINIC







From comms at afrinic.net  Fri Nov 27 11:08:42 2020
From: comms at afrinic.net (AFRINIC Communication)
Date: Fri, 27 Nov 2020 15:08:42 +0400
Subject: [Community-Discuss] Register for the AFRICOMM 2020 Online Conference
Message-ID: <86B0D364-4EDC-4CE2-9D37-EDE05F8112BC@afrinic.net>

Dear colleagues,

AFRINIC is pleased to invite you for the AFRICOMM 2020 Online Conference. This edition is the 12th EAI International Conference on e-Infrastructure and e-Services for Developing Countries, taking place from December  2-4, 2020.

We have an interesting programme that includes several keynotes as well as a wide array of technical experts and topics.

Registration is currently ongoing here: https://bit.ly/AFRICOMM-2020-Registration

More information on AFRICOMM 2020 is available here: https://africommconference.eai-conferences.org/2020/

We look forward to seeing you online.

Ashil Oogarah





From abscoco at gmail.com  Sat Nov 28 06:24:30 2020
From: abscoco at gmail.com (Sylvain Baya)
Date: Sat, 28 Nov 2020 07:24:30 +0100
Subject: [Community-Discuss]  Yet more data base problems/inconsistancies
In-Reply-To: <9E14BB14-159B-4877-A1F6-3B436FF8832D@afrinic.net>
References: <55860.1604715875@segfault.tristatelogic.com>
 <9E14BB14-159B-4877-A1F6-3B436FF8832D@afrinic.net>
Message-ID: <CAJjTEvH29Au48SMyUvL0REYb+G+i_GTudg41Ff5_gHY+_6mJgA@mail.gmail.com>

Dear all,
Hope you are doing well !

Please see my comments below...

Le lun. 23 nov. 2020 16:25, AFRINIC Communication <comms at afrinic.net> a
?crit :

Dear Community,

Following your inquiry regarding the existence of inconsistencies between
reverse DNS delegation records within the WHOIS Database and the published
RDNS zone files at ftp://ftp.afrinic.net/pub/zones/ directory, we have
carried out further analysis and below are the findings.


[...]


Please note that the issue of duplicate domain objects in the database was
resolved last week.



...so! thanks to Ronald ? :-)


 On behalf of the IT and Engineering Team



Thanks for your reactivity, Team.

How critical is that database to you, guys, now; so that
you could put in place a follow-up mechanism to
anticipate, as possible as, the impact of any incident
which could occur ?

Shalom,
--sb.



> [...]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/community-discuss/attachments/20201128/c3a7a1ce/attachment.html>

From rfg at tristatelogic.com  Sat Nov 28 20:55:06 2020
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Sat, 28 Nov 2020 12:55:06 -0800
Subject: [Community-Discuss] Yet more data base problems/inconsistancies
In-Reply-To: <9E14BB14-159B-4877-A1F6-3B436FF8832D@afrinic.net>
Message-ID: <14145.1606596906@segfault.tristatelogic.com>

My apologies for having failed to report to this recent message
sooner.

In message <9E14BB14-159B-4877-A1F6-3B436FF8832D at afrinic.net>, 
AFRINIC Communication <comms at afrinic.net> wrote:

>Following your inquiry regarding the existence of inconsistencies 
>between reverse DNS delegation records within the WHOIS Database and the 
>published RDNS zone files at ftp://ftp.afrinic.net/pub/zones/ directory, 
>we have carried out further analysis and below are the findings.
>
>1.     This situation is a result of the presence of overlapping records 
>in the WHOIS Database. The script that picks and publishes to the ftp 
>picks only the reverse DNS domain covering the less specific prefix, for 
>instance with reference to the example provided, the ftp file contains 
>the record for 203.196.in-addr.arpa and not any other more specific 
>reverse DNS records such as  35.203.196.in-addr.arpa
>
>2.     These overlapping records are historical and date back to the 
>period between 2004 - 2007 and the whois at that time did not have the 
>checks that guard against creation of these overlaps.
>
>The issue regarding the existence of these overlaps in the WHOIS 
>Database was raised by staff during the first database working group 
>session at AIS-19 in Kampala, for the best way forward on resolving this 
>and the consensus was that nothing should be done. The DBWG session 
>report is available here:
>
>https://lists.afrinic.net/pipermail/dbwg/2019-June/000140.html
>
>Going forward, we intend to ensure that these overlapping records are 
>cleared and no longer present inconsistencies.

I'm sorry, but I must take issue, in a modest way, with this chosen
resolution.

I believe that you have explained the "issue" of the "overlapping"
reverse DNS delegations clearly, but I am not persuaded that there
is actually any problem here, other than that some of the AFRINIC
reverse DNS delegations were not being represented in the public
AFRINIC zone file(s).

I must ask the question: Why should it be considered to be either "bad"
or even "a problem" if AFRINIC maintains reverse DNS delegations for,
say, some /16 and also and separately, maintains a different reverse
DNS delegation for some particular /24 block which is a part of that
larger containing /16 block?

It is certainly the case that if AFRINIC has allocated, for example,
some large containing block to some party or entity and if it has also
properly delegated to that party/entity responsibility for handling the
reverse DNS for that entire block, then if the block registrant wishes
to do so, he/she/it can then sub-delegate parts of this responsibility 
to others parties himself.  But I see nothing which technically prevents
AFRINIC itself from delegating reverse DNS athority for, say, some /16
block to some specific name servers even while it also and separately
delegates the reverse DNS authority for some sub-block of that containing
/16 block to some different set of name servers.

In fact, I am going to go out on a limb here and assert that other
Regional Internet Registries are in fact doing this exact thing, i.e.
frequently delegating authority for reverse DNS for both contained
blocks and, in some cases, for their containing blocks.  (I will
attempt to find and present some actual examples from each of the
other RIRs if anyone thinks that may be helpful here.)

I may be wrong in my assertion that other RIRs are themselves providing
separate rDNS delegations for both blocks and sub-blocks thereof,  but
I don't think so.

If I am correct, then there is really nothing for AFRINIC to "clean
up" here, other than some slight tweeking of the code used to generate
AFRINIC's public reverse DNS zone files.

I would hasten to add that the question of whether any of the other
five RIRs are or are not doing rDNS delegation for both blocks and
(separately) for contained sub-blocks is almost irrelevant, and that
AFRINIC is, I believe, free to choose whether it will do this or not
do this as it wishes.  As I have said above, I am not personally aware
of any technical issue that would absolutely -prevent- AFRINIC from
delegating to both blocks and also (and separately) to contained
sub-blocks also.  (And indeed, it sounds to me like this -is- already
being done in some instances, so just from a technical perspective,
it seems to work.)

In any case, I wish to thank the technical staff for their attention
to this set of issues, and in particular to the issue I originally raised
which related just to the content of the public zone files, and which
did not delve into the separate issue/question of what kinds of rDNS
delegations AFRINIC should or should not be doing.  (I think this latter
stuff is a policy issue, not a tecnhical one, and I have no real opinion
on the question of which rDNS delegations AFRINIC should or should not
be doing, in general, other than to express my hope that it all continues
to function at least as well as it currently does.... except, of course,
for any of the still stolen blocks.)

>Please note that the issue of duplicate domain objects in the database 
>was resolved last week.

Excellent!  Thanks also for that!


Regards,
rfg



From benm at workonline.africa  Mon Nov 30 01:33:19 2020
From: benm at workonline.africa (Ben Maddison)
Date: Mon, 30 Nov 2020 03:33:19 +0200
Subject: [Community-Discuss] Yet more data base problems/inconsistancies
In-Reply-To: <14145.1606596906@segfault.tristatelogic.com>
References: <9E14BB14-159B-4877-A1F6-3B436FF8832D@afrinic.net>
 <14145.1606596906@segfault.tristatelogic.com>
Message-ID: <20201130013319.xddpolsgaynzlza6@benm-laptop>

Hi Ronald,

On 11/28, Ronald F. Guilmette wrote:
> My apologies for having failed to report to this recent message
> sooner.
> 
> In message <9E14BB14-159B-4877-A1F6-3B436FF8832D at afrinic.net>, 
> AFRINIC Communication <comms at afrinic.net> wrote:
> 
> >Following your inquiry regarding the existence of inconsistencies 
> >between reverse DNS delegation records within the WHOIS Database and the 
> >published RDNS zone files at ftp://ftp.afrinic.net/pub/zones/ directory, 
> >we have carried out further analysis and below are the findings.
> >
> >1.     This situation is a result of the presence of overlapping records 
> >in the WHOIS Database. The script that picks and publishes to the ftp 
> >picks only the reverse DNS domain covering the less specific prefix, for 
> >instance with reference to the example provided, the ftp file contains 
> >the record for 203.196.in-addr.arpa and not any other more specific 
> >reverse DNS records such as  35.203.196.in-addr.arpa
> >
> >2.     These overlapping records are historical and date back to the 
> >period between 2004 - 2007 and the whois at that time did not have the 
> >checks that guard against creation of these overlaps.
> >
> >The issue regarding the existence of these overlaps in the WHOIS 
> >Database was raised by staff during the first database working group 
> >session at AIS-19 in Kampala, for the best way forward on resolving this 
> >and the consensus was that nothing should be done. The DBWG session 
> >report is available here:
> >
> >https://lists.afrinic.net/pipermail/dbwg/2019-June/000140.html
> >
> >Going forward, we intend to ensure that these overlapping records are 
> >cleared and no longer present inconsistencies.
> 
> I'm sorry, but I must take issue, in a modest way, with this chosen
> resolution.
> 
> I believe that you have explained the "issue" of the "overlapping"
> reverse DNS delegations clearly, but I am not persuaded that there
> is actually any problem here, other than that some of the AFRINIC
> reverse DNS delegations were not being represented in the public
> AFRINIC zone file(s).
> 
> I must ask the question: Why should it be considered to be either "bad"
> or even "a problem" if AFRINIC maintains reverse DNS delegations for,
> say, some /16 and also and separately, maintains a different reverse
> DNS delegation for some particular /24 block which is a part of that
> larger containing /16 block?
> 
This seems fairly clear, to me at least, that having delegations at the
same authoritative nameserver for a subdomain and a
subdomain-of-a-subdomain is problematic.

Consider:
ns-a delegates foo.example.com to ns-b
           and bar.foo.example.com to ns-c
ns-b delegates bar.foo.example.com to ns-d

Who is authoritative for host.bar.foo.example.com?

I haven't checked whether this is permitted by the RFCs, but even if it
is, it seems like a readily avoidable recipe for breakage. And one
without an obvious benefit that I can see.

Maybe someone here knows the answer definitively?
Or can think of a use-case that would require this kind of a delegation?

Cheers,

Ben
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.afrinic.net/pipermail/community-discuss/attachments/20201130/b16a589b/attachment.sig>

From rfg at tristatelogic.com  Mon Nov 30 02:48:03 2020
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Sun, 29 Nov 2020 18:48:03 -0800
Subject: [Community-Discuss] Yet more data base problems/inconsistancies
In-Reply-To: <20201130013319.xddpolsgaynzlza6@benm-laptop>
Message-ID: <20370.1606704483@segfault.tristatelogic.com>

In message <20201130013319.xddpolsgaynzlza6 at benm-laptop>, 
Ben Maddison <benm at workonline.africa> wrote:

>This seems fairly clear, to me at least, that having delegations at the
>same authoritative nameserver for a subdomain and a
>subdomain-of-a-subdomain is problematic.

I don't see that.

>Consider:
>ns-a delegates foo.example.com to ns-b
>           and bar.foo.example.com to ns-c
>ns-b delegates bar.foo.example.com to ns-d
>
>Who is authoritative for host.bar.foo.example.com?

My understanding is that the delegation of DNS authority works a lot
like routing, i.e. in any case where two or more DNS authority delegations
-could- theoretically be applicable, the most specific DNS delegation wins.

Of course, if there are ties, where each of two or more delegations are
equally specific, then that's problematic.  But I don't think we are
discussing such cases at the moment.

I freely admit that I may perhaps not be on entirely solid ground when
it comes to this "most specific wins" rule, but I do believe that's how
DNS works.  If I am wrong about that, I will be happy to be corrected.


Regards,
rfg



From comms at afrinic.net  Mon Nov 30 10:29:24 2020
From: comms at afrinic.net (AFRINIC Communication)
Date: Mon, 30 Nov 2020 14:29:24 +0400
Subject: [Community-Discuss] Yet more data base problems/inconsistancies
In-Reply-To: <20370.1606704483@segfault.tristatelogic.com>
References: <20370.1606704483@segfault.tristatelogic.com>
Message-ID: <1754D42E-5DD2-4486-8ED3-B9C45D89896C@afrinic.net>

Dear community,

We would like to highlight and appreciate your feedback on the WHOIS Database.

AFRINIC is committed to working towards improving the accuracy and security of the WHOIS Database and relies on such feedback to continuously improve the WHOIS Database.

In this regard, we would like to invite anyone who is willing to make such contributions to join the Database working group (DBWG) by subscribing to our mailing list.

https://lists.afrinic.net/mailman/listinfo/dbwg

AFRINIC is also pleased to announce the upcoming deployment of features that will improve security in the WHOIS Database.

Please read more on these deployments on our blog: https://afrinic.net/20201130-deprecation-of-crypt-and-md5

Ashil Oogarah

On behalf of AFRINIC?s IT and Engineering Team


> On 30 Nov 2020, at 06:48, Ronald F. Guilmette <rfg at tristatelogic.com> wrote:
> 
> In message <20201130013319.xddpolsgaynzlza6 at benm-laptop>, 
> Ben Maddison <benm at workonline.africa> wrote:
> 
>> This seems fairly clear, to me at least, that having delegations at the
>> same authoritative nameserver for a subdomain and a
>> subdomain-of-a-subdomain is problematic.
> 
> I don't see that.
> 
>> Consider:
>> ns-a delegates foo.example.com to ns-b
>>          and bar.foo.example.com to ns-c
>> ns-b delegates bar.foo.example.com to ns-d
>> 
>> Who is authoritative for host.bar.foo.example.com?
> 
> My understanding is that the delegation of DNS authority works a lot
> like routing, i.e. in any case where two or more DNS authority delegations
> -could- theoretically be applicable, the most specific DNS delegation wins.
> 
> Of course, if there are ties, where each of two or more delegations are
> equally specific, then that's problematic.  But I don't think we are
> discussing such cases at the moment.
> 
> I freely admit that I may perhaps not be on entirely solid ground when
> it comes to this "most specific wins" rule, but I do believe that's how
> DNS works.  If I am wrong about that, I will be happy to be corrected.
> 
> 
> Regards,
> rfg
> 
> _______________________________________________
> Community-Discuss mailing list
> Community-Discuss at afrinic.net
> https://lists.afrinic.net/mailman/listinfo/community-discuss




From comms at afrinic.net  Mon Nov 30 12:33:27 2020
From: comms at afrinic.net (AFRINIC Communication)
Date: Mon, 30 Nov 2020 16:33:27 +0400
Subject: [Community-Discuss] =?utf-8?q?Rappel=3A_Participez_au_prochain_we?=
 =?utf-8?q?binaire_de_l=27AFRINIC_=7C_Mercredi_02_D=C3=A9cembre_2020?=
Message-ID: <4ED88F87-FBF5-406C-AB21-38F785D227DA@afrinic.net>

Chers coll?gues,

AFRINIC a le plaisir de vous inviter ? son prochain webinaire sur ' l'AG de l'AFRINIC, la nomination, la r?vocation et les pouvoirs des administrateurs'.

Ceci est le cinqui?me webinaire de notre s?rie sur l'?cosyst?me et la gouvernance de l'AFRINIC.

Date: Mercredi 02 D?cembre 2020

Heure: 12h30 GMT / UTC

? 12:30 UTC (Ghana, Cote D'Ivoire)
? 13:30 WAT (Nigeria, Cameroon)
? 14:30 SAST (Afrique du sud, Lesotho)
? 15:30 EAT (Kenya, Uganda)
? 16:30 GST (Maurice, Seychelles)

Inscription: https://bit.ly/AFRINICWebinar-December-FR <https://bit.ly/AFRINICWebinar-December-FR>

Langue: Fran?ais

Audience:
Les membres de la communaut? AFRINIC et toute autre personne int?ress?e par
gestion les ressources de num?riques Internet dans la r?gion de service
d'AFRINIC.

Objectifs:

? la fin de cette session, les participants pourront:

# Conna?tre le r?le du pr?sident de l'AG des membres et comment il (elle) est
nomm?(e)
# Comprendre le r?le de la convocation l'AG des membres
# Comprendre le quorum
# Conna?tre les diff?rents mode de votes et qui peut voter
# Expliquer le r?le des proxys et quand les utiliser
# Conna?tre les crit?res d'?ligibilit?
# Expliquer comment le directeur d?AFRINIC est nomm?
# D?crire les conditions et les circonstances de r?vocation d'un administrateur
# Conna?tre les pouvoirs des membres du conseil d'administration

Pr?sentateurs:
Kishna Dhondee - Juriste
Arthur Nguessan - HoD - Engagement des parties prenantes
Brice Abba - Responsable du d?veloppement communautaire

Rendez-vous au webinaire!

Ashil Oogarah
De la part du d?partement Stakehoders Engagement d'AFRINIC

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/community-discuss/attachments/20201130/69097b7d/attachment.html>