Free domain from Freenom

I have seen thatin cloud free domains not going to supported from Dec 28 to Jan 2. Is that may be a issue ??

try to set your CF nameservers in management tools > nameservers

2 Likes

You shouldn’t change the nameservers until the domain has been added to the :logo: dashboard.

Also, in this case I am not sure it really is a nameserver issue. It rather seems Cloudflare cant run the whois or gets for some other reason the impression the domain is not registered.

Thats a case for support -> https://support.cloudflare.com/requests/new

1 Like

Why not? I always do it when registering a new domain, since all the sites in the same account share the same NS (almost always)

The issue is that the domain doesn’t have any NS set: DNS Checker - DNS Propagation Check & DNS Lookup

@cs-cf speculated about that recently → Failed to lookup registrar and hosting information of h-com.school at this time. (Code: 1110) - #3 by cs-cf but I am still not convinced. Anyhow though, worth a try.

From what I see the domain is resolved directly by the ga root TLD:

$ nslookup -type=soa milliondreams.ga

Non-authoritative answer:
*** Can't find milliondreams.ga: No answer

Authoritative answers can be found from:
ga
        origin = a.ns.ga
        mail addr = cctldga-tech.nic.ga
        serial = 1546256611
        refresh = 10800
        retry = 3600
        expire = 604800
        minimum = 5

When using external NS, it should be instead:

$ nslookup -type=soa fete.ga

Non-authoritative answer:
fete.ga
        origin = chin.ns.Cloudflare.com
        mail addr = dns.Cloudflare.com
        serial = 2029137617
        refresh = 10000
        retry = 2400
        expire = 604800
        minimum = 3600

Authoritative answers can be found from:

I think that’s because he’s using it in the “forward url” mode, so they don’t set a NS for the second-level domain, and Cloudflare thinks it’s not registered (even if the A record is resolving)

1 Like

@francesco

From this support article:

https://support.cloudflare.com/hc/en-us/articles/360000977291-My-domain-has-been-hijacked-how-did-this-happen-

Pointing to Cloudflare name servers without signing up the domain first

We never recommend you point to Cloudflare name servers at your registrar or delegate to our name servers without having your domain signed up in your account first. Anyone can sign up domains to Cloudflare and when you point to Cloudflare name servers without claiming the site first, you are effectively opening up DNS control to whomever signs up the domain first on our platform.

The fix here is to sign up the site in your Cloudflare account first and then point to only your Cloudflare assigned name servers after .

Yes ok, in theory it’s right, but if the domain has just been registered nobody has interest to hijack it since it has no traffic… and I would notice immediately when I add the domain in my :logo: account. (the wizard would tell me to change the NS, for example, from ian and lana to john and alan, in the unlikely event someone has already added it to ian and lana)

I just like to try and follow the official guidelines when helping here!! :smile:

It’s entirely up to you what you do with them!

Guys sry for the interruption what should I do finally.

If it still doesn’t work, you will probably need to login to Cloudflare and then contact Cloudflare Support. Unless anyone else has any suggestions, sorry!


1 Like

You are more expert than me but if the domain has no nameservers I doubt the Cloudflare support can do anything… On the Cloudflare side it’s working as intended IMHO

image

That could be the issue as @sandro mentioned @cs-cf’s post earlier …

Some sites return a.ns.ga b.ns.ga c.ns.ga and d.ns.ga as the nameservers… But some show the results you posted.

EDIT:

WHOIS shows:
NS01.FREENOM.COM
NS02.FREENOM.COM
NS03.FREENOM.COM
NS04.FREENOM.COM

Cloudflare can clarify what the issue is and fix whatever possibly needs fixing.

1 Like

a.ns.ga are the nameservers for ga., not for milliondreams.ga.

this is how DNS hierarchy works, in simple words, when query a DNS record for www.subdomain.example.com., the lookup application tries in the order the dns server (nameservers) of:

  • 4th level: www.subdomain.example.com.
  • 3rd level: subdomain.example.com.
  • 2nd level: example.com.
  • 1st level: com.
  • root zone: .

most of the domains have the nameservers at the second level, in this case it hasn’t…and the 1st level nameserver has a zone for the second level domain, this is an anomaly of this TLD, normally you can’t query for example nslookup -type=A google.com a.gtld-servers.net


TL;DR set custom nameservers as here Free domain from Freenom and it will work (if you don’t want to violate the guidelines, you can put random ones like ns1.google.com and change them later)

I realised I had got the wrong ones, I am aware of what you posted.

I meant to paste these nameservers that are shown as being used on that domain by whois.net

NS01.FREENOM.COM
NS02.FREENOM.COM
NS03.FREENOM.COM
NS04.FREENOM.COM

I see, that is the whois record, but it’s only plain text, I could write whatever I want in it, and it’s actually wrong… dns queries don’t read the whois record

They dont but they are supposed to come from the registry, which also holds the authoritative nameservers. If there is a mismatch it is likely a registry issue.

Anyhow, we went slightly off-topic. The domain is registered so Cloudflare should be able to verify that and add it. It is not fully clear whether Cloudflare needs active NS records, if it does adding them should do the trick. Otherwise contact support as mentioned several times so far.

1 Like