inherit
256075
0
Sept 16, 2018 7:15:01 GMT -8
mysterycharge
4
August 2018
mysterycharge
|
Post by mysterycharge on Aug 15, 2018 11:31:21 GMT -8
Forum URL: mysterycharge.com/The only domain that is currently working right now is mysterycharge.freeforums.net/ However, we have already made our payment for our Custom Domain. Our Main Problem:
Upon purchasing our Custom Domain through ProBoards, we choose the option "I want to manage my DNS." From there we went on to choose "Option 2: A Record." This step was completed on our end and we added (104.16.4.137-104.16.8.137). Our Current DNS is currently set up through:
- GoDaddy AND - DMSmadeeasy.com We have continued to get the "Error 1001 Ray ID: 44adfac271b3ba0c • 2018-08-15 19:13:37 UTC DNS resolution error" Next Steps?
- We are wondering what we can do here since we have purchased the Upgrade of Custom Domain, set up the IPs both through GoDaddy and DNSmadeeasy.com - and we are still getting the error. - We are wondering you may be caching some kind of domain settings or something. Becuase we have set up the DNS records on two different DNS providers. Using both methods provided.
|
|
#e61919
Support Staff
224482
0
Member is Online
1
Dec 2, 2024 12:19:32 GMT -8
Scott
“Asking for help isn't giving up... it's refusing to give up.”
24,547
August 2015
socalso
|
Post by Scott on Aug 15, 2018 11:36:54 GMT -8
|
|
inherit
256075
0
Sept 16, 2018 7:15:01 GMT -8
mysterycharge
4
August 2018
mysterycharge
|
Post by mysterycharge on Aug 15, 2018 14:39:02 GMT -8
A CNAME Cross-User Banned error is due to Cloudflare's prohibition on CNAME records pointing from one Cloudflare user into another Cloudflare user's account. ... Incoming CNAME records from other user accounts can be permitted for Pro, Business, and Enterprise customers by contacting support.Aug 8, 2018 Error 1014: CNAME Cross-User Banned – Cloudflare Support support.cloudflare.com/hc/.../213432887-Error-1014-CNAME-Cross-User-Banne... That is the error we are getting.
|
|
#eb7100
33409
0
1
Nov 24, 2024 4:27:37 GMT -8
Brian
48,130
November 2004
smashmaster3
|
Post by Brian on Aug 15, 2018 14:42:38 GMT -8
Can you provide a screenshot of what you're entering into your DNS records that leads to that message?
|
|
inherit
256075
0
Sept 16, 2018 7:15:01 GMT -8
mysterycharge
4
August 2018
mysterycharge
|
Post by mysterycharge on Aug 15, 2018 15:50:31 GMT -8
Thank you for your response. We have attached the file Image (26) to this reply of what we are seeing.
|
|
#eb7100
33409
0
1
Nov 24, 2024 4:27:37 GMT -8
Brian
48,130
November 2004
smashmaster3
|
Post by Brian on Aug 15, 2018 15:53:36 GMT -8
Your CNAME needs to be pointed towards the following exactly as typed in the threads Scott linked: It should not be pointed towards the forum URL.
|
|
inherit
256075
0
Sept 16, 2018 7:15:01 GMT -8
mysterycharge
4
August 2018
mysterycharge
|
Post by mysterycharge on Aug 16, 2018 8:49:04 GMT -8
Thank you ProBoards team for your help! We have made that change and the page with the custom domain is now up and running.
|
|