DNS Propagation between Pat and Cody


#1

I am currently new to CloudFlare and am attempting to set this up for my first time. Seems like an awesome solution, but I cannot get CloudFlare to be happy with my DNS settings. When I utilize NSLookup to verify my NS settings for the domain I find that the Cody NS is updated but Pat is not. Any ideas what the propagation time on CloudFlare’s NSs should be?

com's%20Account%20_%20Cloudflare%20-%20Web%20Performanc


#2

NS change can take from 24-48 hours. A lookup for me returns your old hostinger name servers, but a global lookup shows the Cloudflare ones. Give it more time.


#3

Yes sir. I am at about 24 hours. Sorry for my impatience. It just seemed odd to me that Cody and Pat wouldn’t be more in sync. Thanks for the quick response.


#4

You need to change your nameservers in the registrar portion of your registrar. At the moment they appear to have been changed in the DNS zone you have at hostinger.

dig contactjoshua.com ns

; <<>> DiG 9.11.1 <<>> contactjoshua.com ns
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17851
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
contactjoshua.com. 1799 IN NS cody.ns.cloudflare.com.
contactjoshua.com. 1799 IN NS pat.ns.cloudflare.com.

;; Query time: 58 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Jul 27 19:17:11 CDT 2018
;; MSG SIZE rcvd: 97

[mass_els] dig contactjoshua.com ns +trace master ✭ ✱

; <<>> DiG 9.11.1 <<>> contactjoshua.com ns +trace
;; global options: +cmd
. 109686 IN NS a.root-servers.net.
. 109686 IN NS b.root-servers.net.
. 109686 IN NS c.root-servers.net.
. 109686 IN NS d.root-servers.net.
. 109686 IN NS e.root-servers.net.
. 109686 IN NS f.root-servers.net.
. 109686 IN NS g.root-servers.net.
. 109686 IN NS h.root-servers.net.
. 109686 IN NS i.root-servers.net.
. 109686 IN NS j.root-servers.net.
. 109686 IN NS k.root-servers.net.
. 109686 IN NS l.root-servers.net.
. 109686 IN NS m.root-servers.net.
. 109686 IN RRSIG NS 8 0 518400 20180808050000 20180726040000 41656 . KaVkLPiHhmUCHrQmSBk3Z+3xLJlM+9ZPPqxGievgDO/NFvcGzUmqt/Cy hnDOkFV7E1z//8655POBKjPf4vElbVhRSOSooniQ1+10gIV5YAtOa+wc SjwoweU7K726SFcTQ+wBXXz+hlWYyuOGXf7k43AuuHKz2jmuywI2ZmDX X/tpaAH55ViwZUlUmQnabgTfVFejf6qiLS6Z/0l0O9Xa42nlFRLDcn+D RrsTpiN6Kh9RzvHZZxEgRiWJxk3pdTIThJnQTfePMFTkgkBhjV0y7LLy yoTXowUuBo1/fON6S5Ui7FVXa3PxBU0vvX1LGBNr/zZ/5CLu7FZtCAWL pdyQTQ==
;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 8 ms

com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS m.gtld-servers.net.
com. 86400 IN DS 30909 8 2 E2D3C916F6DEEAC73294E8268FB5885044A833FC5459588F4A9184CF C41A5766
com. 86400 IN RRSIG DS 8 1 86400 20180809170000 20180727160000 41656 . n+hJ2SNZE9Ei+vF0PyOt4YrHkXtBIVYotl0NO8ad6okoWLn38v5mxAPz /EJ7d3AEC1Mr1zi2QATzrZKiYI99CDjSL+P4I6n5ug2j3QVqz2ud4/vI oKkBXnlSPgG+yHLmrwfoCbPaDM/utJzTlMq82NLGX1uu3aiP4+4V4AEz 6Xfujqeljz70voDNmOjaAGIs6MpX2O1rg8YUbbjH7iTOB1bessK4G2ob Wli/zUzdvH3lgr+J35KaxoohAFFZ9SWgTQH4XtLkr49KiDN8bTkv5/M8 z6rU7fHylOYmgLhOEdtP4S1C6X1mXk41lrHx+4Rx/F3dIXE3kWqxMw40 +gf+zA==
;; Received 1177 bytes from 2001:500:a8::e#53(e.root-servers.net) in 9 ms

> contactjoshua.com. 172800 IN NS ns1.hostinger.com.
> contactjoshua.com. 172800 IN NS ns2.hostinger.com.
> contactjoshua.com. 172800 IN NS ns3.hostinger.com.
> contactjoshua.com. 172800 IN NS ns4.hostinger.com.

CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN NSEC3 1 1 0 - CK0Q1GIN43N1ARRC9OSM6QPQR81H5M9A NS SOA RRSIG DNSKEY NSEC3PARAM
CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN RRSIG NSEC3 8 2 86400 20180731044815 20180724033815 46475 com. fM3ga8tkCx9ZVu/L/hQGXNcPxPVEGLfCgCgTtsJyUNefVSPOCMdqneA7 0UMVn06TbkGLDe85cA8ZViEnqc3iG6zhZIAwqas1/5G509o4Ppf4lDI5 CsH3iEhL5ofH+xfLt+wWEaTCLsUtmJN/VrSdqwpgJTNIJCcMQNF5A4J5 btQ=
O25JU5FQBJG1GSDP65V5ROMEVFQCNPEE.com. 86400 IN NSEC3 1 1 0 - O25KAV16OKQ4V2PCOFA2T7RILD7N34KM NS DS RRSIG
O25JU5FQBJG1GSDP65V5ROMEVFQCNPEE.com. 86400 IN RRSIG NSEC3 8 2 86400 20180803045251 20180727034251 46475 com. HIAFmqM4T/y+6BKwWe/JRMDVGCGAyhF+RXvBcGVD4sJn+bLN2gS/7Jl7 WDAQa2Akfctamu7Hm24sE1EECG/McpMHmQbp1tnbzd6e59wrLThb7SVa hLfikXsluPgM8DCDKJBOb+FmgtLCc1fnZ6OX3iw3u4nYSkOBFq0Fs7j0 LWA=
;; Received 677 bytes from 192.31.80.30#53(d.gtld-servers.net) in 10 ms

contactjoshua.com. 1800 IN NS pat.ns.cloudflare.com.
contactjoshua.com. 1800 IN NS cody.ns.cloudflare.com.
;; Received 97 bytes from 173.192.183.247#53(ns3.hostinger.com) in 56 ms


#5

hostinger is what shows up when I do a WHOIS, but something sure seems out of whack:


#6

You were spot on. That is entirely my bad. Thanks so much for finding what I was missing!


#7

I made the edit before I posted. Sorry about that.