ARIN IP Allocation Policy | MNCHOST

An IP address is necessary to access the Internet; however, a globally unique IP address is not required to be able to access the Internet at large. MNCHOST will normally assign, either dynamically through DHCP or statically, an RFC1918 Private IP address to a end customer. In order for the end-user to be able to access the Internet at large, MNCHOST will NAT, potentially at multiple points, an end-users connection on its route to the Internet. MNCHOST realizes there may be technical reasons for requiring a publicly routable IP address. In these events, a customer must formally request a Public IP Address. A request for a Public IP Address does not guarantee assignment of a Public IP Address.

Static Public IP assignment is only provided to business class customers that can properly justify and demonstrate an operatonal need for a Publicly Unique IP Address or block.

In general, MNCHOST will assign an IP Address to a customer in the form of an IP Address block. The size of the block may vary on a case by case basis and usually requires additional planning information to prevent excess waste of IP Addresses. MNCHOST will not modify existing firewall rules or NAT rules in lieu of assigning a Public IP Address to an end-user or customer.

If a customer is assigned an IP address and uses a different IP Address, the IP Address will potentially be considered as fraudulent. MNCHOST will not guarantee that a fraudulent addresses will be able to get to the Internet. If a fraudulent IP Address interferes with another customer's assigned IP Address or block, service may be suspended until the fraudulent IP Addresses are removed.

Prior to any potential assignment of a Publicly Unique IP Address or block, MNCHOST will request and require response to certain questions including but not limited to:

• How many IP addresses does the end-user or customer intend to need within 3 months?
• How many IP addresses does the end-user or customer intend to need within 12 months?
• What is the purpose of the IP addresses?
• Do you want a reverse PTR record associated with the IP Address?
• Will you be running an SMTP or Email Server on this IP address?

IP Address block size and availability will be determined by the above metrics. A few examples of valid justification include:

• Needing to run an internal Exchange server
• Having VPN requirements
• RDP connectivity needs

When submitting a request for IP address space, please include a response to the above questions so that the delegation process can flow as smoothly as possible.

In order to obtain additional IP Address assignments, the existing IP addresses must have a utilization rate equal or greater than 80%. Any request for additional IP space must include sufficient documentation of existing usage.

Please note that if requesting a smaller subnet and eventually need to upgrade to a larger subnet, MNCHOST cannot guarantee that the next address block will be available. Should the need for additional IP Addresses arise, MNCHOST may assign a separate, larger block with the contingency that any prior IP Address Assignment be returned to MNCHOST within 2 months.