For purchase — most stuck domains complete within 30 minutes. If it's been longer, click Recheck DNS on the domain's detail panel. If still stuck after another 30 minutes, contact support. For connect (BYOD) — check that your DNS records at your registrar match exactly what Winnr shows. Common issue is an extra SPF record you didn't remove, or a TTL still too high for propagation.
Diagnosis order
1. Wait 15 minutes past your expected completion time. Most "stuck" domains aren't actually stuck — DNS propagation is variable.
2. Click Recheck DNS. Forces Winnr to re-query authoritative DNS servers. Bypasses stale caches.
3. Verify records at your DNS provider. Domain detail panel → Show expected records. Compare each Type/Name/Value against what's at your DNS host. Match exactly. Typos in DKIM values (they're long random strings) are the most common cause.
4. Check for conflicting records. Any pre-existing SPF, DKIM, or MX records at the apex will conflict with Winnr's. Remove them.
5. Confirm the TTL isn't too high. If your DNS provider has a 24-hour TTL cache, changes can take that long to propagate globally. Lower TTL to 3600 (1 hour) at your DNS provider.
6. Contact support. If none of the above resolves within 90 minutes, email support@winnr.app with the domain name. Include a screenshot of your DNS records at your registrar.
What Winnr checks (specifically)
- MX —
10 inbound.yourdomain.com(priority 10, host inside your own domain), exactly. - SPF (TXT at apex) — includes Winnr's send authorization, starts with
v=spf1and ends in-all. - DKIM (TXT at
dkim._domainkey) — matches the public key on file. - DMARC (TXT at
_dmarc) — well-formed,v=DMARC1.
All four must match for status to flip to Active.
What can also go wrong on purchase specifically
- Registrar rate limits. Rare, but if you bought many domains at once, the registrar may be temporarily throttling. Winnr retries automatically.
- Registrar-side domain hold. Some registrars hold new .com registrations for spam review. Automatically clears in 24-48 hours; not much to do but wait.
- Payment issue. If the purchase card failed, provisioning halts. Check for a red banner on the domain row.
What's next
Frequently asked questions
How long is "normal" for provisioning?
Purchase — 2-5 minutes typical, up to 30 minutes in edge cases. Connect — 5-30 minutes depending on your DNS provider; up to an hour for slow providers like GoDaddy.
What does "DNS pending" specifically mean?
Winnr is trying to verify SPF, DKIM, DMARC, and MX records match what it expects. If any record is missing or wrong at your DNS, verification loops.
What's the first thing to try?
Click Recheck DNS in the domain's detail panel. Forces an immediate re-verification. Often clears the stuck state if propagation just needed a nudge.
What if I have two SPF records?
SPF must be one record. Two SPF TXT records at the apex is an RFC violation and breaks authentication. Remove any pre-existing SPF from your DNS before Winnr's SPF can verify.
My records look correct but Winnr says pending. Now what?
DNS caches can lie — TTL settings can hold stale answers for up to an hour. Wait 30-60 minutes. If still pending, contact support with the domain name and the exact records at your DNS.