Skip to main content
The common uses are a scheduled agent that tells your team which domains renew or expire soon, a customer’s ticket about one of their domains, and a SafeDNS change asked for in a chat, such as a verification TXT record. On a ticket, the agent reaches only the customer’s own ANS client and domains, so SafeDNS, eCloud and the rest of the account are worked from a chat or a scheduled agent.
Automatically enabled when you configure ANS permissions in your agent workflow.

What It Does

  • Read each domain’s client, renewal and expiry dates, auto-renew, privacy, nameservers and registrant, and turn auto-renew or privacy on or off
  • Check renewal prices, renew domains and register new ones
  • Change a domain’s nameservers or registrant
  • Read and manage the account’s clients, the customers its domains are registered for
  • Read, add, change and remove SafeDNS zones, records and templates
  • Read and manage eCloud instances, volumes and images, and power them on, off or restart them
  • Read and manage eCloud VPCs, networks, routers, firewall and network rules, public IPs, VPNs and SSH key pairs
  • Read and manage DDoSX domains, WAF and ACL rules, CDN and HSTS
  • Read and manage load balancers, managed Cloudflare accounts and zones, and DRaaS solutions
  • Read SSL certificates and their expiry, monitoring and threat monitoring, invoices and costs
  • Open, update, approve and close support cases with ANS

Permission Groups

Neo always asks a technician before the writes listed under “Always asks” on Connecting ANS to Neo, whatever the group’s approval setting. It never reads or sends a password, a VPN pre-shared key or a private key, never opens an instance’s console, and hides those values in every answer. On a ticket, the agent works only on the ANS client mapped to the ticket’s company and that client’s domains.

Setup

See Connecting ANS to Neo.