Obtain the API username and password for an account authorised to manage the relevant Liquid Web DNS zones. Confirm the service's current API access and account restrictions with its administrator. Use the provider's DNS inventory to identify which zones will be managed and who owns them before you enable automatic adoption.

The default adapter endpoint is https://api.liquidweb.com/v1. A web control-panel address is not a replacement for that API base. If your provider account uses a different documented deployment, verify the contract before changing the setting.

1. Open Domain Nexus Servers, add a connection and choose StormOnDemand / Liquid Web.
2. Fill in API Username and API Password.
3. Review API Base URL, save and run the check.
4. Inspect an authorised zone using discovery or a test package. The connection check performs a zone-list read, so separately test record access.
5. Add a temporary TXT record, wait for the task's result and compare the provider record and authoritative answer. Remove only the test record after verification.

First establish that the record read completed successfully. A failed or partial inventory should not be treated as an instruction to replace an existing production zone. The adapter follows the provider's record pages; preserve any reported paging or response error for support.

No. Compare the domain's registrar nameservers with the DNS service that holds the zone. DNS hosted in the provider portal, DNS running in a server control panel and the domain's registration may be three separate services. Choose the connection that manages the actual intended source and prepare delegation only after its records are complete.

• Discover existing DNS zones and link only verified customer ownership
• Choose hosting nameservers or DNS management for your domain
• Run a controlled DNS provider acceptance check before assigning customer packages
• Connect DNS Made Easy with its paired API credentials

• Liquid Web: Command line interface and API access