Migrating Away from members.linode.com and nodebalancer.linode.com
Traducciones al EspañolEstamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
All Linode Compute Instances and NodeBalancers are created with a default domain (forward DNS address) and a preconfigured rDNS (reverse DNS) entry for that domain. These default domains use the following patterns:
Linode Instances and NodeBalancers are accessible at these addresses for testing and other non-production purposes. While it’s much more favorable to provide access to these services with a personal or company domain name, it’s possible that some users have referenced the default domain within their own workflows, scripts, and applications.
Linode is changing the default domain and rDNS entry associated with every Linode Instance and NodeBalancer. This new domain name follows a new pattern, where [ip-address] is replaced with the primary public IPv4 address for your server:
Compute Instances and NodeBalancers:
Note that dashes (not periods) separate the values of the IP address.
If you don’t actively use the
nodebalancer.linode.com forward or reverse DNS in any of your scripts, applications, or domain settings, then this migration does not impact your properties.
If you do use your Linode Instance’s
members.linode.com or NodeBalancer’s
nodebalancer.linode.com forward or reverse DNS, please change your scripts, applications, or domain settings to either the new default domain, the IP address of your service, or your own FQDN (fully qualified domain name) if you’ve configured one for the service. In the future, Linode will end support for
For forward DNS, all Linodes and NodeBalancers can be accessed at the new address of
[ip-address].ip.linodeusercontent.com without further configuration. However, you should locate all instances of prior
nodebalancer.linode.com domain addresses in your codebase, application configuration files, etc., and change them to the new address.
In Cloud Manager, select Linodes from the navigation menu, then select the Linode for which you’d like to find the IP Address.
Under IP Addresses, select the top IPv4 address. This is the IP address that you can use with the new forward DNS.
In Cloud Manager, select NodeBalancers from the navigation menu, then select the NodeBalancer for which you’d like to find the IP Address.
On the right hand of the screen, under IP Addresses, note the top IPv4 Address. This is the address you can use to access your NodeBalancer’s forward DNS.
To find an existing
In Cloud Manager, select Linodes from the navigation menu, then select the Linode for which you’d like to find the domain.
Click on the Network tab.
Under IP Addresses, find the Linode Instance’s IP address and it’s corresponding reverse DNS entry.
The value under reverse DNS is the Linode Instance’s current
members.linode.comaddress, and instead find an
ip.linodeusercontent.comaddress, then your Linode Instance has already been configured to use the new domain.
To find an existing
In Cloud Manager, select NodeBalancers from the navigation menu, then select the NodeBalancer for which you’d like to find the domain.
On the Summary page, on the right of the page, find the NodeBalancer’s Hostname.
This is your NodeBalancer’s existing forward DNS.
nodebalancer.linode.comaddress, and instead find an
ip.linodeusercontent.comaddress, then your NodeBalancer has already been configured to use the new domain.
To change a Linode’s reverse DNS records, review the Configure Your Linode for Reverse DNS guide. The new forward DNS records already exist for your Linode’s IP, so you can set your Linode’s reverse DNS records to match the new name by following the linked guide.
This page was originally published on