DNS records are not being resolved by some Internet providers

We have a DNS zone called coinjinja.com set up with Cloudflare DNS

We have been informed by a user that coinjinja.com records are not being resolved by some Internet providers’ DNS servers, and reverse lookups are not possible.

I have been informed by a user that

We have actually checked from several different lines and found that some lines are not able to pull DNS servers to coinjinja.com

From https://digwebinterface.com/

[email protected] (Default):

dig A +noadditional +noquestion +nocomments +nocmd +nostats coinjinja.com. @8.8.4.4

[email protected] (AdGuard (CY)):

dig A +noadditional +noquestion +nocomments +nocmd +nostats coinjinja.com. @94.140.14.14

[email protected] (AT&T (US)):

dig A +noadditional +noquestion +nocomments +nocmd +nostats coinjinja.com. @165.87.13.129

coinjinja.com. 300 IN A 172.67.178.74

coinjinja.com. 300 IN A 104.21.17.204

[email protected] (Cloudflare):

dig A +noadditional +noquestion +nocomments +nocmd +nostats coinjinja.com. @1.1.1.1

[email protected] (Comodo (US)):

dig A +noadditional +noquestion +nocomments +nocmd +nostats coinjinja.com. @8.26.56.26

[email protected] (Google):

dig A +noadditional +noquestion +nocomments +nocmd +nostats coinjinja.com. @8.8.8.8

[email protected] (HiNet (TW)):

dig A +noadditional +noquestion +nocomments +nocmd +nostats coinjinja.com. @168.95.1.1

coinjinja.com. 300 IN A 172.67.178.74

coinjinja.com. 300 IN A 104.21.17.204

[email protected] (OpenDNS):

dig A +noadditional +noquestion +nocomments +nocmd +nostats coinjinja.com. @208.67.222.222

[email protected] (Quad9):

dig A +noadditional +noquestion +nocomments +nocmd +nostats coinjinja.com. @9.9.9.9

[email protected] (Securolytics (CA)):

dig A +noadditional +noquestion +nocomments +nocmd +nostats coinjinja.com. @144.217.51.168

coinjinja.com. 300 IN A 172.67.178.74

coinjinja.com. 300 IN A 104.21.17.204

[email protected] (UUNET (CH)):

dig A +noadditional +noquestion +nocomments +nocmd +nostats coinjinja.com. @195.129.12.122

[email protected] (UUNET (DE)):

dig A +noadditional +noquestion +nocomments +nocmd +nostats coinjinja.com. @192.76.144.66

[email protected] (UUNET (UK)):

dig A +noadditional +noquestion +nocomments +nocmd +nostats coinjinja.com. @158.43.240.3

[email protected] (UUNET (US)):

dig A +noadditional +noquestion +nocomments +nocmd +nostats coinjinja.com. @198.6.100.25

coinjinja.com. 300 IN A 172.67.178.74

coinjinja.com. 300 IN A 104.21.17.204

[email protected] (Verisign (US)):

dig A +noadditional +noquestion +nocomments +nocmd +nostats coinjinja.com. @64.6.64.6

[email protected] (Yandex (RU)):

dig A +noadditional +noquestion +nocomments +nocmd +nostats coinjinja.com. @77.88.8.8

coinjinja.com. 178 IN A 104.21.17.204

coinjinja.com. 256 IN A 172.67.178.74

The current apex domain record for coinjija.com is set up using Cloudflare’s DNS proxy.

I also tried setting PTR records, but I set the IP of the Load Balancer and the IP of the origin server under its LB.

(It is highly possible that there are unnecessary A records and PTR records. I don’t understand the DNS settings in Cloudflare or the configuration of reverse proxy in LB.)

The DNSSEC configuration on your domain registrar, GMO Internet Group, Inc., is incorrect:

1 Like

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