<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DNS resolve response timeout</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/68458/dns-resolve-response-timeout</link><description>Hello, 
 I developed a thread network using the latest SDK for Thread v4.1. I also have the latest OpenThread Border Router running. 
 I cannot ping Google IPv4 from my Thread node (but I can ping it from the Border Router). My ISP does not provide IPv6</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 27 Nov 2020 13:29:21 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/68458/dns-resolve-response-timeout" /><item><title>RE: DNS resolve response timeout</title><link>https://devzone.nordicsemi.com/thread/282265?ContentTypeID=1</link><pubDate>Fri, 27 Nov 2020 13:29:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b403c772-0f7f-4a8f-a167-0f0752a4d732</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;I have reported this internally. Our developers will have a look at it and see if we can determine the root cause of the issue.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DNS resolve response timeout</title><link>https://devzone.nordicsemi.com/thread/280842?ContentTypeID=1</link><pubDate>Thu, 19 Nov 2020 10:54:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cf7f24af-d22a-4ea0-a48e-0fa9d9e8c24d</guid><dc:creator>kalpino</dc:creator><description>&lt;p&gt;UPDATE: It seems that, during the boot of the raspberry pi, the wpantund service is started too soon, probably before the NCP is detected.&lt;/p&gt;
&lt;p&gt;Restarting the wpantund at runtime with sudo systemctl restart wpantund solves the problem as well.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;Please verify this and fix the problem in the next release if it&amp;#39;s the case. I lost a lot of time with this..&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DNS resolve response timeout</title><link>https://devzone.nordicsemi.com/thread/280787?ContentTypeID=1</link><pubDate>Thu, 19 Nov 2020 08:58:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e85d2576-d1c8-4b0e-b3fa-bc7c0cb1a643</guid><dc:creator>kalpino</dc:creator><description>&lt;p&gt;Thanks Jorgen, this procedure worked!&lt;/p&gt;
&lt;p&gt;Anyway I&amp;#39;m wondering if this has to be done for every Border Router I will set-up in the future.. Is there a way to get rid of this problem permanently?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DNS resolve response timeout</title><link>https://devzone.nordicsemi.com/thread/280596?ContentTypeID=1</link><pubDate>Wed, 18 Nov 2020 12:14:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:837fb13f-21a8-4e8a-8cba-9c9c38973e0a</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;It looks like your node has not been assigned the IPv6 address from the NAT64 interface. This address should have a fd11:22::/64 prefix by default.&lt;/p&gt;
&lt;p&gt;I have seen this issue some times and have managed to solve it as described in &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/61283/how-to-ping-host-pc-from-thread-ftd/249798#249798"&gt;step 3 in this post&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Jørgen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>