Once your IPv4 lease has been approved and your address block has been provisioned, the next step is making those addresses available on the internet. This involves more than assigning IPs to servers. You must correctly announce the address space, configure routing security, and complete supporting network tasks to ensure reliable connectivity.
If you're wondering how to announce leased IPv4 addresses, this guide explains the technical deployment process, including BGP, Route Origin Authorizations (ROAs), Reverse DNS (rDNS), and SWIP. It also clarifies which responsibilities belong to the tenant and which are typically handled by the leasing platform.
What Does It Mean to Announce an IPv4 Prefix?
An IPv4 prefix is not reachable on the public internet until it is advertised through the global routing system.
Announcing an IPv4 prefix means:
- Publishing the network through Border Gateway Protocol (BGP)
- Making the prefix reachable from other networks
- Allowing internet traffic to reach your infrastructure
- Establishing global routing visibility
Without a proper announcement, your leased IPv4 addresses cannot be used for public-facing services.
Understanding BGP
Border Gateway Protocol (BGP) is the routing protocol that connects internet networks worldwide.
When announcing leased IPv4 space, BGP tells other Autonomous Systems (AS) that your network is responsible for a specific prefix.
BGP enables:
- Global internet routing
- Traffic optimisation
- Redundant connectivity
- Multi-homed deployments
- Enterprise-scale networking
Businesses operating their own Autonomous System Number (ASN) typically announce leased IPv4 space directly through their upstream providers.
What the Tenant Is Responsible For
After the IPv4 block has been provisioned, the tenant is generally responsible for the technical deployment of the address space.
Typical tenant responsibilities include:
- Configuring BGP sessions
- Announcing the leased prefix
- Operating an ASN, where applicable
- Configuring routers
- Assigning IP addresses to infrastructure
- Monitoring routing performance
- Maintaining network security
The tenant is also responsible for ensuring that the leased addresses are used in accordance with the lease agreement and acceptable use policies.
What the Platform Typically Handles
The IPv4 leasing platform provides the foundation that allows deployment to begin.
Typical platform responsibilities include:
- Provisioning the leased IPv4 block
- Verifying ownership and allocation records
- Providing lease documentation
- Issuing a Letter of Authorization (LOA), where required
- Supporting registry compliance
- Assisting with technical onboarding
The platform generally does not manage the tenant's routers, BGP configuration, or production network.
Configure a Route Origin Authorization (ROA)
A critical security step is creating a Route Origin Authorization (ROA) using Resource Public Key Infrastructure (RPKI).
A ROA specifies which Autonomous System Number is authorised to originate a particular IPv4 prefix.
Benefits include:
- Protection against BGP hijacking
- Improved routing validation
- Increased trust between network operators
- Better routing security
- Compliance with modern routing best practices
Many networks now validate ROAs before accepting route announcements.
Configure Reverse DNS (rDNS)
Reverse DNS maps an IP address back to a hostname.
Proper rDNS configuration is especially important for:
- Email servers
- Web hosting
- Cloud infrastructure
- Authentication services
- Enterprise applications
Correct rDNS improves:
- Email deliverability
- Service reputation
- Troubleshooting
- Network administration
Most organisations configure reverse DNS immediately after routing is operational.
Understanding SWIP
Depending on the applicable Regional Internet Registry (RIR) and deployment model, organisations may also need SWIP (Shared WHOIS Project) records.
SWIP is commonly used to record downstream customer assignments and improve WHOIS accuracy.
Benefits include:
- Better ownership transparency
- Accurate customer assignment records
- Improved abuse handling
- Registry compliance
- Operational visibility
SWIP requirements vary between RIRs, so organisations should follow the policies applicable to their region.
Test Your Route Announcement
Before placing production services online, organisations should verify that the announcement is working correctly.
Recommended checks include:
- Confirm BGP propagation
- Validate ROA status
- Verify reverse DNS
- Test global reachability
- Monitor routing visibility
Network monitoring platforms can confirm that the prefix is being announced correctly across the global internet.
Best Practices for IPv4 Deployment
Successful deployments follow structured operational procedures.
Recommended practices include:
- Maintain accurate documentation
- Enable RPKI whenever possible
- Configure reverse DNS promptly
- Monitor routing continuously
- Review prefix announcements regularly
- Track IP reputation
- Maintain secure router configurations
These practices improve long-term network stability.
Common Deployment Mistakes
Many routing issues result from simple configuration errors.
Common mistakes include:
- Incorrect BGP announcements
- Missing ROAs
- Misconfigured reverse DNS
- Failure to monitor routing
- Incomplete documentation
- Incorrect ASN configuration
Careful testing before production deployment significantly reduces these risks.
The Future of IPv4 Routing
Although IPv6 adoption continues to expand, IPv4 remains critical for enterprise networking.
Current trends include:
- Increased RPKI adoption
- Better routing validation
- Improved BGP monitoring
- Enhanced IP intelligence
- Greater automation
- Continued IPv4 demand across enterprise infrastructure
These technologies continue improving the security and reliability of leased IPv4 deployments.
Building a Reliable IPv4 Deployment
Understanding how to announce leased IPv4 addresses is essential for successful network deployment. Proper BGP configuration, Route Origin Authorizations (ROAs), reverse DNS, and SWIP where applicable all contribute to secure, compliant, and reliable internet routing.
By understanding which technical responsibilities belong to the tenant and which are handled by the leasing platform, organisations can deploy leased IPv4 resources confidently while maintaining strong routing security and operational stability.
About IPv4 Hub
IPv4 Hub helps ISPs, cloud providers, hosting companies, and enterprises lease, buy, and sell IPv4 address resources through a secure and transparent marketplace. In addition to providing verified IPv4 inventory and streamlined provisioning, IPv4 Hub supports customers with technical onboarding, documentation, registry compliance guidance, and best practices for deployment. With expert assistance covering routing preparation, IP intelligence, blacklist screening, and operational readiness, IPv4 Hub enables organisations to deploy reliable IPv4 resources with confidence and build scalable network infrastructure for long-term growth.
Explore our inventory to simplify your IPv4 address sourcing process.