CAA (Certificate Authority Authorization) Records are DNS records that specify which certificate authorities (CAs) are allowed to issue SSL/TLS certificates for your domain. Managing these records enhances your domain’s security by preventing unauthorized certificate issuance.
Here’s how to manage CAA Records in OzSpeed hPanel:
Steps to Manage CAA Records in OzSpeed #
Step 1: Log in to OzSpeed hPanel #
- Visit OzSpeed hPanel.
- Enter your credentials and click Log In.
Step 2: Access DNS Zone Editor #
- From the dashboard, navigate to the Domains section.
- Select the domain for which you want to manage CAA Records.
- Click Manage DNS or DNS Zone Editor.
Step 3: Add a New CAA Record #
- In the DNS Zone Editor, scroll to the CAA Records section.
- Click Add Record or Create Record.
- Fill out the required fields:
- Host/Name:
- Enter
@
for the root domain (e.g.,example.com
). - Specify a subdomain if applicable (e.g.,
www
orsecure
).
- Enter
- Type: Select CAA.
- Flag:
- Use
0
for standard configurations. - Use
128
to indicate critical records that must be followed by the CA.
- Use
- Tag:
- Use
issue
to authorize a specific CA to issue certificates for your domain. - Use
issuewild
to authorize a CA to issue wildcard certificates. - Use
iodef
to specify an email or URL for violation reports.
- Use
- Value:
- Specify the CA or other details depending on the tag.
- Example:
letsencrypt.org
for issuing certificates via Let’s Encrypt.
- TTL (Time to Live): Use a default TTL (e.g., 300 seconds).
- Host/Name:
- Click Save to create the record.
Step 4: Edit an Existing CAA Record #
- Locate the CAA Record you wish to update.
- Click Edit next to the record.
- Modify the fields (e.g., flag, tag, or value) as required.
- Save the changes.
Step 5: Delete a CAA Record #
- Find the CAA Record you want to remove.
- Click Delete next to the record.
- Confirm the deletion.
Example CAA Record Configurations #
Host/Name | Type | Flag | Tag | Value | TTL |
---|---|---|---|---|---|
@ | CAA | 0 | issue | letsencrypt.org | 300 |
@ | CAA | 0 | issuewild | digicert.com | 300 |
@ | CAA | 0 | iodef | mailto:admin@domain.com | 300 |
Common Use Cases for CAA Records #
- Authorize Specific Certificate Authorities:
- Restrict SSL/TLS certificate issuance to trusted providers like Let’s Encrypt, DigiCert, or Sectigo.
- Wildcard Certificates:
- Use the
issuewild
tag to specify which CAs can issue wildcard certificates for your domain.
- Use the
- Violation Reporting:
- Use the
iodef
tag to receive violation reports via email or a URL when unauthorized certificate issuance is attempted.
- Use the
Troubleshooting CAA Records #
- Certificate Requests Failing:
- Ensure the CA you’re authorizing matches the one attempting to issue the certificate.
- Check that the
issue
orissuewild
tags are configured correctly.
- Invalid Records:
- Verify the syntax and ensure no conflicting CAA Records exist.
- Changes Not Reflecting:
- Clear your local DNS cache:
- Windows:
ipconfig /flushdns
- macOS:
sudo killall -HUP mDNSResponder
.
- Windows:
- Use a DNS propagation tool like dnschecker.org to verify global updates.
- Clear your local DNS cache:
Additional Notes: #
- Backup DNS Settings:
- Before making changes, back up your DNS records to ensure you can restore them if needed.
- Propagate Changes:
- Allow up to 24–48 hours for global DNS propagation.
- Keep Records Updated:
- Regularly review CAA Records to ensure they align with your security and certificate management needs.