The leased IP address has a custom PTR record set, ensuring mail and finance systems recognize the identity and preventing integration failures.
The agent interacts with the AnchoredIP API or dashboard to set a PTR (Reverse DNS) record for a specific leased IP address. This is critical for services that verify the sender's identity via reverse DNS lookups, such as email servers or financial APIs. The agent ensures the record is live and correctly associated with the IP.
- Category: Operations and infrastructure
- Effect: Changes data in your accounts
- MCP servers: AnchoredIP MCP (https://koskamo.com/explore/anchoredip-mcp)
- Source: Use cases — allowlists, CI runners, serverless egress, inbound | AnchoredIP (https://anchoredip.com/docs/use-cases)
- Source quote: "Reverse DNS you control Set a PTR record for your address from the dashboard, or over the API."
- Playbook page: https://koskamo.com/explore/use-cases/set-reverse-dns-ptr-record-for-leased-ip
Prompt: Set the reverse DNS (PTR) record for IP 194.0.108.99 to 'mail.example.com' using the AnchoredIP API.