SRV records publish a service location and port, while CAA records restrict which certificate authorities may issue for a domain.
Applies to: Nameservers and DNS records
DNS tells internet services where to find a website, mail server or other service. Changes can be technically correct yet appear inconsistent for a time because recursive resolvers cache earlier answers until their TTL expires.
Key information
| SRV fields | Service, protocol, name, priority, weight, port and target. |
|---|---|
| CAA fields | Flag, tag such as issue or issuewild, and certificate-authority value. |
| Risk | Incorrect SRV can break client discovery; restrictive CAA can block otherwise valid certificate issuance. |
Before you start
- Confirm that you are authorised to manage the domain and identify its authoritative DNS provider.
- Export or record the complete current DNS zone and previous TTL values before making changes.
Step-by-step
- Copy all fields from the service or certificate provider and keep priority, weight and port in their separate inputs.
- For SRV, ensure the target is a hostname that resolves and is not a CNAME where the relevant standard forbids it.
- For CAA, include every certificate authority genuinely required, including wildcard issuance where applicable.
- Save the record and query the exact service or root name publicly.
- Test the consuming application or certificate issuance before removing any previous record.
Confirm the result
- The public record preserves all fields and the dependent service accepts it.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| The panel provides one combined SRV value field. | DNS interfaces represent SRV components differently. | Follow the displayed field labels and verify the final public answer in standard order. |
| Let's Encrypt or a paid CA suddenly cannot issue. | A CAA policy does not authorise that CA or an inherited parent-domain CAA applies. | Query CAA from the requested hostname upward and add the correct authority before retrying. |
When to contact Tudor Internet
Open a ticket through the Customer Portal when the checks above do not resolve the issue, when an action is unavailable for your service, or when continuing could risk data loss or service interruption. Include the following so the request can be investigated efficiently:
- The full domain name
- The current and intended registrar or nameservers
- Any registry or transfer error shown
- Whether website or email service is currently live
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.
Related articles
- A, AAAA, CNAME, MX and TXT records explained
- Use CAA records without blocking certificate renewal
- Check DNS with dig, nslookup and public resolvers
- Create and troubleshoot A and AAAA records
- Plan a DNS change with minimal downtime
Last reviewed: 2026-07-18.
