• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

URGENT: Updating DNS records in bulk

Eric Pretorious

Regular Pleskian
My VPS provider (BitronicTech) has changed the IP addreses assigned to my VPS and, as a result, all of the DNS entries are incorrect.

Is there a way to update the IP addresses all DNS records at once? e.g., Change all of the resource records (RR's) associated with a specific shared IP address?
 
After manually reassigning the IP addresses of each subscription...

Code:
Subscriptions -> Example.com -> Change Hosting Settings
Plesk warns:

New files of configuration for Apache web server were not built due to errors in configuration templates: nginx: [emerg] bind() to 66.232.99.58:80 failed (99: Cannot assign requested address) nginx: configuration file /etc/nginx/nginx.conf test failed . The detailed error message was e-mailed to you, so please check the e-mail, fix the errors, and click here to retry generating broken configuration or click here to retry generating of all configurations.
...so, after reading the "detailed error message [that] was e-mailed to [me]":

Unable to generate the web server configuration file on the host <www.example.com> because of the following errors:

nginx: [emerg] bind() to 66.232.99.58:80 failed (99: Cannot assign requested address)
nginx: configuration file /etc/nginx/nginx.conf test failed


Please resolve the errors in web server configuration templates and generate the file again.
...and verifying that there were no subscriptions that were using the OLD IP addresses (e.g., 66.232.99.58), I removed the OLD IP addresses...

Code:
Tools & Settings -> Toosl & Resources: IP Addresses
...and regernerated the broken configuration (by clicking the hypertext in the warning) but Apache/HTTPD still isn't listening on Port 80:

Code:
[root@www var]# netstat -tan
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address               Foreign Address             State      
tcp        0      0 0.0.0.0:3306                0.0.0.0:*                   LISTEN      
tcp        0      0 0.0.0.0:465                 0.0.0.0:*                   LISTEN      
tcp        0      0 127.0.0.1:10001             0.0.0.0:*                   LISTEN      
tcp        0      0 X.X.X.191:53           0.0.0.0:*                   LISTEN      
tcp        0      0 X.X.X.190:53           0.0.0.0:*                   LISTEN      
tcp        0      0 X.X.X.189:53           0.0.0.0:*                   LISTEN      
tcp        0      0 X.X.X.188:53           0.0.0.0:*                   LISTEN      
tcp        0      0 X.X.X.185:53           0.0.0.0:*                   LISTEN      
tcp        0      0 127.0.0.1:53                0.0.0.0:*                   LISTEN      
tcp        0      0 0.0.0.0:22                  0.0.0.0:*                   LISTEN      
tcp        0      0 127.0.0.1:3000              0.0.0.0:*                   LISTEN      
tcp        0      0 0.0.0.0:25                  0.0.0.0:*                   LISTEN      
tcp        0      0 127.0.0.1:953               0.0.0.0:*                   LISTEN      
tcp        0      0 127.0.0.1:12768             0.0.0.0:*                   LISTEN      
tcp        0      0 X.X.X.185:22           75.111.104.127:40126        ESTABLISHED 
tcp        0    240 X.X.X.185:22           75.111.104.127:41361        ESTABLISHED 
tcp        0      0 :::106                      :::*                        LISTEN      
tcp        0      0 :::110                      :::*                        LISTEN      
tcp        0      0 :::143                      :::*                        LISTEN      
tcp        0      0 :::8880                     :::*                        LISTEN      
tcp        0      0 :::465                      :::*                        LISTEN      
tcp        0      0 :::53                       :::*                        LISTEN      
tcp        0      0 :::21                       :::*                        LISTEN      
tcp        0      0 :::22                       :::*                        LISTEN      
tcp        0      0 :::25                       :::*                        LISTEN      
tcp        0      0 :::8443                     :::*                        LISTEN      
tcp        0      0 :::993                      :::*                        LISTEN      
tcp        0      0 :::995                      :::*                        LISTEN      
tcp        0      0 :::7080                     :::*                        LISTEN      
tcp        0      0 :::7081                     :::*                        LISTEN      
tcp        0      0 ::ffff:X.X.X.185:995   ::ffff:75.111.104.127:39881 TIME_WAIT   
tcp        0      0 ::ffff:X.X.X.185:995   ::ffff:75.111.104.127:39877 TIME_WAIT   
tcp        0      0 ::ffff:X.X.X.185:8443  ::ffff:75.111.104.127:60045 TIME_WAIT
Suggestions? Ideas?
 
Last edited:
Back
Top