Your IP address is 44.220.249.141
Please select your question category
Search FAQs
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

FAQs - AFRINIC member

FAQ for Existing members

 Route object is an object created in Internet Routing Registry to specify the Autonomus System Number "ASN" that will propagate this exact IP prefix to Internet. It can also be used to give information about the organisation that advertises this prefix. Route objects are usually protected and only a person with the authorised password can change them.

Route objects are usually used by Internet Service Providers and Upstreams to validate that routes received from their peers are legitimate. This usually help eliminate routes hijacking if used by all providers. They don't eliminate the need for BGP configuration and advertisement.

 

 

Two methods are available – via the myafrinic portal or by updating the whois database using the email method.

a) Updates via the myafrinic portal can be done as follows:-

Log into https://my.afrinic.net
Go to Resources -> IPv4 Resources
Click on "+" to expand on the target allocation
Click "Add Assignment"

You need to repeat the above process for all assignments that will be registered. Any changes you make from MyAFRINIC will be instantly updated in the AFRINIC Whois database.

b) Update of assignments on the whois database by email

It is possible to send one batch job in one email (containing multiple assignments) using the procedure listed here

 

 We recommend that you add the sub-allocation via the myafrinic portal.

You may do this via https://my.afrinic.net as follows:

o Log into https://my.afrinic.net
o Go to Resources -> IPv4 Resources
o Click on "+" to expand on the target allocation
o Click "Add Sub-Allocation"

o Fill in the form and submit

The AFRINIC hostmasters will then revert back to you for evaluation of the request.

 

 

An LIR may receive an additional allocation when about 80% of all the address space currently allocated to it has been used in valid assignments and/or sub-allocations. A new allocation can also be made if single assignment or sub-allocation requires more addresses than those currently held by the LIR.

 We recommend that you request for the additional allocation via the myafrinic portal.

You may do this via https://my.afrinic.net as follows:

o Log into https://my.afrinic.net
o Go to Resources -> IPv4 Resources
o Select Request New Allocation
o Fill in the form and Submit

 

As per the policy for Autonomous System Numbers, an AFRINIC member can request for an ASN if it is already or plans to be multihomed.

A "multihomed" site is a site with more than one transit provider.

 We recommend that you request for an ASN via the myafrinic portal.

You may do this via https://my.afrinic.net as follows:

o Log into https://my.afrinic.net
o Go to Resources -> AS Numbers

o Fill in the form and Submit (Kindly note that you must mention the ASN and contact emails of at least 2 of your BGP peers)

 

 We recommend that you request for the additional allocation via the myafrinic portal.

You may do this via https://my.afrinic.net as follows:

o Log into https://my.afrinic.net
o Go to Resources -> IPv6 Resources
o Select Request IPv6 resource
o Fill in the form and Submit

 

An excellent Reverse Delegation "Mini-Howto" is available from the documents' section of our website here. You may also contact hostmaster@afrinic.net if you have properly followed the instructions in the document, and reverse delegation still looks broken/non-functional.

 All reverse delegations can be registered via the myafrinic member portal as follows:-

a) via the myAFRINIC member portal

Log into https://my.afrinic.net
Go to Resources -> reverse delegation
Click '+' on the target prefix
Click 'add reverse delegation'
Update the details and submit

b) The steps via the email method to register/update the domain objects on the whois database are documented here

The AFRINIC Database provides mechanisms to control who can make changes in the database and what changes they can make. The distinction of "who" vs. "what" separates authentication from authorisation. The maintainer object serves as a container to hold authentication filters.

Until the launch of AFRINIC’s IRR in 2013, AFRINIC members used the RIPE IRR to register their objects. Now that AFRINIC has its own IRR, members are encouraged to populate it with their objects instead of using the RIPE IRR. 

To register your route objects in the AFRINIC IRR, please see Creating Route Object 

 Members can check their free/used allocation via the MyAFRINIC member portal. A query from the whois database can also give an approximate "visual" impression of how much has been utilised, for example to return a list of all registered assignments from 10.0.0.0/16 block; you can use:

  1. CLI: type the command whois -h whois.AFRINIC.net -m -r 10.0.0.0/16 in your client.
  2. Web-Based: choose advanced search, type 10.0.0.0/16 in the query field and select -m and -r options.

 

 

For utilisation to appear in myAFRINIC, you must register the IP addresses in use in the database. You may do this via https://my.afrinic.net as follows:

  • Log into https://my.afrinic.net
  • Go to Resources -> IPv4 Resources
  • Click on "+" to expand on the target allocation
  • Click "Add Assignment"

You need to repeat the above process for all assignments that will be registered.

Profile Information

Application afterLoad: 0.003 seconds, 0.72 MB
Application afterInitialise: 0.123 seconds, 2.70 MB
Application afterRoute: 0.164 seconds, 5.96 MB
Application afterDispatch: 0.210 seconds, 7.06 MB
Application afterRender: 0.409 seconds, 9.61 MB

Memory Usage

10124040

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 = 400)
      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 = '6'
      AND published = 1
      ORDER BY ordering
  13. SELECT *
      FROM www3fsf_faq_faq
      WHERE faq_cat_id = '6'
      AND published = 1
      ORDER BY ordering
      LIMIT 15, 15
  14. SELECT *
      FROM www3fsf_faq_tags
      WHERE faq_id IN (61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 145)
      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 = 400 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