SRV Record Generator
Build a valid _service._proto record for SIP, XMPP, Minecraft, LDAP or Autodiscover — and read an existing one back in plain English.
The SRV Record Generator runs entirely in your browser. Your host names and ports never leave your device.
Open the Port Number Lookup
SRV Record Generator について
SRV is the one record type whose name carries data. The service and the transport are underscore labels in front of the domain — _sip._tcp.example.com — and the answer carries four fields: a priority that picks the group of servers to try, a weight that splits traffic inside that group, the port, and the host. Getting them in the right order matters, because nothing validates a hand-typed record until a client silently fails to connect. This generator starts from the services people actually publish, checks every field against the format rules, and prints both a BIND zone line and the separate columns a DNS dashboard asks for. Paste an existing record and it reads it back the other way.
機能
- Presets for SIP, XMPP, Matrix, Minecraft, LDAP, Kerberos, Autodiscover, CalDAV, STUN and TURN
- Validation of priority, weight, port and TTL ranges
- Catches IP addresses in the target, the most common SRV mistake
- Understands "." as a deliberate no-service target
- Zone file line and dashboard fields from the same input
- Decode mode that explains a pasted record field by field
- A dig command to check what was published
- Everything is generated on your device
SRV Record Generator の使い方
- Pick a service preset, or type the service and protocol yourself
- Enter the domain and the host that runs the service
- Set priority, weight and port — the preset fills in a sensible port
- Copy the zone line or the individual fields into your DNS provider
例
入力
sip over tcp on example.com, host sipserver.example.com:5060
出力
_sip._tcp.example.com. 3600 IN SRV 10 60 5060 sipserver.example.com.
The owner name carries the service and transport; the rdata carries priority, weight, port and target.
よくあるエラーとトラブルシューティング
- The record was rejected because the target is an IP address. — SRV targets must be hostnames. Publish an A or AAAA record for the server and point the SRV target at that name instead.
- Clients ignore the second server entirely. — Priority is a strict preference, not a load balancer — the lower number is used until it fails. To split traffic between servers, give them the same priority and different weights.
- The DNS dashboard rejects the name with underscores. — Some panels want only the service part in the name field and add the domain themselves. Enter _sip._tcp rather than the full owner name, and check the preview the panel shows before saving.
よくある質問
- What does an SRV record look like?
- The name is _service._proto.domain and the value is four fields: priority, weight, port and target — for example _sip._tcp.example.com. 3600 IN SRV 10 60 5060 sipserver.example.com.
- How do priority and weight differ?
- Priority chooses the group: clients use the lowest number available and only fall back when those hosts fail. Weight splits traffic between hosts that share a priority, in proportion to the numbers, so 60 and 20 sends three times as much to the first.
- What does a target of a single dot mean?
- It is the standard way to publish that the service is deliberately not available at this domain. Clients read it as a definitive no rather than falling back to guessing a default host.
- Do I need an SRV record for a Minecraft server?
- Only if you run on a non-default port and want players to connect using the bare domain. _minecraft._tcp.example.com pointing at your host and port removes the need for anyone to type a port number.
- Why is _tcp written with a leading underscore?
- The underscore marks the label as a protocol prefix rather than a real host name, which keeps it out of the normal hostname namespace and stops it colliding with a machine actually called tcp.
関連ツール
すべての ArrayKit ツール