Domain Name Issues

[Rat Boy]

Hello,

So I, like everyone else, is trying to fix our forum.

I have done the guide as posted above, however, when I get to the part about putting in my forum URL, it is asking me for another $70 when I just extended this for 5 years less than a month ago.

Do we really have to pay again because of the Cloudflare stuff?

Also, for my CNAME, should it point to cpnd.us or httr.cpnd.us?   It currently looks like the attached file.



Thanks in advance.

[Brian]

Hi, Rat Boy.

If you've already purchased your custom domain you don't need to go through the purchase process on ProBoards to complete the setup. The domain is already associated with your forum and our service should accept requests from it right away.

Your CNAME is pointed at the correct domain but the host name for your CNAME should be httr rather than the root of your domain since you're making a subdomain point towards the forum and not the root of the domain.

[Rat Boy]

Thanks Brian.

So in the screen shot just change cpnd.us to httr

Got it.

[Brian]

That's correct.

Please let us know if you need any further assistance with this and we'll be happy to help.

[Rat Boy]

Aug 2, 2018 14:21:23 GMT -8 Brian said:

That's correct.

Please let us know if you need any further assistance with this and we'll be happy to help.

Hey Brian,

So I just noticed that while my forums are now fixed, all my custom graphics and some custom pages I had outside of ProBoards no longer work.

Examples:

cpnd.us/images/Addiction_Banner.jpg


cpnd.us/pcinoz/Salaries_and_Contracts.pdf

Is this because of what we changed on CloudFlare and is there a fix for it?

[Scott]

Rat Boy, Brian is off this week, so perhaps I can help. Just so I'm clear, are these links that reside on your site, or links used elsewhere pointing back to your forum?

[Rat Boy]

These are files that we host on the main site on GoDaddy.

Sometimes we reference them, or use them for header images, etc.

In the case of the PDF, its simple links on the boards to PDFs that hold salary cap info for the team.

Either way, my entire website is no longer working since the change to the managed nameservers.

CPND.US appears to have died. I can no longer hit it via FTP either to upload files.

[Rat Boy]

Also, CloudFlare is showing me what the issue is, but I have no idea how to get the correct info to make the records:

An A, AAAA, CNAME, or MX record is pointed to your origin server exposing your origin IP address.
An A, AAAA or CNAME record was not found pointing to the root domain. The cpnd.us domain will not resolve.
An MX record was not found for your root domain. An MX record is required for mail to reach @cpnd.us addresses.

[Scott]

Rat Boy,
From what I can tell you aren't pointing your root domain at anything, only the subdomain of httr is pointing to us (your forum).

You would need to set up your root domain (and possibly a www subdomain) to point to your own server, both of which will be set in your Cloudflare panel. You'll have to know what to point it at and what kind of record to use.

[Rat Boy]

Ok.

I am not sure where I get that info from is the problem.

I am kind of new at this as I didn't do the original set up.

Can GoDaddy (Site Host) answer this?

[Michael]

Aug 9, 2018 11:24:55 GMT -8 Rat Boy said:

Ok.

I am not sure where I get that info from is the problem.

I am kind of new at this as I didn't do the original set up.

Can GoDaddy (Site Host) answer this?

If you login to the old DNS panel on GoDaddy you should be able to find what the root was pointing at originally (it should still be saved there). Then you just need to re-enter that into the CF panel and you should be good to go. 

[Rat Boy]

Thanks Michael.

I created an A record for @ and pointed it at the same IP that was listed before.

Also did the same for FTP, which was pointed at @ before.

It's fixed.

Thank you both for your time.

[Michael]

Aug 9, 2018 11:38:40 GMT -8 Rat Boy said:

Thanks Michael.

I created an A record for @ and pointed it at the same IP that was listed before.


Also did the same for FTP, which was pointed at @ before.

Guess now the propagation wait happens. LOL.

Thanks again.

That should have it fixed, but of course please let us know how it goes! 

[Rat Boy]

Well, mostly fixed now.

Just can't get my FTP client to connect. But worst case, I can use GoDaddy's site to upload files.