New A record is served with incorrect IP, yet reverse lookup returns correct name

New A records added 1.5 hours ago, not published.

Lookups on the names return the parent domain default records - i.e. for an existing web server.

Reverse lookup with dig -x on the target IP returns the correct name of the first A record.

Lookups against local servers and the authoritative (Cloudflare) servers both give the same results, so this is not just a local caching issue.

I need to wait another 24/48 hours?

method:
dig demo.livinggracedianella.org.au +short
104.21.16.110
172.67.210.204
dig demo.livinggracedianella.org.au @alec.ns.cloudflare.com +short
172.67.210.204
104.21.16.110
dig -x 139.59.238.138 +short # correct target IP, visible in Cloudflare console DNS listing
demo-livinggracedianella.
demo-livinggracedianella.local.

??

That is the correct IP address. If you don’t want to take advantage of Cloudflare related services such as DDoS protection and caching, you can point directly to your origin server by disabling proxy and using DNS only :grey:

3 Likes

I may not have described the problem clearly enough.

I created a record in the CF DNS Records form, entering these details:

Name: demo (or demo.livinggracedianella.org.au, which reverts to ‘demo’ on entry)
Type: A
IP: 139.59.238.138

CF is publishing these details:

dig demo.livinggracedianella.org.au +short
104.21.16.110
172.67.210.204

Can you see the confusion / error?

Yes. Go ahead and change the :orange: record to :grey: and see what happens.

When a record is being proxied the IP address returned to a external user is the address of the proxy service.

2 Likes

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