Domain does not resolve - 1.1.1.1/1.0.0.1


#1

Hi , i have some troubles when try to use cloudflare as resolver with a domain from Argentina

Domain : ar.santanderrio.com.ar

Here some nslookup …

$ nslookup

server 1.1.1.1
Default server: 1.1.1.1
Address: 1.1.1.1#53
ar.santanderrio.com.ar
Server: 1.1.1.1
Address: 1.1.1.1#53

** server can’t find ar.santanderrio.com.ar: SERVFAIL

server 1.0.0.1
Default server: 1.0.0.1
Address: 1.0.0.1#53
ar.santanderrio.com.ar
Server: 1.0.0.1
Address: 1.0.0.1#53

** server can’t find ar.santanderrio.com.ar: SERVFAIL


If i try google dns / or isp dns works well every time

server 8.8.8.8
Default server: 8.8.8.8
Address: 8.8.8.8#53
ar.santanderrio.com.ar
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: ar.santanderrio.com.ar
Address: 200.61.38.185


Could be a problem on the domain dns servers? between cloudflare and that domain? country level domain servers? any idea, i have users using this domain in daily basis and many days it give error with cloudflare, i should add google dns for this domain and no fails since that.

Any ideas? sorry my english if some term is wrong

Thanks


#2

Most likely. For example, the registry returns the following two nameservers as authoritative

fry.santanderrio.com.ar
zoidberg.santanderrio.com.ar

Whereas these nameservers actually return

fry.bancorio.com.ar
zoidberg.bancorio.com.ar

Check out https://intodns.com/santanderrio.com.ar and http://dnsviz.net/d/santanderrio.com.ar/dnssec/


#3

yes i saw those error on domain configuration that are not good but still operational , when i use other dns to resolve its resolve ok , even with cloudflare it resolve without problem most of the time , in fact right now …

server 1.1.1.1
Default server: 1.1.1.1
Address: 1.1.1.1#53
ar.santanderrio.com.ar
Server: 1.1.1.1
Address: 1.1.1.1#53

Non-authoritative answer:
Name: ar.santanderrio.com.ar
Address: 200.61.38.185

And nothing change on the specific domain , could be some problems to route from cloudflare to root name servers on country here? or ip route problem? some kind of dns block query on our ISP provider?

Thanks for the answer


closed #4

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