Your IP address is 44.212.96.86
Please select your question category
Search FAQs
All FAQs
View all frequently asked questions
Tags
View FAQ Tags
Billing

AFRINIC membership and resources related billing FAQs.

WHOIS Database

AFRINIC WHOIS related FAQs
General Queries

General FAQs related to AFRINIC activites
MyAFRINIC

MyAFRINIC portal related FAQs
Membership and Resource Request

Membership related queries

AFRINIC member

FAQ for Existing members
BPKI

AFRINIC BPKI Services
IPv4 Exhaustion

FAQs related to IPv4 Exhaustion and its impact on AFRINIC
FAQs - WHOIS Database

AFRINIC WHOIS related FAQs

What is the AFRINIC whois database?

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.

Your whois database is very complicated to deal with!

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.

How do I query the AFRINIC whois database?

 

There are two methods to query the whois database:

Command Line Interface: using whois client which can be downloaded from here.
Web Based Interface: using whois query page at our website.

 

Where can I find documentation related to the whois database?

The AFRINIC database reference manual is available on the AFRINIC website here

How can I update my maintainer object information?

Please read the documentation available here and follow the instructions. Should you require any assistance, you may send your request to afrinic-dbm@afrinic.net.

My person object information has been changed by another person. What should I do?

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.

How is the maintainer object used?

The maintainer is used to protect your other objects in AFRINIC database. It ensures that only authorised changes can be done to your objects.

I forgot my maintainer password, what should I do?

Choose a new password and encrypt it using BCRYPT password hashing method on this link and send the encrypted password to hostmaster@afrinic.net requesting for mntner password update.

Tags: mntner
How can I create a maintainer?

You will find a step-by-step guide here.

Our organisation is located in country XXX and according to the internet, our IP number resources are reflected to be in country YYY ?

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 hostmaster@afrinic.net.

Tags: geolocation
How do I create a person object?

You will find a step-by-step guide here.

I already have person and maintainer in AFRINIC whois database, why do I need new ones to register my routes in RIPE NCC database?

The RIPE NCC database does not synchronise with the AFRINIC database. In this regard, there is a need to register the person, maintainer & aut-num objects on the RIPE NCC database before our members can register their route objects.

Tags: IRR, RIPE
Can I use AFRINIC objects to register in RIPE NCC database? Why not?

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.

Can I edit my organisation details on the whois database?

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 hostmaster@afrinic.net. The requestor must be a registered contact and provide either the details of the new contacts or their nic-hdls.

Tags: MyAFRINIC, organisation
I am getting an error message when I try to create an object on the whois database?

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 auto-dbm@afrinic.net).

Display #
Page 1 of 2

Profile Information

Application afterLoad: 0.002 seconds, 0.71 MB
Application afterInitialise: 0.110 seconds, 2.70 MB
Application afterRoute: 0.149 seconds, 5.95 MB
Application afterDispatch: 0.190 seconds, 7.05 MB
Application afterRender: 0.375 seconds, 9.60 MB

Memory Usage

10119480

