Scanning takes too long

dns

#1

I just registered, I started to scan my web and it took 55 minutes, after it finished, I started from 55 again …

Use this page:
https://www.cloudflare.com/a/setup

Please, it’s important.


#2

That doesn’t sound right. I suggest you open a Support Ticket at support.cloudflare.com or email support at cloudflare dot com from you account’s email address.


#3

Can you help me? What i do here?


#4

Add another CNAME for brain-ocio.tk that points to the same 000webhost address as the www cname.


#5

For example?
I don’t know so much


#6

From your picture:

  1. Where it says “A” for the menu choices, pick CNAME instead.
  2. Where it says “Name” enter brain-ocio.tk
  3. Where it says IPv4 address, have it say semiotic-minimum.000webhost.com (same as your other entry)
  4. Click “Add Record” (the green box)

Then click the green “Continue” box.


#7

what is the error of the orange circle


#8

Hey @brain_ocio,

That’s not actually an error but more an information saying that this record will be flattened at the root level since you can’t CNAME to the APEX on a given domain (https://support.cloudflare.com/hc/en-us/articles/200169056-CNAME-Flattening-RFC-compliant-support-for-CNAME-at-the-root). CloudFlare will flatten this record in order to operate DNS resolution as if it was a A record.
Then, did you know that you can upload all your DNS records via a BIND configuration file? For that, go to the “Advanced” menu and you’ll see a menu where you can upload a zone file.


#9

how to fix this? is the third time that happen

I put your dns in the tk domain


#10

@brain_ocio, this error indicate that your backend server responded with that status code, Cloudflare EDGE is just replaying the error to your visitor in a pretty fashion with the information of the connection.

If you suspect your application to deliver that status code too much, i suggest you look at your webserver logs to see where the issue is coming from.


#11

This has happened 2 times the last hour, i should contact the hosting service or domain?


#12

Since it’s more an application issue, I would say your hosting provider.


#13

Ok i’ll contact