View all frequently asked questions
View FAQ Tags
AFRINIC membership and resources related billing FAQs.
AFRINIC WHOIS related FAQs
General FAQs related to AFRINIC activites
MyAFRINIC portal related FAQs
Membership related queries
FAQ for Existing members
AFRINIC BPKI Services
FAQs related to IPv4 Exhaustion and its impact on AFRINIC
AFRINIC WHOIS related FAQs
The AFRINIC Database is a public database that contains information about registered IP address space and AS numbers, routing policies,and reverse DNS delegations in the AFRINIC region. It is used for Internet network management.
There are very good documents that explain the working of the AFRINIC whois database: The AFRINIC DB reference manual and the AFRINIC DB supporting document. If you still find lots of complications even after reading these documents, we advise that you enrol for one of our LIR training courses, the schedule of which is available at the training section of the AFRINIC website.
The AFRINIC database reference manual is available on the AFRINIC website here
AFRINIC whois database is a public database which is open for anyone to use. If your person object (nic-hdl) is not protected then anybody can alter it. We advise you to create personal maintainer or use your organisation maintainer to protect your object.
The maintainer is used to protect your other objects in AFRINIC database. It ensures that only authorised changes can be done to your objects.
1. Fill in the template below.
- In the "mnt-by" field use the same as "mntner" field.
- Encrypt your password using this link and paste the encrypted password in "auth" field after MD5-PW.
- Fill in "password" field with your clear text password.
- The "source" field is already filled for you.
2. Copy the object into plain text format mail.
3. Send the mail to firstname.lastname@example.org with blank subject line and wait for the result.
4. The clear text password will be required whenever you update objects that are protected by the maintainer. Please ensure that you memorise it.If the maintainer belongs to your organisation, please ensure that it forms part of your organisation's password policy.
AFRINIC registers the prefix with XXX as country( we use the organisation's country as reference). What the internet will reflect will depend as to whether the databases storing this info are synchronised/updated with the current AFRINIC whois data. We have no control onthe info stored in other databases. You can validate the information stored in AFRINIC database by querying whois database. If you find any discrepancies, please report it to email@example.com.
Person object can be created with the following template. Arguements are supplied after the colon (:) delimiter for each attribute.
a.) the "person" attribute takes full name as arguement. e.g. ( person: Nelson Mandela)
b.) complete the "address:" attribute with your address as the name suggests
c.) same for the "phone: " and "email:" attribute.
d.) Leave the "nic-handle:" and "source:" attribute as it has already been completed.
d.) complete the "notify:" attribute with the email address of the person to be notified of any changes to this person object
e.) complete the "changed:" attribute with the email and date of the person making the changes (e.g. changed: firstname.lastname@example.org 20130731)
when done send plain text email to email@example.com.
AFRINIC and RIPE NCC are two different WHOIS databases. Objects in AFRINIC database will have the suffix "-AFRINIC" while in RIPE will have the suffix "-RIPE". So, the objects can't be used interchangably and you must create your own objects at each one separately.
Organisation objects are maintained by AFRINIC. AFRINIC provides mechanism to edit addresses, e-mails and phone numbers through the myAFRINIC member portal. The Administrative contact has the right to edit the details of the organisation. Any other changes or addition of new contacts must be requested from AFRINIC by sending e-mail to firstname.lastname@example.org. The requestor must be a registered contact and provide either the details of the new contacts or their nic-hdls.
If you are having challenges updating an object in the database, you may want to re-examine the way your email is formed. Recent research we conducted indicate that people encounter challenges while interacting with our auto-dbm robot because of how their e-mail is formed. Please always ensure that the content of your email is in plaintext (no formatting at all before submitting to email@example.com).