Still dns record not changed from registar

A have change my name server at porkbun with ns cloudflare but still shows the prokbun IPs.
Is that something else that must do in order to completely use cloudflare dns and proxy ?

Any idea someone ?

What’s the domain name?

1 Like

dcomet [dot] net

even at nslookup shows as cloudflare
at my network shows the below

dig ns dcomet[dot]net +short
salvador[dot]ns[dot]porkbun[dot]com
fortaleza[dot]ns[dot]porkbun[dot]com
maceio[dot]ns[dot]porkbun[dot]com
curitiba[dot]ns[dot]porkbun[dot]com

Are you gonna help or just asking domain info ?

i have purchase a domain from porkbun at 22/05 and change name server with cloudflare ones but still dns record points to porkbun.

Is there anything else i have to do in order to use my domain as i want ? Is anything wrong with my settings ?

dig ns dcomet [dot] net [Cloudflare DNS] +short
fortaleza [dot] ns [dot] porkbun [dot] com
curitiba [dot] ns [dot] porkbun [dot] com
salvador [dot] ns [dot] porkbun [dot] com
maceio [dot] ns [dot] porkbun [dot] com

Your site is pointing to Cloudflare’s IP address, reported by Cloudflare nameservers.
See Network Tools: DNS,IP,Email .
What is it that’s not working?

2 Likes

Did you see the screenshot i pasted ?

Yes, I did.

dig ns dcomet.net +short
harlan.ns.cloudflare.com.
aitana.ns.cloudflare.com.

dig ns dcomet.net @1.1.1.1 +short
aitana.ns.cloudflare.com.
harlan.ns.cloudflare.com.

dig ns dcomet.net @8.8.8.8 +short
aitana.ns.cloudflare.com.
harlan.ns.cloudflare.com.

Again, everything seems to be working now. Are you still encountering any problems?

2 Likes

Yes

>dig ns dcomet.net @8.8.8.8 +short
curitiba.ns.porkbun.com.
fortaleza.ns.porkbun.com.
salvador.ns.porkbun.com.
maceio.ns.porkbun.com.

>
>dig ns dcomet.net @1.1.1.1 +short
salvador.ns.porkbun.com.
maceio.ns.porkbun.com.
fortaleza.ns.porkbun.com.
curitiba.ns.porkbun.com.

>dig ns dcomet.net @202.67.220.220 +short
fortaleza.ns.porkbun.com.
curitiba.ns.porkbun.com.
salvador.ns.porkbun.com.
maceio.ns.porkbun.com.
dig ns dcomet.net @8.8.8.8 +short
aitana.ns.cloudflare.com.
harlan.ns.cloudflare.com.
dig ns dcomet.net @1.1.1.1 +short
aitana.ns.cloudflare.com.
harlan.ns.cloudflare.com.
dig ns dcomet.net @202.67.220.220
.... request timed out.... 

Works just fine for me as well. What answer do you get to

dig ns dcomet.net @162.159.38.222

1 Like
>dig ns dcomet.net @162.159.38.222 +short
curitiba.ns.porkbun.com.
fortaleza.ns.porkbun.com.
maceio.ns.porkbun.com.
salvador.ns.porkbun.com.

Can you also try dig dcomet.net +trace please?

1 Like
>dig dcomet.net +trace

; <<>> DiG 9.16.41 <<>> dcomet.net +trace
;; global options: +cmd
.                       448750  IN      NS      c.root-servers.net.
.                       448750  IN      NS      k.root-servers.net.
.                       448750  IN      NS      l.root-servers.net.
.                       448750  IN      NS      a.root-servers.net.
.                       448750  IN      NS      d.root-servers.net.
.                       448750  IN      NS      g.root-servers.net.
.                       448750  IN      NS      h.root-servers.net.
.                       448750  IN      NS      f.root-servers.net.
.                       448750  IN      NS      m.root-servers.net.
.                       448750  IN      NS      e.root-servers.net.
.                       448750  IN      NS      j.root-servers.net.
.                       448750  IN      NS      b.root-servers.net.
.                       448750  IN      NS      i.root-servers.net.
.                       490845  IN      RRSIG   NS 8 0 518400 20230605170000 20230523160000 60955 . gpH4r5hp4yyPyDnzzLbBAD38Y2IGbYhyuAnY/+byRgCqRCNKWaCX2G9E Qm23/dq5PC+4enkxvbfszLj2WwQQVDjfDcqsev/CJmevHIzrkNn3s2hJ xmeD0VHj4JMeO2le/ovgKcY/6TKLPNe052/iQUFmsIOes1kUJ3zy/7EP pkX1mrtd/jXvcaylJ9qlEJVVEaeDvsDknjFs1B9dBndRY5xyPIz3e0kr nFMswn3Zil2pk5YZR3/itkD5j2M1GHvpZK6+SoD7EiFOqSDjcI/SxYGB 8ska4hRJtKqinrAEW6yCRDRXQ/+MiAVpLRpHW7SxtGaCA4H8bFjSi3q5 mUsbqw==
;; Received 553 bytes from 1.1.1.1#53(1.1.1.1) in 14 ms

;; expected opt record in response
;; Received 28 bytes from 193.0.14.129#53(k.root-servers.net) in 2 ms

lol… well 162.159.38.222 is an Ip for aitana.ns.cloudflare.com which knows nothing about your previous DNS settings and answers authoritatively for your zone. Your DNS queries are being intercepted somewhere on your machine or network.

2 Likes

My network is clear, i have reset everything

Then DNS resolution is working correctly for you now? Awesome, glad you got it sorted.

1 Like

Porkbun uses Cloudflare, and their nameservers are just branded Cloudflare nameservers. In fact, until recently, their nameservers were not even branded: they handed out the usual Cloudflare-banded nameservers to their customers.

So that might explain this.

2 Likes

There’s nothing to explain.

dig ns dcomet.net @162.159.38.222 +short
aitana.ns.cloudflare.com.
harlan.ns.cloudflare.com.

The authoritative nameservers return the correct answer. 1.1.1.1 returns the correct answer. 8.8.8.8 returns the correct answer. The OP gets the wrong answer and believes it is because DNS isn’t updating properly on the Internet. It is. The problem is/was on their local machine or network. The test I had them perform proved it 100%.

2 Likes

This makes it very likely that your provider is intercepting DNS traffic, as your query to k.root-servers.net failed. You are probably being served with cached entries and would receive the same response if you tried querying with dig ns dcomet.net @1.2.3.4 +short or any other ip.

2 Likes