So, I have a friend trying to do something funky between his primary domain and subdomains. He ultimately needs blog.hisdomain.com to point to a silly cPanel host and his primary domain to point to a static IP (for AWS).
I'm not an expert with http or dns, but I was trying to help him through it while he was up (it's night time in his country at present), but it doesn't really look like it's working out.
I had him perform the following steps:
- His primary domain was set up in cPanel with nameservers set, so I had him create a subdomain in cPanel for blog.hisdomain.com which just went to the public root.
- Then I had him add an A Record for "blog" with the IP of the cPanel host as the value. This made it so that we could see his blog at blog.hisdomain.com.
- Next I had him change the "@" A Record to point elsewhere. I just grabbed a google IP address for the value here. This didn't really change anything at first, but we figured it might have been a propagation issue.
It's now been over 24 hours and his primary domain still (more slowly now) takes me to the blog. Just now I remembered that I didn't have him change his nameservers or anything; just the A Record. Is it possible that having an A Record and Name Servers is causing some confusion and is leading the dns to ignore the A Record IP address.