Open supernovia opened 1 week ago
While I am not sure whether all of these specifically tried clicking "Point to WordPress.com" we do have many issues that mention "restore default A records" and seem to show people struggling with pointing their sites here.
here's one, though: 9009128-zd-a8c
Support References
This comment is automatically generated. Please do not edit it.
I think we avoided changing people's A records automatically when they transfer a domain in (especially when domains were moving from the Google Domains situation; changing registrars in that case may not necessarily indicate a desire to change hosts) so I am guessing this could be mostly happening with transfers.
This has been reported before in p2MSmN-cgl-p2 as well.
Quick summary
When a user transferrs or connects an existing domain to us, sometimes they'll wait several days for it to start working. We have a button that says "Point to WordPress.com" but if they are already using our name servers, that action doesn't do anything to fix the broken A record.
Steps to reproduce
I am not sure how best to replicate this since it requires starting with an existing domain that's not registered here and presumably isn't happening in all cases, but we see it fairly regularly. My guess is:
What you expected to happen
If someone clicks "Point to WordPress.com" with a domain registered here, we should:
What actually happened
Currently the button just takes us into the domain management page. Judging from the status bar, it may point to our name servers as well, but if that's already done, it doesn't seem to do anything else. Any incorrect A records will stay in place, and there is no user guidance for updating them so the domain can start working.
Impact
Some (< 50%)
Available workarounds?
Yes, easy to implement
If the above answer is "Yes...", outline the workaround.
The workaround is easy but not easy for users to know they should do this:
Platform (Simple and/or Atomic)
No response
Logs or notes
No response