I have observed that the URL “https://mrewardz.mutualtrustbank.com/Login.aspx” is not resolving when using Cloudflare Public DNS (1.1.1.1). However, when I switch to Google DNS (8.8.8.8), the website resolves without any problem.
This discrepancy in resolution behavior between Cloudflare Public DNS and Google DNS is concerning, especially considering Cloudflare’s reputation for providing reliable and efficient DNS resolution services.
As a user who relies on Cloudflare Public DNS for my DNS resolution needs, encountering such inconsistencies raises questions about the reliability and performance of the service.
mutualtrustbank.com. 172800 IN NS dns1.link3.net.
mutualtrustbank.com. 172800 IN NS dns3.link3.net.
mutualtrustbank.com. 172800 IN NS ns-cloud-e1.googledomains.com.
mutualtrustbank.com. 172800 IN NS ns-cloud-e2.googledomains.com.
mutualtrustbank.com. 172800 IN NS ns-cloud-e3.googledomains.com.
mutualtrustbank.com. 172800 IN NS ns-cloud-e4.googledomains.com.
The Google nameservers respond with an SOA record, indicating that they are authoritative but that the name does not exist.
QUESTION SECTION:
;mrewardz.mutualtrustbank.com. IN A
;; AUTHORITY SECTION:
mutualtrustbank.com. 300 IN SOA ns-cloud-e1.googledomains.com. cloud-dns-hostmaster.google.com. 1 21600 3600 259200 300