Create an SRV DNS record in My.GARMTECH or Plesk (format and examples)

An SRV record tells clients which server and port provide a specific service (for example SIP/VoIP, XMPP chat, or other service discovery use cases).

Because SRV records have several fields (priority, weight, port, target), they are a frequent source of DNS mistakes. This article explains the format and how to create an SRV record on GARMTECH services.

SRV record format (what each field means)

An SRV record normally looks like this:

_service._proto.example.com  TTL  IN  SRV  priority  weight  port  target

• _service: the service name (starts with _), for example _sip or _xmpp.
• _proto: _tcp or _udp.
• priority: lower number = preferred record.
• weight: load balancing between records with the same priority.
• port: the port where the service listens (for example 5060).
• target: the hostname of the server providing the service (must resolve to A/AAAA).

Example

_xmpp._tcp.example.com  86400  IN  SRV  10  5  5223  server.example.com

Where to create SRV records at GARMTECH

• My.GARMTECH DNS Management — use this if the domain uses GARMTECH nameservers (ns1.garmtech.com, ns2.garmtech.com, ns3.garmtech.com).
• Plesk DNS Settings — use this if you manage the DNS zone inside Plesk for a hosted domain.

Option A — Create an SRV record in My.GARMTECH

1. Log in to My.GARMTECH and open Domains.
2. Click the domain and open DNS Management.
3. Choose Add Record → SRV.
4. Fill in the fields provided by your service vendor. Depending on the form you may see:

• Service / Name (for example _sip)
• Protocol (for example _tcp)
• Priority, Weight, Port
• Target (for example sipserver.example.com)

Save changes.

Option B — Create an SRV record in Plesk

1. Log in to Plesk for your hosting service.
2. Open Websites & Domains → DNS Settings.
3. Click Add Record and select SRV.
4. Enter the values and click OK, then click Update to apply changes.

Common mistakes (and how to avoid them)

• Using a CNAME as the target. Many clients require the target to be a real hostname with an A/AAAA record.
• Wrong “Name/Host” format. Some panels want _service._proto only, others want the full name. Follow your control panel hints and vendor instructions.
• Forgetting the trailing dot. Some DNS editors automatically add your domain. If you enter server.example.com, ensure it does not become server.example.com.example.com.

After you add the record

• Allow time for DNS propagation.
• If the service still cannot find your SRV record, verify the final record with a DNS lookup tool (or ask the vendor what exact name they query).