Your IP address is 18.206.12.157
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 - All FAQs
What is a Core DNS provider?

 A core DNS service provider is a company who provides DNS service for the root level of the DNS tree (ICANN-sanctioned root operators).

 

Tags: core DNS, DNS, root operator
I have data confidentiality concerns regarding documents supplied to AFRINIC during evaluation process.

 AFRINIC is bound by Section 4(g) of the Registration Service Agreement (RSA) to non disclosure of any information that we receive from our members. The AFRINIC hostmaster team usually requests for supporting information to verify the information given in the online registration process.  The documentation supplied will be used solely to evaluate the requests against the AFRINIC policies in place.

Tags: confidentiality, policy, RSA
What are membership fees?

AFRINIC needs funds to sustain its operations , and therefore bills its members a fee calculated on the type and number of resources they hold. The AFRINIC fees schedule is available online . The fees may change from year to year according to operational costs and financial health of the organisation and upon validation by the Board of Directors.

How do I register a domain name ?

AFRINIC is not involved in domain name registration. Your ISP may be able to help you register a domain name. For more information about TLDs (Top Level Domains) and ccTLDs (Country Code Top Level Domain) registrations, please visit the ICANN website

The services I offer to my customers depend on the AFRINIC whois data. Can I get a copy of the db?


AFRINIC WHOIS data is for Internet Operations or Technical Research related to the Internet purpose only. It should not be used for advertising, direct marketing, marketing research or similar purpose. Use of AFRINIC WHOIS bulk data for these activities is explicitly forbidden. The redistribution of the provided bulk data is also explicitly forbidden.

If your organsiation usage of the data comply with thes terms and conditions then submit a request for AFRINIC Bulk Whois Data.

How can I request for bulk whois data?

The Bulk WHOIS request form can be downloaded from here. Complete the form by filling all the required details. As the hostmaster will approve the request only if the requester has provided all the necessary information required for Bulk WHOIS. The completed form should be either fax to AFRINIC Ltd on +230 466 6758 or sent via email to hostmaster@AFRINIC.net. As soon as the request is approved the hostmaster will send you the link to access the Bulk WHOIS along with the user name and password. 

 

Does AFRINIC support the "rwhois" protocol?

AFRINIC does not support the "rwhois" protocol formerly available to members from the ARIN service region. All (re)assignments and sub-allocations MUST be recorded in the AFRINIC whois database according to the procedure detailed here.

I am no longer able to query the AFRINIC whois database. I get error message "Your IP address has been blocked due to abusive behaviour".

Abusive behaviour regarding whois queries will automatically be blocked. The  process is detailed in Section1.7 of the database reference manual.

 

How do I get my IP address unblocked for whois queries?

You must send your request to hostmaster@afrinic.net

I am having routing/propagation issues with my IP addresses.

AFRINIC does not guarantee that any address space it allocates will be globally routable. This is because the filtering policies implemented by transit providers around the world are beyond our control. The best way to avoid filtering problems is to ensure that your network is numbered into the address range of a larger network , so that many addresses can be aggregated and announced globally as a single route. The shorter prefix of such a global route will increase its chances of being unaffected by the filtering policies of large transit providers. We have carried out extensive tests to ensure that the minimum allocation (/22) from AFRINIC blocks is not filtered.

 

I am receiving spam and network abuse from AFRINIC IPs!

Please see a detailed page dedicated to this question here

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

Display #
Page 3 of 12

Profile Information

Application afterLoad: 0.001 seconds, 0.72 MB
Application afterInitialise: 0.062 seconds, 2.70 MB
Application afterRoute: 0.100 seconds, 5.96 MB
Application afterDispatch: 0.151 seconds, 7.06 MB
Application afterRender: 0.339 seconds, 9.61 MB

Memory Usage

10129104

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 = 419)
      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 published = 1
      ORDER BY ordering
  13. SELECT *
      FROM www3fsf_faq_faq
      WHERE published = 1
      ORDER BY ordering
      LIMIT 30, 15
  14. SELECT *
      FROM www3fsf_faq_tags
      WHERE faq_id IN (31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45)
      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 = 419 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,292,335)
       
      AND jf_content.reference_table='modules'

Language Files Loaded

Untranslated Strings Diagnostic

None

Untranslated Strings Designer

None