Your IP address allocation is changing
IP address change FAQs
FAQs
01
We're consolidating legacy public IPv4 pools into a modern, resilient set of ranges. Some services with static IPs or routed subnets will receive new public IP details during an overnight maintenance window.
02
Customers with a static public IP (/32) or a routed public subnet (/30–/27).
03
The work will start on 1st November 2025 and run until the end of December 2025. You will be contacted nearer the time with an accurate timeline.
04
Yes. Your notice will include your new IP or routed block.
05
Expect a brief reconnection (usually 1-5 minutes) at least once during your window. Some customers may need to reconnect manually.
06
No.
07
Most users will not need to take action. Your WAN router will automatically receive the new IP address once it reconnects after the change window has passed.
You only need to act if:
- Your router does not automatically reconnect and requires a manual IP update.
- You use your public IP for systems, partners, or external services (for example, firewall or VPN allowlists, DNS records, SFTP access, or licensing).
If either applies, please update those systems with your new IP address once the change is complete.
08
You may receive a new routed block. We'll provide details and coordinate if you need a parallel test/renumber plan.
09
No. After the cutover, traffic to the old IP will not reach your service. Please update allowlists/DNS promptly.
10
Please use an external "what's my IP" checker from behind your router and confirm it matches the IP in our notice.
11
We'll recreate existing PTRs where feasible. If you need a different hostname, reply to your notice with the required value.
12
Site-to-site VPNs that reference your public IP address will require the peer to be updated on the remote side. Tunnels should re-establish once updated.
13
Update DNS/port-forwards/allowlists to the new IP. For mail, also review SPF/DKIM/DMARC and any provider allowlists.
14
Please change it to obtain the new IP address automatically or update it manually.
15
No changes will be made to your internal network. Please review any port-forward rules that hard-code the old public IP.
16
No changes will be made to IPv6. (If you don't currently use IPv6, this work won't enable it.)
17
No. Existing DDoS protections and filtering policies remain in place.
18
Please plan updates for immediately after the window. If you run business-critical services, please contact us beforehand to coordinate.
19
We can't guarantee specific addresses, but please tell us your requirements and we'll advise on what's possible.
20
No onsite visit is expected.
21
Restart your router/firewall, verify your new IP address, and check your DNS settings and allowlists. If issues persist, please contact support (connectivity.support@nasstar.com) with your account/username, current public IP address, and a brief description.
Latest insights
- Secure networks
- Secure networks
- Cloud
Transforming connectivity, security, and collaboration
We’re joined by experts from Fortinet to explore how a unified security strategy can help businesses stay secure.
Leigh Walgate
Managing Director (Secure Networks Division)
The business case for SASE: From complexity to clarity with Nasstar’s Adoption Framework
Traditional network security models simply can’t keep up with today's business models. Find out why SASE is the solution.
Rebecca Hopwood-Keay
Marketing Manager (Secure Networks)
Cloud migration: A step-by-step approach
AI can only shine if it’s built on strong cloud foundations. Find out how to ensure you've got the basics right before investing in AI.
Sean Morris
Chief Technology Officer