Nameservers not updating for .ci domain

I’ve configured the NS records in our registrar and i can see them propagated around the web. However the SOA record keeps changing back to the original registrar.

On AWS route53 we’ve had the same problem, and were told .ci TLDs were not supported there.

The list for cloudflare doesn’t seem to include country code TLDs. Is the TLD supported in cloudflare, or are we doing something wrong?

Below the output of dig


; <<>> DiG 9.10.6 <<>> our-domain.ci @8.8.8.8 +trace NS
;; global options: +cmd
.			71187	IN	NS	a.root-servers.net.
.			71187	IN	NS	b.root-servers.net.
.			71187	IN	NS	c.root-servers.net.
.			71187	IN	NS	d.root-servers.net.
.			71187	IN	NS	e.root-servers.net.
.			71187	IN	NS	f.root-servers.net.
.			71187	IN	NS	g.root-servers.net.
.			71187	IN	NS	h.root-servers.net.
.			71187	IN	NS	i.root-servers.net.
.			71187	IN	NS	j.root-servers.net.
.			71187	IN	NS	k.root-servers.net.
.			71187	IN	NS	l.root-servers.net.
.			71187	IN	NS	m.root-servers.net.
.			71187	IN	RRSIG	NS 8 0 518400 20210714050000 20210701040000 26838 . CgUQzW6vMjPeevJLQ4gE34fy1EjjebM1es/pazPTJ3gUzioLj08kBLxt Lf5ky5NE1WE7B5yIPRIxQCL391mftHhGNfTl/VFrqALD3a1Wn6rpR81I g6ssLIlaXE+fKtbCbiNVfFlcY/4CgnA5CIHwO/LvP7yQkpeLk++OfbD3 852f1woJTDoYUZ3U2uyBVqrapygZX5Y8/KgYDcnUPQZSKHz6aMdQQ5id fAjkzmRyUMFyCzqx9qxrbWcu1xK9Kk6qrLNvhRSoIpScGzKKmXBQx4eM 80Gwkv/6OBt6Vi0XBpt/+1EQOhTIqT7OoNpc/gR4A1JZLLsCMk9HfFQv bZ7K5g==
;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 104 ms

ci.			172800	IN	NS	ci.hosting.nic.fr.
ci.			172800	IN	NS	ns.nic.ci.
ci.			172800	IN	NS	any.nic.ci.
ci.			172800	IN	NS	ns-ci.afrinic.net.
ci.			172800	IN	NS	phloem.uoregon.edu.
ci.			172800	IN	NS	censvrns0001.ird.fr.
ci.			86400	IN	NSEC	cipriani. NS RRSIG NSEC
ci.			86400	IN	RRSIG	NSEC 8 1 86400 20210714050000 20210701040000 26838 . e78XCWQTtwHrMNvy8j8frT8rccuR52idJ6Jota3SF2kW+KhVIeZUTTO8 OAR5VZEXmpjiSDaVwvNhQT061o6gPpaoNWXN8A+g2MllFsijODZMVTwR 7ZtZRERe5bMfW/rfJNhofWtHmyXBNb29+WgX8c7OaqqndrofiC4k9ajJ 7lGUPqhdLDnEYq7lLcJhV3GzCgu2whIC9w7hGT4qyMzGvIodNlmj3fcc 0quItdSdjMmJol0CJ31ayyAHAF6WYcMYyQHwbN2TmIgTAt/af51klMU6 NbJzFizE+ci0G2wFC6Sq60ZQhfPF7GDa1txOJ7g2+qfxYSdWC01U45ds SoURhg==
;; Received 731 bytes from 193.0.14.129#53(k.root-servers.net) in 58 ms

our-domain.ci.		7200	IN	NS	ns1.netim.net.
our-domain.ci.		7200	IN	NS	ns2.netim.net.
our-domain.ci.		7200	IN	NS	ns3.netim.net.
;; Received 101 bytes from 196.216.168.30#53(ns-ci.afrinic.net) in 219 ms

our-domain.ci.		86400	IN	NS	igor.ns.cloudflare.com.
our-domain.ci.		86400	IN	NS	tina.ns.cloudflare.com.
;; Received 93 bytes from 192.174.68.97#53(ns2.netim.net) in 62 ms

In this instance, that list is not applicable. The list of TLDs are those that Cloudflare Registrar support and you are not using our Registrar service.

What is the name of the domain that is causing issues? Does it show as active on cloudflare?

Hey , thanks! The domain is nosana.ci

It hasn’t activated for 4 days, the day since I added the zone in cloudflare and changed the NS records in my registrar. Hence my question here… Do you maybe have an idea what can be the case?

1 Like

I see na record are pointing to cloudflare now

15877 opcode QUERY rcode NOERROR flags QR RD RA QUESTION nosana.ci. IN NS ANSWER nosana.ci. 21585 IN NS tina.ns.cloudflare.com. nosana.ci. 21585 IN NS igor.ns.cloudflare.com. AUTHORITY ADDITIONAL

Do you mean is not active in CF dashboard ? Did you click to check again ? Does na records match what is in dashboard ?

Hey! Yeah can see some happening as well, however the CF dashboard is never activated indeed (for 4 days). The records match.

Yes seems like some of DNS`s still report old NS server, not sure if this is due to registar but I would assume when CF checks it shows those old that why it is not activated
I think you can only wait or check with your resistar

on one registar I have domain OVH it took around 3 days, on other Go Daddy took 5 minutes .

Regards,
Miroslaw Pabian

According to nic.ci, the authoritative body for .ci, you haven’t changed that domain’s WHOIS information to the new name servers.

1 Like

Hey sdayman,

This is interesting did not know cloudflare is also checking whois DB for NS entries good to know for future

whois nosana.ci
Domain Name: nosana.ci
Registry Domain ID: 127948-cinic
Registry WHOIS Server:: whois.nic.ci
Updated Date: 2021-06-14T20:00:12.0Z
Creation Date: 2021-06-12T18:19:28.684Z
Registry Expiry Date: 2022-06-12T18:19:28.799Z
Registrar Registration Expiration Date: 2022-06-12T18:19:28.799Z
Registrar: Netim
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID: 1qrUg-xrrDh
Registrant Name: Redacted | EU Registrar
Registrant Organization: Unraveled B.V.
Registrant Street: Heesterveld 241
Registrant City: AMSTERDAM
Registrant Postal Code: 1102SC
Registrant Country: NL
Registrant Phone: Redacted | EU Registrar
Registrant Email: Redacted | EU Registrar
Registry Billing ID: Njhr8-ZUP6m
Billing Name: Redacted | EU Registrar
Billing Organization: Unraveled B.V.
Billing Street: Redacted | EU Registrar
Billing City: Redacted | EU Registrar
Billing Postal Code: Redacted | EU Registrar
Billing Country: NL
Billing Phone: Redacted | EU Registrar
Billing Email: Redacted | EU Registrar
Name Server: ns1.netim.net
Name Server: ns2.netim.net
Name Server: ns3.netim.net
DNSSEC: unsigned
>>> Last update of WHOIS database: 2021-07-01T20:00:08.892Z <<<

It has to. NS records won’t work, as they have to come from the authoritative name servers for that domain, as determined by WHOIS.

Thanks for the answers! Indeed there was an additional thing on the registrar side we had to configure.

Zones are working now :slight_smile: :rocket:

Cheers!

1 Like

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