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

Input Better DNS record validation

danami

danami

Silver Pleskian
We regularity see users adding invalid DNS records into the panel that Plesk happily accepts:

Eg 1. Invalid SPF records (users include double quotes for their SPF records):
Code: 
"v=spf1 include:spf.protection.outlook.com -all"

Eg. 2. Invalid SRV records (users enter in the underscore in the service name and protocol not knowing that Plesk automatically adds this so you end up with double underscores).
Code: 
__sip.__tls.example.com.

All of this could be corrected very easily with better DNS record validation.
 
You must log in or register to reply here.

Similar threads

TorbHo
Resolved After migrating to a new Plesk server: DKIM records end with ;;
Replies
2
Views
367
TorbHo
TorbHo
T
Migrator doesn't adjust DNS properly (certain conditions)
Replies
6
Views
2K
TomBoB
T
C
Unable to create A DNS record with underscore in Plesk: The specified domain name is not valid. You need to specify a valid domain name like domain.co
Replies
6
Views
3K
scsa20
scsa20
C
Resolved Webmail will not resolve on new domain
Replies
4
Views
2K
Ch3vr0n
C
L
Issue Spam-/Mailproblems
Replies
1
Views
1K
Peter Debik
P
Back
Top