• Inviting everyone who uses WordPress management tools in Plesk
    The Plesk team is conducting a 60-minute research session that includes an interview and a moderated usability test.
    To participate, please use this link .
    Your experience will help shape product decisions and ensure the tools better support real-world use cases.

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

nethubonline
Forwarded to devs Possible DMARC Bypass - Spoofed MAILER-DAEMON Return-Path Not Rejected
Replies
9
Views
2K
nethubonline
nethubonline
TorbHo
Resolved After migrating to a new Plesk server: DKIM records end with ;;
Replies
2
Views
2K
TorbHo
TorbHo
T
Migrator doesn't adjust DNS properly (certain conditions)
Replies
6
Views
3K
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
5K
scsa20
scsa20
C
Resolved Webmail will not resolve on new domain
Replies
4
Views
3K
Ch3vr0n
C
Back
Top