How to Prepare a Useful Domain or DNS Support Request

A useful support request gives NicNames the exact domain, the outcome you want, what changed and what you see now. A few specific details can make the problem easier to understand while passwords, transfer codes and other sensitive information stay out of the message.

1. Start with the domain and the goal

Use a subject that names the task, such as “DNS help for example.com” or “Transfer status question for example.com.” In the message, include the complete domain name and describe the result you want: connect a website, restore email, verify a service, understand a transfer status or correct a DNS record.

Say which address or service is affected. For a website, distinguish example.com from www.example.com or another subdomain. For email, say whether sending, receiving or both are affected. If you are asking about a transfer, include the domain extension and the step where the process stopped. Never send your password, account-recovery codes, payment-card details or domain AuthInfo/EPP transfer code in an ordinary support message.

2. Record the current state and timing

Copy the exact error text and note when the problem began, including your time zone. Mention whether it affects every device or network you tried, or only one. If you recently changed a DNS record, nameserver, website connection or mail setting, identify the change and its approximate time without guessing.

Check the domain's current nameservers before describing a DNS issue. Records must be managed at the DNS provider named by those servers. Our domain lookup guide explains how to read the delegation and common status information. If NicNames shows Custom Name-Servers, say which provider hosts the active DNS zone; an inactive NicNames zone may not control the public answer.

3. Add evidence that support can compare

For a DNS record question, list the relevant host label, record type, expected destination or value and TTL. Use only the records connected to the problem; a complete zone export may reveal unrelated service details. If a value contains a private verification token, share only what support specifically requests through the appropriate channel.

Attach a cropped screenshot when it clarifies an error or setting, but remove account identifiers, customer data and unrelated browser tabs. Include the page address and visible error message in text as well, so the issue is searchable even if the image is hard to read. For a recent DNS change, the NicNames DNS troubleshooting guide can help you separate an incorrect authoritative record from an older cached answer.

4. Send the request and keep the history together

Open the NicNames Support page and use Apply to support. Keep replies about the same problem in one email thread, and add any new error, result or configuration change with its time. If the scope changes, state that clearly instead of leaving support to infer it from an earlier message.

For a transfer question, review the domain-transfer preparation guide first and include the current registrar, transfer status and the date the transfer was requested. For a website or email issue, say what still works as well as what fails. A compact timeline and a precise expected result give support a clearer starting point than a message that only says the domain is not working.