Skip to content

Troubleshooting

Diagnose and resolve common issues with Bindy DNS operator.

Quick Diagnosis

Check Overall Health

# Check all resources
kubectl get all -n dns-system

# Check CRDs
kubectl get bind9instances,dnszones,arecords -A

# Check events
kubectl get events -n dns-system --sort-by='.lastTimestamp' | tail -20

View Status Conditions

# Bind9Instance status
kubectl get bind9instance primary-dns -n dns-system -o yaml | yq '.status'

# DNSZone status
kubectl get dnszone example-com -n dns-system -o yaml | yq '.status'

Common Issues

See Common Issues for frequently encountered problems and solutions.

DNS Record Label Matching Issues

If you're seeing "No matching DNSZone found" errors: - Records use labels to match DNSZones via label selectors - Common mistake: Record missing required labels or labels not matching DNSZone selector - See DNS Record Issues - Record Not Matching DNSZone for detailed troubleshooting

Debugging Steps

See Debugging Guide for detailed debugging procedures.

FAQ

See FAQ for answers to frequently asked questions.

Getting Help

Check Logs

# Operator logs
kubectl logs -n dns-system deployment/bindy --tail=100

# BIND9 instance logs
kubectl logs -n dns-system -l instance=primary-dns

Describe Resources

# Describe Bind9Instance
kubectl describe bind9instance primary-dns -n dns-system

# Describe pods
kubectl describe pod -n dns-system <pod-name>

Check Resource Status

# Get detailed status
kubectl get bind9instance primary-dns -n dns-system -o jsonpath='{.status}' | jq

Escalation

If issues persist:

  1. Check Common Issues
  2. Review Debugging Guide
  3. Check FAQ
  4. Search GitHub issues: https://github.com/firestoned/bindy/issues
  5. Create a new issue with:
  6. Kubernetes version
  7. Bindy version
  8. Resource YAMLs
  9. Operator logs
  10. Error messages

Next Steps