Network DNS propagation issues

DNS & Network 1.1.1.1
#1

About hour ago I’ve added new domain to Cloudflare services & updated DNSes for the domain.

All popular DNS servers got new NS records within seconds, while my default 1.1.1.1 server (waw02) still responds with old records.

dig +short CHAOS TXT id.server @1.1.1.1 -> "waw02"

dig NS blockchainassociationinfo.com @1.1.1.1

; <<>> DiG 9.9.7-P3 <<>> NS blockchainassociationinfo.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20008
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1536
;; QUESTION SECTION:
;blockchainassociationinfo.com.	IN	NS

;; ANSWER SECTION:
blockchainassociationinfo.com. 3600 IN	NS	ns49.domaincontrol.com.
blockchainassociationinfo.com. 3600 IN	NS	ns50.domaincontrol.com.

;; Query time: 66 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Thu Apr 12 11:57:19 CEST 2018
;; MSG SIZE  rcvd: 110

VALID SERVERS:
google:

dig +short NS blockchainassociationinfo.com @8.8.8.8
oswald.ns.Cloudflare.com.
tani.ns.Cloudflare.com

1.1.1.1 dub01
dig +short CHAOS TXT id.server @1.1.1.1 > “dub01”

dig +short NS blockchainassociationinfo.com @1.1.1.1
tani.ns.Cloudflare.com.
oswald.ns.Cloudflare.com
#2

Appears to have updated for me, are you still experiencing incorrect resolution?

#3

I also find that Cloudflare DNS is really slowly compared to Google in DNS propagation. In facts, I pointed a domain to Cloudflare and changed the IP of the A record, Google see the change already but Cloudflare DNS not. Isn’t supposed that Cloudflare DNS should see first Cloudflare changes?

I’m thinking to swich back to Google DNS just because that.

#4

:wave: @laszlo.jr.demeter,

That’s not exactly how DNS works. Resolvers cache responses based on the TTL specified by the authoritative nameservers for the record in question.

-OG

#5

Hi Oliver,

I know, but even with TTL set to 2 minutes it took like 4 hours to propagate. And then, the cache refresh page didn’t works.

#6