Troubleshooting & Questions

DNS template did not apply after domain order

DNS templates and managed zones are created automatically only when you order a real domain product with an internal nameserver set. If you use a generic product option, an external nameserver set, or custom external nameservers, Hostware skips zone creation and does not install the template.

Template did not apply

No DNS records were created after the order because one of the required conditions for automatic template installation was missing.

Domain was ordered via a product option

When a customer enters a domain through a generic product option, Hostware uses that value for module mapping only. It does not create a domain entry, so DNS template installation never triggers.

Fix: Order the domain as a standalone domain product instead of using a product option. If the goal is only to require specific DNS records on an external domain, use the DNS Templates for validation flow.

Domain uses an external nameserver set

If the matched nameserver set is marked external, or if custom external nameservers are configured, Hostware skips managed zone creation because the DNS is not managed by Hostware or the registrar.

Fix: Create the zone and records manually at your external DNS provider. If you want Hostware to manage DNS automatically, select an internal nameserver set before ordering.

Zone is missing after a transfer

Domain transfers follow the same external-nameserver rule.

Transfer used external nameservers

During a transfer, Hostware checks the nameserver configuration. If the domain uses an external nameserver set, the transfer proceeds with the configured nameservers and skips zone creation.

Fix: Switch to an internal nameserver set before initiating the transfer, or create the zone manually at your external provider after the transfer completes.

Domain shows REGISTER_ERROR after ordering

The DNS host or registrar module failed to create the zone during installation.

Zone creation failed at the DNS host

Hostware calls the provider to create the zone when a managed DNS host is configured. If the provider rejects the request—for example, because the zone already exists, the API credentials are invalid, or the nameserver configuration is wrong—the installation job catches the exception and sets the domain status to REGISTER_ERROR. The error details contain the provider message.

Fix: Review the error details stored on the domain, correct the issue at the DNS host or provider, and place the order again with the corrected configuration.

Was this helpful?