System Guide

IP Address and ASN Administration System


LACNIC's IP and Autonomous System Number (ASN) administration system has three basic elements that are related in the following manner:

  • Organization or Entity;
  • Contacts or Users;
  • Internet Resources (IP addresses or ASNs)

[Fig. 1 - Database relationships]


An Entity represents an organization for which there exists an IP address or ASN registered in LACNIC's database.

For each Entity an identifier is created (owner-id). This identifier is made up by the country code, an abbreviation of the organization's name and the identifier of its Regional Registry, in this case LACNIC.

This identifier is made up by the following information:

  • Name of the organization;
  • Name of the administrative contact;
  • Postal address,
  • Country;
  • Telephone number;
  • Identifier of the organization's administrative contact;
  • Date of creation;
  • Latest date that this information was updated.

An Entity is usually created when LACNIC allocates an Internet Resource.

Most Entities currently existing in LACNIC's database were created by importing from ARIN's database information relating to the Internet resources allocated to organizations within Latin America and the Caribbean.

The Administrative Contact associated with an Entity is responsible for maintaining the organization's information.

This Administrative Contact has the autonomy to modify any information, including the information associated with the Entity's resources. Hence the importance of updating this information.


LACNIC's IP address and ASN administration system has an authentication system by means of a username and password through a page that is coded with the SSL protocol.

In order to register a system user, the following form must be completed:

[ FIG 2 - User Registration ]

This form must be completed with the following user information:

  • Name;
  • E-mail;
  • Postal address;
  • Number of the locality;
  • Complement of the locality (if existant) (For example, floor number within the building);
  • Postal code, if existant;
  • City;
  • State, if existant;
  • Country;
  • Language in which the user wishes to use the system;
  • Telephone country code;
  • Telephone area code;
  • Telephone number;
  • Telephone extension;
  • Personal password;
  • Password confirmation. If a user forgets his/her password, this reminder may be requested.

After completing this form, the system will send a user registration confirmation request to the e-mail previously provided. This e-mail includes a URL link, which the user must access in order to confirm the registration.

Once the user registration request is confirmed though the above mentioned URL, a new e-mail is sent confirming the registration. This e-mail informs the USER-ID created by the system for the new user.

This USER-ID must be used to log on to LACNIC's IP address and ASN administration system.

[ FIG 3 - User Authentication ]

Once the user is logged on to the system, the first screen he/she will see is the following:

[ FIG 4 - Main ]


The resources distributed and administered by LACNIC are:

  • IPv4 address blocks;
  • Autonomous System Numbers (ASNs); and
  • IPv6 address blocks.

In order to be registered in LACNIC's database, these resources must be associated to an Entity.

The same entity may have one or more of these resources.

Each one of the resources may have one or more associated contacts.

Initially, when LACNIC allocates a resource, the only existing contact is the Entity's administrative contact.

This contact may register other new contacts for the resource.

In the case of IP addresses, in addition to the administrative contact, we have:

  • TECH-C (The BLOCK's technical or administrative contact).

This contact's function is to administrate the IP blocks. In other words, to make new allocations, modify or remove existing allocations, and make DNS delegations.

An the administrative contact of an Entity may register a block's technical contact through LACNIC's IP address and Autonomous Numbers administration system. In order to do so, he/she must log on to the system and, in the "Entities" area, click on the Name of the Entity that has the block.

Then he/she must click on the block for which he/she wishes to change the contact in the "Blocks" area.

[ FIG 5 - Entity Info. ]

Then he/she must proceed to change the contact that appears as "Administrative." This refers to the block's administrative contact.

[FIG 6 - Contact ]

In the case of ASNs we have the following contacts:

  • ROUTING-C (Technical Contact) and
  • ABUSE-C (Security Contact).

The function of the technical contact (routing-c) is to register or modify the information relating to the routing policy adopted by the Autonomous System identified by the ASN. Registering the routing policy is optional.

The security contact (abuse-c) does not have administrative functions in the system. But it is an advantage for the Entity to have a specific person to respond to complaints of abuse.

The entity's administrative contact may register an ASN's technical and security contacts through LACNIC's IP address and ASN administration system. In order to do so, he/she must log on to the system and, in the "Entities" area, click on the Name of the Entity that has the block.

Then, in the "Autonomous Systems" area, he/she must click on the ASN for which he wishes to change the contact, and proceed to change the contact that appears as "Administrative." This means the ASN's administrative contact, and "Security."

[ FIG 7 - ASN Contact ]