Thread Network Border Router DNS Timeout

[askabu]

Hello there,

I'm able to successfully setup the Thread Border Router on RPI4 B+ by following this (https://openthread.io/guides/border-router) tutorial. I've built it from the source (not used Docker).

I've verified the RCP with ot-ctl command and it's working fine. I wanted to work with thethings_io_coap example. I do followed the instructions described in https://infocenter.nordicsemi.com/topic/sdk_tz_v3.1.0/thread_thethings_io_coap.html and the cloud setup is successful and I'm able to send the data to the particular thing with the thing-token from the command-line using the command.

curl -i -H "Accept: application/json" -H "Content-Type: application/json" -d '{"values":[{"key":"temp","value":"0"}]}' -X POST "https://api.thethings.io/v2/things/{THINGS_TOKEN} " -k

But, the problem is, I'm unable to send the counter or the temp values to the thing from the nRF52833-DK, when I ran in debug mode it says,

<info> app: DNS response error 28

I'm not sure what - if the address with the fdff:cafe:cafe:cafe:: prefix is visible means which is mentioned in the troubleshooting section of this https://infocenter.nordicsemi.com/topic/sdk_tz_v3.1.0/thread_thethings_io_coap.html link.

But when I checked the IP Address of the Node and the RCP of the border router, it gives,

For RCP (border router),

> ipaddr
fdc3:1564:5193:5b:0:ff:fe00:fc31
fdc3:1564:5193:5b:0:ff:fe00:fc11
fdc3:1564:5193:5b:0:ff:fe00:fc10
fdc3:1564:5193:5b:0:ff:fe00:fc38
fd11:22:0:0:388e:2ee9:c6f5:b601
fdc3:1564:5193:5b:0:ff:fe00:fc00
fdc3:1564:5193:5b:0:ff:fe00:4400
fdc3:1564:5193:5b:280a:5326:4a66:2fad
fe80:0:0:0:48be:899c:4161:9380
Done

For Node,

> ipaddr
fd11:22:0:0:e598:14e3:6918:bfe4
fdc3:1564:5193:5b:0:ff:fe00:ec00
fdc3:1564:5193:5b:a418:3f2b:128f:60dd
fe80:0:0:0:6c77:78c0:e91e:e352
Done

Let me know what I'm missing in the setup.

Additional Note - My ISP is not supporting IPv6 addressing to access the internet, I've confirmed that by ping6 2001:4860:4860::8888 which says, "Network is unreachable", if I use IPv4 it responds. Does it matter in this case?

[askabu]

I'm able to ping the external IPv4 address with the help NAT64. But the thread_things_io_coap_pca10100 project still gives the DNS Timeout

This is from my debug terminal on the CoAP node

<info> app_timer: RTC: initialized.
<info> app: Thread version   : OPENTHREAD/20191113-00534-gc6a258e3; NRF52833; Apr  5 2020 21:44:15
<info> app: Network name     : Cloud CLI Demo
<info> app: Thread interface has been enabled.
<info> app: 802.15.4 Channel : 15
<info> app: 802.15.4 PAN ID  : 0x1234
<info> app: Radio mode       : rx-on-when-idle
<info> app: State changed! Flags: 0x011FD33D Current role: 1

<info> app: State changed! Flags: 0x008010E4 Current role: 3

<info> app: State changed! Flags: 0x00000200 Current role: 3

<info> app: State changed! Flags: 0x00000001 Current role: 3

<info> app: DNS response error 28.

<info> app: DNS response error 28.