DNS Integrations
Connect once. Infraova operates from there.
Connect the DNS infrastructure your clients already use. Infraova uses that connection to continuously monitor changes, understand what matters, propose the right remediation, execute approved fixes, verify the live result, and keep monitoring.
How it works
The connection is what lets Infraova enter the operational loop.
Without a DNS provider connection, Infraova can monitor. With it, Infraova can operate — detecting changes, proposing fixes, executing approved remediations, and verifying the result against live infrastructure.
Your client infrastructure
Cloudflare · GoDaddy · Namecheap · Porkbun · DigitalOcean · Vercel · Route 53 · Squarespace
Infraova
What the connection enables
Not just visibility. Operational capability.
Connecting a DNS provider gives Infraova what it needs to move through the full operational loop — not just to observe, but to act on approved decisions.
Without a connection
With a connected provider
Monitor changes — passively
Monitor changes — with full DNS record context
Detect failures — from scan results
Detect failures — with before/after record state
Propose a fix — manually described
Propose the exact record value via provider API
Remediate — someone edits DNS manually
Remediate — executed directly via connected provider
Verify — next scheduled scan
Verify — immediately after execution
Report — what you manually documented
Report — complete operational record, automatically
The approval boundary
You stay in control. Infraova does the work.
Connecting a DNS provider does not give Infraova automatic permission to change anything. Every proposed remediation requires explicit approval before execution.
Infraova never modifies client DNS automatically.
When a fix is needed, Infraova generates a specific remediation proposal — the exact record, the reason, and the expected outcome. Your team reviews it. Your team authorizes it. Only then does Infraova execute the change through the connected provider. The approval is recorded with timestamp and actor identity. The connection provides capability. Your authorization provides permission.
Detect
Infraova identifies what changed or failed. The event is captured with full context.
Propose
Infraova prepares the exact remediation — the specific DNS record or configuration required.
You approve
Your team reviews the proposal and authorizes execution. This step is always explicit.
Execute
Infraova carries out the approved change via the connected provider API.
Verify
Infraova re-checks live infrastructure to confirm the expected state was achieved.
Record
The full audit trail — who approved, what changed, when it was verified — is preserved automatically.
Supported DNS providers
Connect the providers your clients already use.
Each provider connection gives Infraova the operational access needed to monitor continuously, execute approved remediations, and verify the result against live infrastructure.
Cloudflare
DNS infrastructure
Pull all active zones from your Cloudflare account. Infraova monitors every zone continuously and executes approved remediation via the Cloudflare API.
Connect →GoDaddy
DNS infrastructure
Import all registered domains from your GoDaddy account using the API. Infraova monitors and operates across every domain in the portfolio.
Connect →Namecheap
DNS infrastructure
Pull registered domains from Namecheap once API access is enabled on your account. Infraova monitors and executes approved fixes through the operational workflow.
Connect →Porkbun
DNS infrastructure
Pull registered domains from your Porkbun account using the API. Infraova continuously monitors every domain and acts on approved remediations.
Connect →DigitalOcean
DNS infrastructure
Pull managed domains from your DigitalOcean account using a personal access token. Infraova monitors and operates across every managed domain.
Connect →Vercel
DNS infrastructure
Import all domains managed through your Vercel account or team. Infraova monitors DNS configuration and executes approved changes through the operational loop.
Connect →Route 53
DNS infrastructure
Import all hosted zones from your AWS Route 53 account using IAM credentials. Infraova monitors and operates across every hosted zone.
Connect →Squarespace
DNS infrastructure
Import domains managed through Squarespace Domains using your API key. Infraova monitors DNS configuration and acts on approved remediations.
Connect →Why agencies connect DNS providers
The connection is what closes the operational loop.
Most tools stop at detection. The DNS connection is what lets Infraova move from detecting a problem to fixing it — with your approval at the decision point that matters.
No manual DNS editing
Approved fixes are executed directly through the connected provider. Your team approves — Infraova handles the technical execution.
Immediate verification
After execution, Infraova re-checks the live DNS state immediately — not at the next scheduled scan cycle.
Exact record values
Infraova generates the precise DNS record required — not a generic recommendation. The proposal includes the exact value to set.
Complete audit trail
Every execution is recorded with the provider, the record changed, the timestamp, and the approving actor.
Faster resolution
The time between detecting a problem and verifying a fix drops from days to minutes when execution and verification are automated.
Consistent across clients
The same approval → execute → verify workflow runs for every client, every DNS provider, every time.
Connect your first DNS provider.
Start monitoring immediately. Connect a provider when you're ready to close the operational loop — from detection to verified remediation.