RIPE NCC Objects
All ripe NCC objects
Role/Maintainer pair
To create a role/Maintainer pair, please go here and fill out the form.
First, you need to pick a name for your maintainer, it can be anything, but it needs to end in -MNT for it to be valid. After doing this, you will also need to create a name for your role, this can also be whatever you choose, though it's common for it to be your network name followed by NOC. You can also create a person instead, should you so choose.
Next, fill out your address and email. I would recommend getting a PO box or alternate mail address, as THIS IS PUBLIC INFORMATION. Once you've filled out this form, click submit and you now have a role and maintainer pair!
Organization
Another important and required role for being assigned ASNs and Internet Number resources is an organization object. (You don't have to be a company to make this) this object lists out your networks information, contact info and management. To create one, you should go here! And fill out the form
At the very top, it should ask what maintainers you would like to use as MNT-BY (This grants full control of your org, so generally this should only be the MNT you created when you followed these steps.
The next field will be organization, and it will be set to AUTO-1. There is no need to change this, it's purely the ORG-ID.
Org name is what you want your organization to be called. This should be your first and last name if you are a natural person, or your exact company name if you are a LLC/Corp etc.
org type should be set to other, and you don't need to change it.
Address is the same as what you used when you created your role/MNT pair, unless your org is different from the two, which is uncommon.
email should also be the same as your role/MNT, generally noc@beako.net with the domain being your own, of course.
Abuse-c you likely don't have yet, so click the bell to create one while in your org creation, then enter the email you want to use for abuse contact and click submit.
Finally, MNT-REF is other organizations you want to be able to assign you resources, this would generally be your LIR but can be anyone who is willing to assign IP addresses to you.
Once you've filled out all that information, click submit on the bottom and you now have an org object!
person
A person role is generally used for providing information about who maintains an object in more detail, generally needed for AS-SETs and some other objects. Thankfully it's super easy to create one! Just go here and fill out the info!
MNT-BY should already be set assuming you have a MNTer, if you don't follow this guide and make one!
Person is the name of the person or group you want to use, don't need to be too general as you either want this to be yourself or a dedicated groups contact that handles abuse or administration.
address is the address of you or your group, I highly recommend a PO box or similar mailbox obfuscation service as the RIPE database is public!
phone number should just be your or some phone number you/your group are reachable at
NIC-NDL should be AUTO-1 so it creates a valid ripe user handle for you
Once that's filled out just click submit and you have a person object now!
Once you create the object it will generate the handle code at the top in the format of person "HANDLE-CODE-HERE", which you should copy if you are making this object to use in another object like an AS-SET
as-set
An important object in the RIPE database is the AS-SET, this is typically what upstream providers and carriers use to generate prefix lists and filters for your ASN/network. To create one you should go here and input the following information
MNT-BY which should be autofilled by default with your MNTer object assuming you have one (if you don't, go here and make one)
AS-SET should be the name of your AS-SET, which can be anything so long as it isn't in use by someone else (it will complain if it is)
tech-c and admin-c need a person role, which you can create by following this page
If it doesn't exist, you will need to click the plus button and add the members subgroup, this is where you specify the AS-SETs and ASNs you want in your AS-SET, in the format of ASN, ASN, AS-SET
Once you do that click submit and you have a new AS-SET!
A further note is an AS-SET can contain only other AS-SETs, so you can chain down a clean structure like
- AS-RTT - Root org AS-SET
- AS-RTT-DS - downstreams of AS-RTT
- AS-RTT-CORE - ASNs run by AS-RTT
Note your new AS-SET will have the as-set section editable, this is an existing object
Domain
The domain object is used for delegating nameservers for reverse DNS zones. To create one, you should go here and there will be a form to fill in. It should look like the below
The prefix is where you put in the prefix you have rDNS delegation control over in. You don't need to write it in in.addr.arpa ipv6.arpa format, just input the prefix.
YOU MUST DELEGATE THE PREFIX ON YOUR NAMESERVERS BEFORE YOU TYPE THEM HERE.
nserver is where you type the nameservers that host your rDNS delegation. You must have at least two but can use the arrow to add more of them as needed.
Once you've filled in all this information, you can click submit and you've delegated your prefixes rDNS to your new provider!