Webnames is currently completing an IP address change across our Plesk Web Hosting infrastructure. As part of this change, legacy hosting IP addresses in the 209.15.37.x range are being decommissioned and replaced with new 198.148.174.x addresses.
If your website is hosted on a Webnames Plesk Web Hosting server and has recently become unavailable, your DNS or CDN configuration may still reference one of our legacy hosting IP addresses.
Your website content has not been removed or migrated to another hosting platform. In most affected cases, website accessibility can be restored by updating the legacy IP address to the corresponding new address.
Check your DNS records
Review the DNS records for your domain, particularly A records associated with:
Your root domain
wwwor other hosted subdomainsAny other hostname that should direct visitors to your Webnames-hosted website
If you find one of the Old IP Addresses below, replace it with the New IP Address shown on the same row.
Old IP Address | New IP Address |
209.15.37.16 | 198.148.174.130 |
209.15.37.23 | 198.148.174.131 |
209.15.37.27 | 198.148.174.132 |
209.15.37.28 | 198.148.174.133 |
209.15.37.29 | 198.148.174.134 |
209.15.37.30 | 198.148.174.135 |
209.15.37.21 | 198.148.174.136 |
209.15.37.34 | 198.148.174.137 |
209.15.37.9 | 198.148.174.138 |
209.15.37.35 | 198.148.174.139 |
209.15.37.61 | 198.148.174.141 |
209.15.37.71 | 198.148.174.142 |
Only replace an IP address if it exactly matches an Old IP Address listed above. DNS records containing other IP addresses or values should not be changed.
If you use Cloudflare or another CDN or proxy service
If your website uses Cloudflare or another CDN, reverse proxy or similar service, your public DNS records may not contain a Webnames hosting IP address.
Instead, the Webnames Plesk server may be configured as the origin server within your CDN or proxy service.
Review the origin server configuration with your provider. If the origin IP matches one of the Old IP Addresses in the table above, replace it with the corresponding New IP Address.
If your CDN or proxy configuration does not reference one of these legacy addresses, do not change the origin IP based solely on this notice.
Why did my website suddenly become unavailable?
Webnames previously operated these Plesk Web Hosting services using IP addresses in the 209.15.37.x range. Those legacy addresses are now being decommissioned.
A website or CDN configuration that continues to direct traffic to a decommissioned address will no longer be able to reach the Webnames hosting server.
Updating the affected DNS or origin-server configuration to the corresponding new IP address directs traffic to the current address for the same Webnames hosting service.
I made the change but my website is still unavailable
After making the required change, allow for the updated DNS information to take effect.
If your website remains unavailable, first confirm that:
Every relevant DNS A record has been reviewed.
No applicable hostname still references an Old IP Address from the table above.
If you use a CDN or proxy, its origin server configuration has also been checked.
You replaced the Old IP Address with the New IP Address from the same row of the conversion table.
No unrelated DNS records were changed.
If none of the legacy addresses appear in your DNS or CDN origin configuration, the website issue may be unrelated to this IP address change and should be investigated separately.
What about email and SPF records?
This web hosting IP address change does not mean that customers should indiscriminately replace IP addresses found in email-related DNS records.
A small number of customers have legacy Webnames hosting IP addresses explicitly defined within their SPF records. Where Webnames manages the affected DNS, we are updating those specific legacy Webnames references to our standard SPF inclusion:
include:_spf.webnames.ca
For these updates, no other values within the customer's existing SPF record are being altered.
If you receive an automated DNS Updated notification from Webnames relating to this SPF change, the notification is expected.
Previous Notifications About This Change
Webnames has sent multiple notifications to affected hosting customers in advance of the retirement of our legacy Plesk Web Hosting IP addresses. These communications explained the required DNS update, provided the applicable old and new IP addresses, and encouraged customers to complete the change before the legacy addresses were decommissioned.
We recognise, however, that the person troubleshooting a website today may not have seen those earlier notifications. Some common situations include:
The contact information associated with the Webnames account is no longer current.
The notifications were delivered to another person within the organisation, such as the account owner, billing contact or a previous technical contact.
Responsibility for the website or DNS has changed since the Webnames account was originally established.
The messages were filtered, redirected or otherwise overlooked among other email.
A third-party web developer, IT provider or DNS/CDN provider manages the website configuration and did not receive the notifications sent to the Webnames account contact.
If you did not receive our previous notifications, you can still make the required change now. Follow the IP address conversion table and instructions in this article to update any affected DNS records or CDN origin configuration.
We also recommend reviewing the contact information associated with your Webnames account so that future service and infrastructure notifications reach the appropriate people within your organization.
Need assistance?
If you are unsure whether your website is affected, cannot determine which record needs to be changed, or have made the appropriate change and your website remains unavailable, please contact Webnames Support.
Our team can also help you verify the authenticity of communications you have received regarding this IP address change.