Unable to resolve host using 1.1.1.1 on `asa003b.centers.ihost.com`

Zero Trust 1.1.1.1
1

This might be related to the old report:
https://community.cloudflare.com/t/unable-to-resolve-host-using-1-1-1-1-only-on-certain-syd-datacenter/215203/1

I’m having an issue where I can’t resolve a certain host asa003b.centers.ihost.com when using Cloudflare DNS (1.1.1.1) but it can be resolved with Googles DNS (8.8.8.8).
I don’t have any issues with other websites or hostnames using that 1.1.1.1.

Here are “nslookup” results:

nslookup asa003b.centers.ihost.com
Server:  one.one.one.one
Address:  1.1.1.1

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to one.one.one.one timed-out

nslookup asa003b.centers.ihost.com 8.8.8.8
Server:  dns.google
Address:  8.8.8.8

Non-authoritative answer:
Name:    asa003b.centers.ihost.com
Address:  131.239.211.196

Could you please take a look.

Best regards
Michael

4

To which Cloudflare data center are you connected? It might be regional as it resolves fine for me.
Check it here: https://1.1.1.1/help

5

To which Cloudflare data center are you connected?

https://1.1.1.1/help#eyJpc0NmIjoiTm8iLCJpc0RvdCI6Ik5vIiwiaXNEb2giOiJObyIsInJlc29sdmVySXAtMS4xLjEuMSI6IlllcyIsInJlc29sdmVySXAtMS4wLjAuMSI6IlllcyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjExMTEiOiJObyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjEwMDEiOiJObyIsImRhdGFjZW50ZXJMb2NhdGlvbiI6IlRYTCIsImlzV2FycCI6Ik5vIiwiaXNwTmFtZSI6IkRldXRzY2hlcyBGb3JzY2h1bmdzbmV0eiIsImlzcEFzbiI6IjY4MCJ9

But I also have that from my home which I currently cannot not create a similar link of.

6

Here another one:

https://1.1.1.1/help#eyJpc0NmIjoiTm8iLCJpc0RvdCI6Ik5vIiwiaXNEb2giOiJObyIsInJlc29sdmVySXAtMS4xLjEuMSI6IlllcyIsInJlc29sdmVySXAtMS4wLjAuMSI6IlllcyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjExMTEiOiJObyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjEwMDEiOiJObyIsImRhdGFjZW50ZXJMb2NhdGlvbiI6IlRYTCIsImlzV2FycCI6Ik5vIiwiaXNwTmFtZSI6IlZvZGFmb25lIEdlcm1hbnkiLCJpc3BBc24iOiIzMjA5In0=

7

After almost one month the problem still exists, is there any update?

8

Hi @micwinx,

I’m sorry to hear that you have such an issue, and for the late reply. It is because that our servers in TXL region are not able to reach the nameserver spns.centers.ihost.com. I just sent an email to their admin, hopefully we could figure out the root cause. In the meantime, I also applied a workaround, so the domain should resolve now.

2 Likes
9

Thank you for the update and forwarding this to the admins. Sadly the work around does not seem to work for me and the domain still does not resolve.

10

Looks like the affect is wider than I thought. Can you check again? If it still does not work, could you please query the /help page again and let me know the current Cloudflare data center you are connected to(as the routing could have changed), thanks.

2 Likes
11

Information for Cloudflare anb:

I tested from the Cloudflare FRA Location right now and get the same Error. So the FRA Location has this Problem as well

I also seem unable to contact their Nameservers directly when coming from a German IP. Its not the ASN i tried from multiple. When i change to Country to say the Netherlands i get an answer from their Nameservers. Its just the German IPs that dont result in an Answer from them

Netherlands:

Server:  spserve.centers.ihost.com
Address:  192.148.8.2

Name:    asa003b.centers.ihost.com
Address:  131.239.211.196

Germany:

DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  192.148.8.2

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
1 Like
12

Thanks for the investigation, @oneandonlyjason. I extended the list, hopefully people won’t get issues anymore.

2 Likes
13

The problem still persists, here again the /help query:

https://1.1.1.1/help#eyJpc0NmIjoiTm8iLCJpc0RvdCI6Ik5vIiwiaXNEb2giOiJObyIsInJlc29sdmVySXAtMS4xLjEuMSI6IlllcyIsInJlc29sdmVySXAtMS4wLjAuMSI6IlllcyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjExMTEiOiJZZXMiLCJyZXNvbHZlcklwLTI2MDY6NDcwMDo0NzAwOjoxMDAxIjoiWWVzIiwiZGF0YWNlbnRlckxvY2F0aW9uIjoiVFhMIiwiaXNXYXJwIjoiTm8iLCJpc3BOYW1lIjoiVm9kYWZvbmUgR2VybWFueSIsImlzcEFzbiI6IjMyMDkifQ==
14

Is it still the subdomains under centers.ihost.com? I cannot reproduce it.

2 Likes
15

Yes, it’s still the same addresses.

1 Like
16

Now the nslookup command (without the Google DNS) resolves

nslookup asa003b.centers.ihost.com
Server:  one.one.one.one
Address:  1.1.1.1

Non-authoritative answer:
Name:    asa003b.centers.ihost.com
Address:  131.239.211.196

but still reaching the address in any browser (I tested) does not resolve. E.g., for Chrome you get:

Die Server-IP-Adresse von **asa003b.centers.ihost.com** wurde nicht gefunden.

Versuche Folgendes:

* Verbindung prüfen
* [Proxy, Firewall und DNS-Konfiguration prüfen](chrome-error://chromewebdata/#buttons)
* [Windows-Netzwerkdiagnose ausführen](javascript:diagnoseErrors())

ERR_NAME_NOT_RESOLVED

(Sorry for the German here, but the error should be clear.)

1 Like
17

I also checked again against the FRA Location. And for the FRA Location i still get a Request Timed out Error.

Server: one.one.one.one
Address: 1.1.1.1

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.