DNS Record for ANAME

Hello,

I am new to Cloudflare my web site was hosted on Hostinger as follows with ANAME record on Digicert’s DNS Management as follows:

Type:ANAME
Name field of DNS Record: blank
FQDN or IP: alhussnain.org.cdn.hstgr.net.
TTL: 3600

I am trying to create the same record the system doesn’t gives any option for ANAME record, after reviewing the documentation they say that I need to create a CNAME record for the same, but again the system is giving me an error message that a similar record exist.

Presently my website is down.

The Digicert DNS has the following:

The Cloudflare DNS has the following:

Type: A
Name: alhussnain.org
FQDN or IP: 191.101.104.13

Type: A
Name: ftp
FQDN or IP: 217.196.55.16

Type:A
Name: www
FQDN or IP: 154.62.106.77

Works for me. Can you explain what error you are experiencing?

I moved the Name Servers back to DigiCert’s (DNSMadeEasy), when they were pointing Cloudflare the site was down, as I cannot afford downtime hence moved the NS back.

In that case, you should make sure that the records on Cloudflare are exactly the same as they are on your previous DNS provider.

Instead of an ANAME, you would use a CNAME as you said. The error you receive is also fairly clear: Delete the automatically imported A record if you want to create a CNAME. However, both seem to work from what I can see.

What error message did you see when you tried to open your site via Cloudflare?

1 Like

These were the records setup earlier.

Drop the first A record, the one where the name is the domain name.

Add this one as a type CNAME instead.

Type: CNAME
Name: @, or alhussnain.org
Target: alhussnain.org.cdn.hstgr.net
Proxy status: :orange: Proxied:.

Record types such as ALIAS and ANAME, as well as Cloudflare’s CNAME Flattening, will all be attempting to give you the same result.

You should note that the change of name servers can take 48 - 96 hours to propagate out to the whole Internet.

Switching back and forth multiple times within a short time can cause trouble that will be hard to troubleshoot, or even cause you the downtime you claim you cannot afford.

I followed your instructions and removed the A record, created a CNAME as advised, still the issue persists.

Now the DNS records shows as follows:

The site is not loading, anyone to help me on this?

You have “too many redirects”…
https://cf.sjr.org.uk/tools/check?78b83ffbe6e84cfbb08321f846e95c07#connection-server

For completeness, check your SSL/TLS is set to “Full (strict)” here…
https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls

…but it appears the circular redirect is coming from your origin (it is redirecting alhussnain.org to alhussnain.org). I suggest you pause Cloudflare, get your site working correctly at your server, then unpause Cloudflare.

Your ftp record should be set to “DNS only” if you use FTP.

[add] It also appears www.alhussnain.org redirects to itself on your origin as well…
https://cf.sjr.org.uk/tools/check?245a4f784c9a4396ab093149034f1c11#connection-server

2 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.