Before you begin
Export or record the current DNS zone before editing. Identify the authoritative DNS provider using the domain’s name servers, not only its registrar.
Work only on devices, domains and accounts you own or are authorized to manage. Make a recoverable backup before changes that may affect data or access. If the system is already unstable, prioritize preserving information over experimenting.
Step-by-step approach
Map A and AAAA records to hosting, MX records to mail delivery, CNAME records to aliases and TXT records to verification or authentication purposes.
Confirm the exact values supplied by the service provider. Enter host names in the format the DNS interface expects to avoid adding the domain twice.
- Change only the relevant records and account for TTL caching. Check from an independent DNS lookup rather than relying solely on the control-panel display.
- Repeat the original task after the change and record what improved, what stayed the same and any new error. Keep the previous configuration available until validation is complete.
Validation and common mistakes
Keep a change log with the previous values and reasons. Roll back a specific incorrect change instead of replacing the entire zone from memory.
Change one variable at a time so that the result can be attributed to a particular action. Do not treat a temporary absence of symptoms as proof of a permanent repair. Redact personal information from logs and screenshots before requesting help.
Conclusion
A documented, reversible process is more dependable than repeated unrecorded changes. Keep your observations with the version and configuration details so that further assistance can build on what you have already checked. For a CracksHelp service request, confirm the scope through the existing support email before payment.