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

DNS and SOA records configuration help

Nitin12

New Pleskian
Hello,

I have installed Parallels Plesk 12.0.18 installed on my Windows Server. I have found issues with my DNS and SOA records having issues it says I have not configured my DNS and SOA records when I do a DNS diagnosis.

I am looking forward for any of you to help me to setup my configure the records for me correctly so that my domains issues could be solved. It would be a great help if you could do this for me. You can see a link below to know the errors I have for my domain name. I have hosted multiple domain names on the same server with Plesk.

URL - https://www.domaindiagnosis.com/index.php?query=jagstechnologies.com

I will look forward for your time and corporation to help me setup Plesk as soon as possible. At the moment I have installed Plesk with a Trial key to understand how to use and to get it working for my requirements and look for someone to help in this setup as Parallels is not providing direct support for this but on the forum I do expect a help from people over here.
 
I'm going to be mainly basing it off of http://www.dnsstuff.com/tools#dnsReport|type=domain&&value=jagstechnologies.com since that gives you more of a run down then domaindiagnosis.com.
  • Recommended expire time is 14 days, so under the SOA record you'll want to set the Expire Interval to 14 days.
  • You should set it to use IETF and RIPE recommend serial format.
  • You should add a SPF record to include Google (learn more about what to put down for Google's SPF record at https://support.google.com/a/answer/178723?hl=en )
  • You should add all of Google's MX records to ensure deliverability at the recommended weights (you can find that information at https://support.google.com/a/answer/174125?hl=en )
  • Your PTR record should be on the primary domain and not on a sub domain (this means that the domain name value should be blank).
  • The AAAA record is not reachable, if you are using IPv6 then ensure your IP configuration is setup properly, otherwise remove the AAAA records along with any NS AAAA record types.
  • For every NS record on the primary domain, you should have an A record for said NS record.
    • If you have an NS record of server1.jagstechnologies.com you should have an A record for server1.jagstechnologies.com
    • Likewise if you have any other NS records
  • Here's what my primary domain DNS records looks like: http://gyazo.com/bae3613645a802ea3edb84aee365b2da
  • Here's what one of my secondary domain DNS records looks like: http://gyazo.com/c3c00f3f22b29d6587c18c23f9aa4708 (primary thing you want to note on here is MX record and the TXT record for the SPF)
Hope this gives you some guidance.
 
Back
Top