Unable to resolve host / increase DNS timeout?

[jweismueller]

I get very often the following error inside my notifications.
If I use "Synchronize now" inside the app, it always worked.
Maybe some more robust handling of this exception could help ... or increasing the timeout...

Unable to resolve host "[ics.teamup.com](http://ics.teamup.com/)": No address associated with hostname

java.net.UnknownHostException: Unable to resolve host "[ics.teamup.com](http://ics.teamup.com/)": No address associated with hostname
at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:124)
at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:103)
at java.net.InetAddress.getAllByName(InetAddress.java:1152)
at okhttp3.Dns$Companion$DnsSystem.lookup(Dns.kt:49)
at okhttp3.internal.connection.RouteSelector.resetNextInetSocketAddress(RouteSelector.kt:169)
at okhttp3.internal.connection.RouteSelector.nextProxy(RouteSelector.kt:132)
at okhttp3.internal.connection.RouteSelector.next(RouteSelector.kt:74)
at okhttp3.internal.connection.RealRoutePlanner.planConnect(RealRoutePlanner.kt:147)
at okhttp3.internal.connection.RealRoutePlanner.plan(RealRoutePlanner.kt:67)
at okhttp3.internal.connection.FastFallbackExchangeFinder.launchTcpConnect(FastFallbackExchangeFinder.kt:118)
at okhttp3.internal.connection.FastFallbackExchangeFinder.find(FastFallbackExchangeFinder.kt:62)
at okhttp3.internal.connection.RealCall.initExchange$okhttp(RealCall.kt:267)
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:32)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:95)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:84)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:65)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:205)
at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:537)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
at java.lang.Thread.run(Thread.java:1012)

[sunkup]

Hello. Is this still an issue for you?

[jweismueller]

Yes, the issue still occurs nearly every day.

[sunkup]

Right. ICSx5 has a connect timeout of 10 seconds. How long does your DNS server take to respond? Maybe you could change to a faster one.

Besides increasing the timeout, how do you suggest to do "more robust handling of this exception" ?

[UserX404]

Running on v2.2 I also run into this every now and then.
Whereas I have no new info about that issue's root cause I want to report a subsequent issue.

I got notification from icsx5 about unable to resolve host blablabla. When i click on this notification a grayed out screen is shown with a info box in the top. Talking about unable to resolve host .... with "view details" on the botom left and "ok" on the bottom right.
It's not possible to click on OK or leave that screen. I need to swipe the screen from the recent apps or force-close be long click on back button.

[sunkup]

Thanks for telling us. 👍

Tracked in #296

[devvv4ever]

This is a message that we have had for ages on various devices. If I remember correctly it is the system that triggers a sync for ICSx5 when the network is basically up again after a downtime. but in fact it is a little bit too early and internet is not totally available yet when ICSx5 is performing the sync (although the system reported that it should be), leading into this error.