Lease In Contract Network Operations Guide

Route, PTR, and NS operations inside the i.lease Lease In contract workflow

After a lease-in contract is created, operational network delivery continues through the contract-level Route, PTR, and NS modules. These are the real execution requests used to prepare the leased prefix for use.

This guide explains how to start from the contract workflow, open each module, submit the required requests, and understand the status and follow-up actions for each step.

What These Modules Do

Step 1: Start From the Contract Route Config Wizard

Open the contract network operations entry from the contract workflow. The Route Config Wizard shows the real request progress for each paid allocation and tells you which module is required next.

1. Review the summary cards for Route, PTR, NS, and LOA.
2. Find the target allocation row by its CIDR.
3. Check the current badges and the Next step field.
4. Use the primary action button such as Open Route, Open PTR, or Open NS.
5. If PTR or NS is currently external and you want to manage it inside i.lease, use Enable PTR or Enable NS before opening the module.

Step 2: Submit the Route Object First

Route object creation is the first operational delivery step for a prefix. If the route request is missing or rejected, complete the Route page before moving to PTR or NS.

Route Page Actions

1. Open the target allocation’s Route page.
2. Review existing route object rows, if any.
3. Use Create Route Object when no usable route object exists yet.
4. Use the row action menu to View, Edit, or Delete a route object when updates are still allowed.
5. If the LOA file is available, use Download LOA.
6. Use Set Geofeed and Verify Geofeed when the route workflow requires geolocation follow-up.

Required Route Form Fields

The route object form requires the operational and authorization details for the leased prefix.

1. IP Prefix and IP CIDR
2. ASN
3. Data Center Country, Data Center City, and Data Center Name
4. Authorizer
5. Abuse Contact, Abuse Mobile, Abuse Email, and Abuse Address
6. Optional fields such as Data Center Address and Remark

If the authorizer is changed and the new value is not English, the page also requires Authorizer English and an Authorizer File before submission.

When Route Editing Is Locked

If the latest Route request is already submitted, processing, or waiting on supplier/platform follow-up, the page becomes effectively read-only for update actions. In that state, track the request instead of trying to overwrite it.

Step 3: Submit PTR Records

Use the PTR page when reverse DNS PTR entries are required for the allocation. PTR requests are submitted as a list of IP-to-hostname pairs.

1. Open the target allocation’s PTR page.
2. Review the current request status, owner badge, helper text, and reject reason if one exists.
3. Review the current PTR entries table if records already exist.
4. Click Submit PTR Request to open the PTR form.
5. Add one or more rows of IP Address and DNS Hostname.
6. Use Add row or Remove to adjust the request payload.
7. Submit the request and then track it in the request history section.

PTR Validation Rules

1. Every row must contain both an IP address and a DNS hostname.
2. The IP address must be a valid IPv4 value.
3. If the request quota or contract conditions block submission, the page shows the reason and blocks the action.

PTR Request History

The PTR page keeps a request history list and a detail view. Use it to review who submitted a request, how many entries were included, the audit record, and why a request was rejected if it did not pass review.

Step 4: Submit NS Delegation

Use the NS page when reverse zone delegation is managed inside i.lease. This page submits the nameserver payload for the allocation’s reverse zone.

1. Open the target allocation’s NS page.
2. Review the current request status and owner type.
3. Confirm the prefilled Reverse Zone and Subnet values.
4. Enter the Nameservers, one per line.
5. Choose whether the same nameservers should be used for the whole delegation by setting Same NS for all.
6. Click Save Changes to submit the NS request.

NS Request Rules

1. The NS request cannot be updated while it is already under review or processing.
2. If NS management is disabled for the allocation, the page treats it as externally managed and the operational work should happen outside the i.lease NS workflow.
3. If the last request was rejected, review the history and resubmit a corrected nameserver payload.

Recommended Operational Order

1. Start in the Route Config Wizard and check the next required step.
2. Complete the Route request first if it is missing or rejected.
3. Submit PTR if PTR management is enabled and the page says it is required.
4. Submit NS if NS management is enabled and the page says it is required.
5. Track progress in each page’s status badges and request history instead of resubmitting while a request is locked.

Status and Follow-Up Tips

• Not submitted means the operational request still needs to be created.
• Submitted or Processing means follow-up is in progress and the current payload should usually not be overwritten.
• Rejected means you should open the relevant module, correct the real payload, and resubmit.
• Platform and Supplier owner badges show which side currently owns the next action.
• If PTR or NS is marked as External, manage that part outside the internal request module unless you explicitly enable internal management first.