...
An example of how this should look:
We can verify this information by querying the ARIN database, like so:
| No Format |
|---|
https://whois.arin.net/rest/org/CONNEEXPCO-81/pft?s=conneexpco-81 https://whois.arin.net/rest/poc/6CONNEXPCO-ARIN?s=6connexpco-arin |
Once you have an LIR in ProVision, it is trivial to query the API of its resource from the ProVision database using the resource Id number.
...
We've got everything together so let's do some SWIP'ing. Our example domain is 67.221.244.160/27. Here is what it looks like in ARIN Online:
From here we can see that the /27 is currently undivided as far as ARIN is concerned. ARIN's database is arranged in a hierarchy, so it first looks to see if that /27 exists in its
database (nope), then it looks for blocks it *does* know about it which contains it. Here we see 6connect's the /20 as its immediate owner:
...
The story of this block is therefore: "ARIN was given this IP Block by ICANN, then ARIN did a Direct Allocation of a /20 to 6connectEXPCO." And in a bit here, 6connect will ProVision will do a detailed re-assign to MedaTeckle, a made-up company whose headquarters is the birthplace of Genghis Khan.
...
So I open up the gear menu for the IP block right here on the resource page and I get this screen:
I select the LIR in the upper-left (currently selected: 6connectexample), the Net Name is automatically generated from the LIR + netblock, and we are using the "CONNEEXPCO-81" organization within the 6connect LIRexample LIR. This will supply the ARIN API Key to make this all happen. I hit Detailed Reassign and after a few minutes of waiting for ARIN to catch up, here are the results:
Our /27 has been delegated to our new fake company, here:
...