IPv4 planning for hosted applications

Know how your application reaches the internet

IPv4 remains widely used, but public address space is limited. Hosting may use a dedicated address, shared web endpoint, proxy, or translated network. The right model depends on protocols, mail requirements, partner allowlists, and whether users need direct access.

HostGanga plan details determine address assignment and management options. Review live pricing and confirm any requirement for dedicated, additional, reverse-DNS, or reassignable addresses before ordering.

Clear addressing model

Determine whether traffic terminates directly on your server, on shared hosting, or through another gateway.

Record alignment

Keep A records, firewall sources, application bindings, and certificate hostnames consistent.

Responsible use

Use name-based hosting and private addresses where they fit rather than requesting unnecessary public IPs.

Plan every dependency on the address

Inventory A records, external allowlists, monitoring targets, license bindings, mail reputation, and reverse DNS before an address change. Prefer hostnames in application configuration when the integration supports them, because hard-coded addresses increase migration work.

• Bind services only to intended interfaces
• Restrict administrative ports by source
• Coordinate forward and reverse DNS for mail use

Migrate with an overlap window

Lower DNS TTL ahead of a planned move, configure and test the new destination, then update records. Keep the old service available when possible until cached answers expire, while ensuring state-changing traffic cannot diverge between systems.

Frequently asked questions