A missing DNS answer does not prove that /etc/named.conf is corrupt. First identify the authoritative nameserver, the DNS software in use and the error reported by that server. Rebuilding a configuration on the wrong machine can disrupt working zones without fixing the domain.
Establish the failure before changing configuration
This procedure is for an authorized cPanel/WHM server administrator. A shared-hosting customer should give support the domain, expected answer, actual answer and time of failure. Check registrar delegation, zone existence, DNS-service status and relevant logs. A DNS report alone cannot distinguish a missing zone from a configuration error, unreachable server or delegation problem.
On a server using BIND, its configuration checker can help identify syntax errors. Use the configuration path and software documentation for the actual installation. Do not apply BIND file operations blindly to a server using another DNS service or to a secondary node managed by a DNS cluster.
Preserve a recovery path
Before an approved rebuild, preserve the current configuration and zone data in a dated, access-controlled backup. Record custom settings and DNS-cluster relationships. Confirm how to restore the previous state and arrange a maintenance window; the rebuild can restart the DNS service. A second administrator or console connection should be available if remote access depends on the affected DNS.
cPanel's rebuild procedure moves the existing configuration aside, then runs:
/usr/local/cpanel/scripts/rebuilddnsconfigUse that procedure only after confirming that a rebuild is appropriate for the installed system. Do not repeatedly move or overwrite files until the command appears to succeed. If the rebuild reports an error, preserve the output and investigate before further changes.
Validate service and zone answers
Check service status and logs, then query representative records directly against the authoritative server. Include the affected hostname, mail records and another previously working zone. Check external resolution after delegation and caching effects are accounted for. A running process is not proof that every zone loaded correctly.
Document the cause and result. If the configuration rebuilt successfully but the original failure remains, return to delegation, zone content and connectivity diagnosis instead of treating another rebuild as the next step.
