Article ID: 117262, created on Sep 16, 2013, last review on Dec 30, 2015

  • Applies to:
  • Operations Automation 5.4
  • Odin Business Automation Standard 4.5

Symptoms

A domain in Odin Business Automation Standard (OBAS) suddenly stops resolving.

How can I troubleshoot this issue?

Resolution

  1. Verify the name servers used by the domain:

    ~# whois DOMAIN.TLD | grep NS
    Name Server: NS1.SERVER.TLD
    Name Server: NS2.SERVER.TLD
    ~#

    NS1.SERVER.TLD and NS2.SERVER.TLD are 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 NS1.SERVER.TLD and NS2.SERVER.TLD in the registrar.

  2. 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.

  3. Verify synchronization status using DNS Records Suppliers:

    Top > Service Director > Domain Manager > Domains > DOMAIN.TLD > DNS Records Suppliers

  4. Verify the domain has DNS hosting.

  5. 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

  6. 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

  7. 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.

  8. 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:

    DNS zones are not synced to OBAS-managed nameservers

Search Words

DNS zone

Domain is not resolved

nameserver not authoritative

name server

dns zone

zones were disabled

NS records

plesk website not displayed in browser

PBA-S managed name servers

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065 70a5401e8b9354cd1d64d0346f2c4a3e 624ca542e40215e6f1d39170d8e7ec75 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07 ac82ce33439a9c1feec4ff4f2f638899 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF