Inconsistent DNS Resolution for Domain Using Cloudflare

Website, Application, Performance DNS & Network
1

What is the name of the domain?

journals.ieditore.com

What is the issue you’re encountering

dns resolution

What feature, service or problem is this related to?

DNS records

What are the steps to reproduce the issue?

Go to https://www.nslookup.io/domains/journals.ieditore.com/dns-records/#cloudflare

2

Looks like there is no IP address returned for your sub-domain on @1.1.1.1.

EDIT: However, something is odd since I’ve got it few times while testing.

Furthermore, your domain is not using Cloudflare nameservers anymore:

Name Server: cpanel14.vhosting-it.com
Name Server: sdns1.vhosting-it.com
Name Server: sdns2.vhosting-it.com
Name Server: sdns3.vhosting-it.com
1 Like
3

Hi everyone,

I apologize for the confusion earlier. I made a mistake in my initial post, and I want to clarify the situation more thoroughly now.

I’m having a recurring issue with the DNS resolution of my domain journals.ieditore.com while using Cloudflare as the DNS provider. My domain is hosted with VHosting, and I’ve verified with them that everything is correctly configured on their side.

The problem is that the DNS resolution is inconsistent: sometimes Cloudflare returns the correct A record pointing to the IP address of the VHosting server (37.156.244.24), and other times no A record is returned at all. This leads to periods where the domain becomes unreachable.

I’ve double-checked the DNS settings in Cloudflare, and everything seems to be set up correctly. I’ve also ensured there are no conflicting records that could be causing this behavior. VHosting has confirmed that server-side settings are all correct.

Is there anyone here who has faced a similar issue or could help me understand why this is happening? Could this be related to caching or propagation, or is there something specific to Cloudflare’s handling that I should look into?

Any guidance or suggestions would be highly appreciated!

Thanks in advance for your help.

4

cpanel14.vhosting-it.com from the authorative nameservers (see WHOIS) does not resolve your hostname whereas the other 3 do, hence the intermittent resolution failures. cpanel15.vhosting-it.com, as given in your NS records, does appear to do so.

Check you have set the correct nameservers at your domain registrar.

dig journals.ieditore.com @cpanel14.vhosting-it.com

; <<>> DiG 9.10.6 <<>> journals.ieditore.com @cpanel14.vhosting-it.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 45367
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;journals.ieditore.com.		IN	A

;; AUTHORITY SECTION:
ieditore.com.		300	IN	SOA	cpanel14.vhosting-it.com. system.vhosting-it.com. 2024102705 3600 1800 604800 86400


dig journals.ieditore.com @cpanel15.vhosting-it.com

; <<>> DiG 9.10.6 <<>> journals.ieditore.com @cpanel15.vhosting-it.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56247
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;journals.ieditore.com.		IN	A

;; ANSWER SECTION:
journals.ieditore.com.	300	IN	A	37.156.244.24
3 Likes
5

Hi sjr,

Thank you so much for your explanation. Thanks to your detailed response, I was able to resolve the issue by adding the missing IP addresses on cpanel14.

Now both IPv4 and IPv6 are properly configured, and everything seems to be working correctly without any more intermittent failures.

I really appreciate your help!

Best regards

6

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