That is kind of a BS answer. I am talking directly to my DNS provider right now and he says that we need (or should have) at least one actual IP address for the A record which should be provided by my hosting provider (in this case Microsoft Power Pages). Now that might not be correct but it is what they are telling their customers. My guy is telling me that if Microsoft doesn't provide explicit instructions for the A record, then I might want to try adding an ALIAS record. Ah, the old MIcrosoft "trial and error" approach to documentation that is a holdover from the "bad old Microsoft" days.🤣 Then again, for those of us who have suffered through the realities of the Power Platform over the past 6 years, this is just par for the course. Eventually, someone will do a LinkedIn post explaining it all.
There are a number of well known DNS providers (like GoDaddy and DirectNIC) and it should be incumbent on Microsoft to provide correct DNS settings for a few of these services, if only so that we (users) have some examples of this to talk through when we talk to our DNS providers.
I am in the process of moving my websites from Wix to Power Pages. I would expect that this is a pretty common scenario or at least it will be if Power Pages is successful. I am also moving the DNS hosting back from Wix where it has been for a few years to DirectNIC (where my domain is purchased) and so I am not just getting the website working but some additional domain names that I own that need to point to the new Power Pages site too as well as my MX records.
It would be useful and I would expect "table stakes" for Microsoft to put just a little more time and energy into documentation for common scenarios to, for once in its life, not make its users use trial and error and a hundred phone calls to different support sites.
