An SRV record publishes the hostname and port for a service that uses DNS-based discovery. Use the service operator’s required values for service, protocol, name, priority, weight, port and target; an ordinary A record does not carry those fields.

Prepare the service information

Obtain the expected record name and all SRV fields from the application or service provider. Confirm the target hostname has the address records the service needs. A target is a hostname, while the connection port is a separate field.

Open the zone through My Tools in the client portal, then the DNS manager, or Cloudflare DNS → Zones → Records as staff. Review any SRV records already present for the same service name so you do not accidentally replace a deliberate multi-target configuration.

Add the typed record

1. Choose Add record and select SRV.
2. Enter the supplied Service, Protocol and Name in their respective fields.
3. Enter Priority, Weight and Port exactly as specified.
4. Enter the Target hostname and intended TTL.
5. Review the assembled full record name and field values before saving.
6. Confirm the saved record and run the service’s DNS-discovery check.

Do not combine a URL scheme or port into the target hostname when the form has a separate port field. Do not swap priority and weight simply because both are numbers; they serve different parts of the service’s requested configuration.

Check application support

The application must actually use SRV discovery for this purpose. Publishing an SRV record does not make every browser or client ignore its normal connection settings, and it does not open the service’s firewall port.

If a client still cannot connect, compare the published SRV answer, target address, listening port and application configuration. A correct DNS record and a running application are separate results.

Resolve form errors

Record the complete intended name, type and redacted validation/provider error. Check zone editing permission and limits before retrying. Leave unrelated working SRV targets in place while investigating; multiple entries can be intentional for that service.

See the PD Cloudflare DNS Blesta guide for related tasks, or explore the module.