33 queries logged

  1. SELECT m.*, c.`option` AS component
      FROM www3menu AS m
      LEFT JOIN www3components AS c
      ON m.componentid = c.id
      WHERE m.published = 1
      ORDER BY m.sublevel, m.parent, m.ordering
  2. SELECT jf_content.reference_field, jf_content.VALUE, jf_content.reference_id, jf_content.original_value

      FROM www3jf_content AS jf_content

      WHERE jf_content.language_id=1
           
      AND jf_content.published=1
       
      AND jf_content.reference_id IN(1,11,20,304,324,262,231,275,340,393,791,661,12,51,348,805,831,13,52,154,795,14,24,53,793,15,797,16,62,803,17,799,68,97,27,387,619,191,221,172,170,76,171,337,418,521,845,175,174,177,237,176,499,511,455,481,523,547,671,184,185,188,423,837,527,179,181,204,235,156,158,159,384,475,675,629,160,161,162,157,192,621,268,270,266,321,264,265,338,416,483,519,843,276,283,278,282,477,677,279,631,280,281,429,277,382,305,306,307,308,424,835,317,330,318,319,320,325,326,327,328,529,341,342,343,345,350,349,408,351,354,745,489,509,356,479,525,549,673,388,400,403,404,405,406,419,513,399,394,396,397,395,617,615,663,665,801,414,163,731,733,735,737,715,739,741,789,743,269,271,272,292,289,290,291,293,294,339,295,420,386,807,811,285,286,288,819,383,287,515,567,809,817,415,284,633,763,315,312,561,563,565,767,314,380,517,332,333,334,335,336,370,346,347,311,378,787,352,364,362,365,833,719,366,367,368,411,412,453,825,379,357,358,359,360,361,371,431,459,463,467,469,471,473,531,533,537,539,541,543,545,599,609,601,605,485,487,491,493,495,497,551,553,557,559,841,573,575,577,579,581,583,585,591,589,777,779,813,749,751,753,755,747,757,759,761,783,373,374,375,376,721,417,829,669,353,413,461,535,781,727,667,611,597,603,815,769,635,637,639,641,645,643,647,649,651,653,655,657,659,785,821,823,827,697,701,703,705,707,709,711)
       
      AND jf_content.reference_table='menu'
  3. SELECT *
      FROM www3rokcandy
      WHERE published=1
  4. SELECT template
      FROM www3templates_menu
      WHERE client_id = 0
      AND (menuid = 0 OR menuid = 388)
      ORDER BY menuid DESC
      LIMIT 0, 1
  5. SELECT *
      FROM www3fsf_settings
  6. SELECT *
      FROM www3fsf_settings_big
  7. SELECT *
      FROM www3fsf_settings_view
  8. SELECT *
      FROM www3fsf_faq_cat
      WHERE published = 1
      ORDER BY ordering
  9. SELECT *
      FROM www3fsf_user
      WHERE user_id = '0'
  10. SELECT id, link
      FROM www3menu
      WHERE link LIKE '%option=com_fsf%'
      AND published = 1
  11. SELECT jf_content.reference_field, jf_content.VALUE, jf_content.reference_id, jf_content.original_value

      FROM www3jf_content AS jf_content

      WHERE jf_content.language_id=1
           
      AND jf_content.published=1
       
      AND jf_content.reference_id IN(400,388,404,393,394,395,396,397,399,403,405,406,419,513)
       
      AND jf_content.reference_table='menu'
  12. SELECT *
      FROM www3fsf_faq_faq
      WHERE faq_cat_id = '2'
      AND published = 1
      ORDER BY ordering
  13. SELECT *
      FROM www3fsf_faq_faq
      WHERE faq_cat_id = '2'
      AND published = 1
      ORDER BY ordering
      LIMIT 0, 15
  14. SELECT *
      FROM www3fsf_faq_tags
      WHERE faq_id IN (42, 43, 44, 45, 165, 167, 169, 171, 173, 175, 177, 179, 181, 183, 185)
      GROUP BY tag
      ORDER BY tag
  15. SELECT COUNT(*) AS cnt
      FROM www3fsf_faq_tags
  16. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  17. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  18. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  19. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  20. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  21. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  22. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  23. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  24. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  25. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  26. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  27. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  28. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  29. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  30. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  31. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  32. SELECT id, title, module, POSITION, content, showtitle, control, params
      FROM www3modules AS m
      LEFT JOIN www3modules_menu AS mm
      ON mm.moduleid = m.id
      WHERE m.published = 1
      AND m.access <= 0
      AND m.client_id = 0
      AND ( mm.menuid = 388 OR mm.menuid = 0 )
      ORDER BY POSITION, ordering
  33. SELECT jf_content.reference_field, jf_content.VALUE, jf_content.reference_id, jf_content.original_value

      FROM www3jf_content AS jf_content

      WHERE jf_content.language_id=1
           
      AND jf_content.published=1
       
      AND jf_content.reference_id IN(79,330,35,326,331,347,345,329,319,292,335)
       
      AND jf_content.reference_table='modules'

Language Files Loaded

Untranslated Strings Diagnostic

None

Untranslated Strings Designer

None