Static IP for Business

What a static IP enables

• Hosting inbound services. Anything reachable from the internet — mail server, web server, VPN concentrator, video surveillance, FTP for partners — needs a stable destination address.
• Allowlisting by partners and vendors. SaaS providers, banks, and B2B partners often allowlist customer IPs for security. A changing IP breaks the allowlist on every change.
• Site-to-site VPNs with peer endpoints. Many VPN configurations identify the remote peer by IP. Dynamic IPs require dynamic DNS workarounds or pre-shared identifiers.
• Reverse DNS records. Some services (notably mail servers) require a working reverse DNS lookup that matches the sender. ISPs only let you control reverse DNS on static IPs.
• SSL/TLS certificates tied to IPs. Less common today but still relevant for some legacy systems.
• BGP and multi-homing. Running your own AS number and announcing routes requires static address space.

What a static IP does not do

• Make outbound services work better. Web browsing, email through cloud providers, SaaS access — all of these work identically on a dynamic IP.
• Improve performance. Speed and latency depend on the link, not the address.
• Provide security. A static IP is no more or less secure than a dynamic one; what matters is what's behind it.
• Hide you from tracking. If anything, a static IP is more identifying because it stays the same — easier to attribute behavior to you over time.

The dynamic-IP workarounds

For businesses that don't want to pay for static IPs, there are workarounds for some use cases:

For many small businesses, "use a cloud SaaS instead of self-hosting" eliminates the static-IP need entirely.

How many static IPs do you need

Most ISPs offer:

• 1 static IP. Use with NAT to host multiple services on different ports. Cheapest tier.
• Block of 5 usable (typically a /29). One for each separately-routed service. Common for offices with multiple inbound services.
• Block of 13 usable (/28) or larger. For complex networks needing IP-per-server.

A block lets you assign one public IP per service without port-translating, which simplifies firewall rules and avoids port conflicts. The IETF recommends one IP per service for clean architecture; cost realities often dictate one IP plus NAT.

Reverse DNS specifics

Reverse DNS (PTR records) maps IPs to hostnames. Forward DNS maps hostnames to IPs. They are independent records; both should be configured and ideally match.

For a mail server:

• Forward: mail.example.com → 203.0.113.45
• Reverse: 203.0.113.45 → mail.example.com

If reverse is missing or doesn't match the sending hostname, many receiving mail servers reject or score down the mail as spam. The ISP delegates reverse DNS for your IP block on request; on a single static IP, they typically let you set the PTR via a control panel.

Static IPs and IPv6

IPv6 changes the static-IP economics. With abundant address space, providers commonly allocate a /56 or /48 to each customer — that's millions or billions of addresses, all of which are "static" in the sense that the allocation doesn't change. The whole "pay extra for one static address" model is an IPv4 artifact. For IPv6-reachable services, every host can have a stable, public address by default.

Whether you can use IPv6 in practice depends on whether your remote services support it. Inbound VoIP, partner APIs, and many enterprise systems are IPv4-only. IPv6 is a complement, not a replacement, in most current business setups.

CGNAT and the loss of static IPs

Some ISPs — especially mobile carriers and fixed-wireless providers — put customers behind CGNAT. CGNAT means your "public" IP is shared with many other customers. Inbound connectivity is impossible: there is no port that maps directly to your network. Even paying for a "static IP" on CGNAT often means a static private IP behind CGNAT, which is useless for hosting.

If you need to host services on a CGNAT-only ISP, the options are: ask for a CGNAT bypass (some ISPs offer it as an extra), use a cloud bastion to terminate inbound traffic, or change ISPs.

Cost-benefit for a small business

A reasonable test: list every service that would require a static IP. If the list is empty or contains only marginal items, save the money. If the list contains anything you can't easily move to a cloud SaaS, get a static IP — the operational simplicity is worth the cost.

Frequently Asked Questions

What is a static IP?

A public IP address assigned to your business connection that does not change over time. A dynamic IP, by contrast, is reassigned periodically by the ISP — your address today may be different next week. Static IPs are essential for hosting services that other parties need to reach reliably.

Does my business need a static IP?

Yes if you host any inbound service — mail server, web server, VPN gateway, VoIP PBX, surveillance system accessible from outside. Yes if vendor or partner systems need to allowlist your office IP for access. Probably no if you only use the internet for outbound traffic (web browsing, email through cloud providers, SaaS access).

What is reverse DNS and why does it matter?

Reverse DNS maps an IP address back to a hostname. Mail servers reject mail from IPs without proper reverse DNS as a spam signal. If you run an on-premises mail server, your static IP needs a reverse DNS record matching your sending domain. ISPs typically let static-IP customers set reverse DNS; dynamic IPs cannot.

How is a static IP different from a domain name?

A domain name (e.g., office.example.com) is a human-readable label that resolves to an IP via DNS. A static IP is the actual numeric address. You can have a static IP without a domain, or a domain pointing at a static IP, or a domain pointing at a dynamic IP via dynamic DNS. For many purposes (mail server reverse DNS, partner allowlisting) the IP itself matters; for end-user access, the domain matters.

Can I get static IPs over IPv6?

Yes. IPv6 has plenty of address space and providers typically allocate a /56 or /48 prefix to business customers, all of which is static. IPv6 deployment varies — not every business ISP offers IPv6, and not every remote service is reachable over IPv6 — but for IPv6-capable workloads, static IPv6 is standard rather than an extra-cost option.