Written steps are the source of truth for this guide.
Videos and screenshots are supporting demonstrations. Follow the written steps and confirm the current screen, account, registry, and resource state before acting.
For supplier prefixes using Platform delivery in i.lease
When a prefix is configured as platform_managed, i.lease requires a successful
Whois maintainer match before setup can be saved and before submission can pass final validation.
When This Guide Applies
- You are in Lease Out and configuring a prefix in Set Up IP Details.
- The prefix setup mode is switched to Platform delivery /
platform_managed. - The UI shows the Maintainer Information block and the button Confirm maintainer setup.
How i.lease Verifies Maintainers
i.lease checks only these Whois fields: mnt-by, mnt-lower, and mnt-routes.
| RIR | Required maintainer value(s) | Match rule | Whois server used by i.lease |
|---|---|---|---|
| RIPE |
mnt-by: HK-LARUS-1-MNTmnt-lower: HK-LARUS-1-MNTmnt-routes: HK-LARUS-1-MNT
|
Per-field match. All three fields must contain the required value. | whois.ripe.net |
| APNIC | MAINT-LCS-HK |
Across-fields match. Value can appear in any of the three maintainer fields. | whois.apnic.net |
| AFRINIC | LARUS-SERVICE-MNT, CIL1-MNT |
Across-fields match. Both values must be found across the three maintainer fields. | whois.afrinic.net |
| ARIN / LACNIC | No platform maintainer template configured in product. | Automatic platform-maintainer verification is not configured. | N/A |
Where Suppliers Should Update Maintainer Data
| RIR | Portal / Tool | Recommended update path |
|---|---|---|
| RIPE | https://apps.db.ripe.net/ | Edit the related inetnum object in RIPE Database Webupdates. |
| APNIC | https://www.apnic.net/manage-ip/myapnic/ | Use Resources > Maintainers and/or Resources > Whois updates. |
| AFRINIC | https://my.afrinic.net/ https://afrinic.net/whois-web/public/query |
Update maintainer-related fields in the target resource object and verify via AFRINIC Whois tools. |
Supplier Action Steps by RIR
RIPE
- Sign in to RIPE Database Webupdates.
- Find the object that covers the target prefix.
- Add required values to
mnt-by,mnt-lower, andmnt-routes. - Submit changes and wait for Whois visibility.
- Return to i.lease and click Confirm maintainer setup.
APNIC
- Sign in to MyAPNIC.
- Open maintainer or Whois object update workflow.
- Ensure
MAINT-LCS-HKis present in maintainer-related fields for the resource. - Save and wait for Whois visibility.
- Return to i.lease and click Confirm maintainer setup.
AFRINIC
- Sign in to MyAFRINIC and open the target resource object.
- Ensure both
LARUS-SERVICE-MNTandCIL1-MNTare associated in maintainer-related fields. - Use AFRINIC Whois query tools to confirm data is visible.
- Return to i.lease and click Confirm maintainer setup.
What Happens After You Click Confirm
- i.lease sends a Whois query using the prefix CIDR and the RIR-specific Whois server.
- The system parses
mnt-by,mnt-lower, andmnt-routes. - If all required values are found, status is shown as Verified in Whois.
- If not matched, the UI shows Missing maintainer entries (for example,
mnt-routes: HK-LARUS-1-MNT). - For
platform_managed, setup save is blocked until verification is matched.
Troubleshooting Checklist
- Wrong object updated: verify supplier changed the object covering the exact CIDR.
- Wrong field: i.lease checks only
mnt-by,mnt-lower,mnt-routes. - Value mismatch: maintainer IDs must match exactly.
- Whois propagation delay: wait a few minutes and retry Confirm maintainer setup.
- Unsupported RIR template: for ARIN/LACNIC, coordinate with i.lease operations first.
Technical Notes for Internal Teams
- Session endpoint:
POST /api/i_lease/monetization/supplier-import/sessions/{sessionId}/items/{itemId}/maintainer-verify - Offer endpoint:
POST /api/i_lease/supplier-import/offers/{offerId}/maintainer-verify - Response payload includes:
matched,missing,required,found_fields,whois_server.
