Common Issues and Solutions

Record Format Requirements

Canonical Names

Some record types require canonical format (ending with a dot .):

CNAME Records

---
apiVersion: dns.cav.enablers.ob/v1alpha2
kind: RRset
metadata:
  name: test4.helloworld.com
spec:
  type: CNAME
  name: test4
  ttl: 300
  records:
    - test1.helloworld.com.
  zoneRef:
    name: helloworld.com
    kind: "Zone"

PTR Records

---
apiVersion: dns.cav.enablers.ob/v1alpha2
kind: RRset
metadata:
  name: 1.1.168.192.in-addr.arpa.helloworld.com
spec:
  type: PTR
  name: "1"
  ttl: 300
  records:
    - mailserver.helloworld.com.
  zoneRef:
    name: 1.168.192.in-addr.arpa
    kind: "Zone"

MX Records

---
apiVersion: dns.cav.enablers.ob/v1alpha2
kind: RRset
metadata:
  name: mx.helloworld.com
spec:
  type: MX
  name: "helloworld.com."
  ttl: 300
  records:
    - "10 mailserver1.helloworld.com."
    - "20 mailserver2.helloworld.com."
  zoneRef:
    name: helloworld.com
    kind: "Zone"

SRV Records

---
apiVersion: dns.cav.enablers.ob/v1alpha2
kind: RRset
metadata:
  name: database.srv.helloworld.com
spec:
  type: SRV
  name: "_database._tcp.myapp"
  ttl: 300
  records:
    - 1 50 25565 test2.helloworld.com.
  zoneRef:
    name: helloworld.com
    kind: "Zone"

TXT Records

TXT records must be properly quoted. If you see this error:

Parsing record content: Data field in DNS should start with quote (") at position 0

Solution: Ensure TXT records start and end with escaped quotes:

---
apiVersion: dns.cav.enablers.ob/v1alpha2
kind: RRset
metadata:
  name: txt.helloworld.com
spec:
  type: TXT
  name: "helloworld.com."
  ttl: 300
  records:
    - "\"Welcome to the helloworld.com domain\""
  zoneRef:
    name: helloworld.com
    kind: "Zone"

Common Error Scenarios

Zone Conflicts

• Error: Zone shows "Failed" status with "Already existing Zone" message
• Cause: Multiple zones with the same FQDN
• Solution: Remove duplicate zones or use different names

Missing Dependencies

• Error: RRset shows "Pending" status
• Cause: Referenced zone does not exist or is unhealthy
• Solution: Create the zone first or fix zone issues

API Connectivity

• Error: Resources stuck in "Pending" status
• Cause: PowerDNS API unreachable or authentication failed
• Solution: Check API URL, key, and network connectivity

Best Practices

1. Use canonical names for CNAME, PTR, MX, and SRV records
2. Quote TXT records properly with escaped quotes
3. Create zones before records to avoid dependency issues
4. Check for duplicates before creating resources
5. Monitor metrics for failed reconciliations