A domain in Odin Business Automation Standard (OBAS) suddenly stops resolving.
How can I troubleshoot this issue?
Verify the name servers used by the domain:
~# whois DOMAIN.TLD | grep NS
Name Server: NS1.SERVER.TLD
Name Server: NS2.SERVER.TLD
NS2.SERVER.TLDare active name servers registered in OBAS:
Top > Service Director > Domain Manager > Name Servers
If the domain uses external name servers, reconfigure the domain's DNS zone at the authoritative name servers or change them to
NS2.SERVER.TLDin the registrar.
If the NS records are missing, you should reconfigure the DNS zone. Add the OBAS managed name servers:
DOMAIN.TLD. 600 NS NS1.SERVER.TLD.
DOMAIN.TLD. 600 NS NS2.SERVER.TLD.
A client can reconfigure a domain's DNS zone through the Control Panel. The records will appear in the DNS zone after synchronization.
Verify synchronization status using DNS Records Suppliers:
Top > Service Director > Domain Manager > Domains > DOMAIN.TLD > DNS Records Suppliers
Verify the domain has DNS hosting.
If the DNS zone is disabled, verify which orders are running. These orders are shown in the PBA-S Action Log (search by domain name) and in the domain's subscription:
Top > Configuration Director > Logging and Errors > Action Log
Top > Service Director > Domain Manager > Domains > DOMAIN.TLD > Subscription #NUMBER > Orders
For Plesk Domain or Plesk Client subscriptions, verify the backup task is not running in Plesk. If the option Suspend domain until backup task is completed is enabled, the domain and its DNS zone are disabled during the backup process:
Plesk > Subscriptions > DOMAIN.TLD > Open in Control Panel > Websites & Domains > Backup Manager > Scheduled Backup Settings
If the DNS zone exists and it is active in OBAS, but the domain is still not resolved, verify that the domain is resolved at the OBAS-managed name servers:
~# dig DOMAIN.TLD @NS1.SERVER.TLD
~# dig DOMAIN.TLD @NS2.SERVER.TLD
If an error appears when requesting the name servers (for example, a request timeout error), investigate the system log on the name servers and fix the problem.
If you see that the domain's DNS zone is empty at the name servers, verify synchronization with OBAS-managed name servers according to the instructions from this KB: