How to Add an SRV Record in Plesk

SRV records point specific services — like VoIP, Microsoft 365, or game servers — to the right host and port. Unlike A or CNAME records, an SRV record includes the service name, protocol, priority, weight, port, and target host. This guide shows you how to add one in Plesk.

Before you begin

Have these details ready from your service provider:

• Service name (e.g. autodiscover, sip, minecraft)
• Protocol (tcp or udp)
• Target host, port, priority, and weight

Adding an SRV record in Plesk

1. Log in to Plesk.
2. Go to Websites & Domains → find your domain.
3. Click Hosting & DNS → DNS Settings.
4. Click Add Record and select SRV.
5. Fill in the fields:
   • Service name — enter without the underscore (Plesk adds it). E.g. autodiscover, not _autodiscover.
   • Protocol — enter without underscore. Typically tcp or udp.
   • Domain name — leave blank for the main domain.
   • Priority — lower = higher priority (e.g. 0, 10, 100).
   • Weight — for load balancing. Use 1 if only one target.
   • Port — the service port (e.g. 443, 5060, 25565).
   • Target host — the FQDN of the server (e.g. autodiscover.outlook.com).
6. Click OK to save.
7. If prompted, click Update to apply changes.

Common examples

Microsoft 365 autodiscover: Service autodiscover, Protocol tcp, Priority 100, Weight 1, Port 443, Target autodiscover.outlook.com

Minecraft: Service minecraft, Protocol tcp, Priority 0, Weight 5, Port 25565, Target mc.yourdomain.com

Verifying your SRV record

Run: nslookup -q=SRV _autodiscover._tcp.yourdomain.com 8.8.8.8

Or use dnschecker.org with the SRV record type.

Important notes

• Don't add extra underscores. Plesk adds them automatically — typing _sip creates __sip.
• Target must be a hostname, not an IP. Create an A record first if needed.
• Priority works like MX — lower numbers = higher priority.
• Weight is for load balancing among equal-priority records.

Troubleshooting

SRV record not resolving:

• Make sure you clicked Update in Plesk after adding the record.
• Check you didn't add an extra underscore to service or protocol.
• Wait 15–30 minutes for initial propagation.

Service not found after 48 hours:

• Confirm your nameservers point to Plesk. If using external DNS, add the record there.

Need help? Open a support ticket.