Profile Domain Module - Procedure not Recommended?
Using Jamroom
Thanks for your input SE. I'm starting to think I wasn't supposed to do anything with the @ host afterall, so I'm not sure why I was given these instructions. Apparently, I just had to change nameservers to point to my host, not update the @ record in the DNS.
brian:
You need to update DNS so your A record points to your Jamroom server - just as if you were going to host it there. Otherwise Jamroom has no way to respond to the domain request.
brian:
Ken_Rich:
Should I set @ host to point to the server IP (root) or the JR5 dedicated IP?
It must point to your JR5 site - otherwise Jamroom will not see it.
When I change the nameservers to my host, the @ host setting is apparently no longer controlled from the registrar. I apparently had temporary access while the DNS was resolving. In fact, I see this message there now "The zone file is unavailable because the domain's set nameservers do not belong to this registrar."
Because of my interpretation (or misinterpretation) of Brian's instructions, I set the DNS Zone File @ host to my JR5 IP and perhaps that caused the loop?
So to be crystal clear, at the level of the registrar:
1) Is it necessary to manually edit the DNS zone file @ host setting to point to the JR5 IP?
2) Or, does one simply change the nameservers as per normal (and not mess with the @ host setting).
updated by @ken-rich: 01/29/15 07:02:44AM