• 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!
  • 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.

Updating the DNS Template - Changing SPF TXT Record to Reflect new IP Addresses

Eric Pretorious

Regular Pleskian
The IP addresses assigned to our servers have changed so it's time to update the default SPF information contained in the DNS records for ALL of the domains hosted on our servers:

OLD
Code:
v=spf1 +ip4:173.236.23.185 +ip4:173.236.23.188/30 +a +mx -all

NEW
Code:
v=spf1 +ip4:69.160.255.188/30 +ip4:69.160.255.192 +a +mx -all

However, when we update the resource record in the DNS template and then "Apply the changes to all zones...",
Panel will apply changes from the template to all DNS zones including the customized ones. Note that user-modified records always remain intact. For example, if the template contains a new record that was already added by a customer, Panel will keep the customer's record.

... Plesk reports "The DNS zone template was successfully applied." but the DNS records of individual domains are not updated.

Have I overlooked something?
 
Never mind:

Performing the changes a second time then "Apply the changes to all zones..." the changes are reflected across all zones.
 
Back
Top