Provide a stable reference point
A static address can support applications that depend on a consistent internet endpoint. Whether it is included, and how it is presented, depends on the selected service.
A static address can support applications that depend on a consistent internet endpoint. Whether it is included, and how it is presented, depends on the selected service.
A single address and a routed address block have different requirements. IPv4 availability, allocation size, service compatibility and any charges must be confirmed.
IPv6 requirements can be assessed with the access service, router, firewall, DNS and applications. Availability, prefix size and configuration are not assumed.
A public address alone does not make an application reachable. NAT, firewall rules, service policies and the application configuration must also support the intended traffic.
An address assigned with a service is not automatically portable to another provider. Customer-held resources require authority, compatible routing and an agreed service design.
Plan permitted access, DNS changes and dependencies before changing an address. Publicly reachable systems require appropriate security controls and ongoing administration.
A static address does not itself provide encryption, firewall protection or guaranteed reachability. Hosting and remote access should be designed with restricted access and suitable security controls.
Address assignments, block sizes, reverse DNS options, IPv6 support and any routing arrangements must be confirmed for the service. No address inventory or allocation entitlement is implied by this page.
Explain hosting, remote access, allowlisting or other requirements.
Identify the existing public addresses, DNS and service dependencies.
Review the router, firewall, NAT and permitted inbound traffic.
Confirm availability, authority, service terms and the migration plan.
Inclusions depend on the selected service. Check the current plan information or proposal; do not assume the same addressing applies to every access type.
A requirement can be assessed. Availability, justification, service compatibility, routing and any charges need confirmation.
Not automatically. Provider-assigned addresses are generally tied to the service arrangement. Portability and routing authority require separate assessment.
It must be confirmed for the specific service and equipment. This page does not promise an IPv6 allocation or prefix size.
Tell us about your locations, applications, existing services and the outcome you need. KernWi-Fi can assess suitable options and prepare a proposal with a clear scope.