This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Issue Resolving DNS in Border Router

I'm following the tutorial in the NRF52840 SDK on setting up a Thread Border Router here and I've run into some issues during testing. For one, I'm trying to resolve ipv4.google.com on the dev kit running the CLI, and in response I get Error 28: ResponseTimeout. Looking into the system log for OpenWRT, the dnsmasq service fails to create a listening socket as port 53 is in use. As a result, the service doesn't start. If I try to ping 8.8.8.8 directly from the OpenWRT command line, I get a response, but pinging google.com returns an unknown host or a bad address error (depending on if I use the command line interface or the web interface).

I'd really appreciate any help you folks can provide and will update with any additional information requested. Thanks!

Parents
  • Hi Jørgen, I'm currently using version 0.10.0 of the SDK for Thread and version 0.10.0-1.alpha on the OpenWRT build with the Thread stack. I moved the setup to my work network today and was able to resolve the dns for ipv4.google.com. The border router is connected to the internet via ethernet and both my work and home connection are IPv4. Also, I still can't ping the primary google dns server (limited because of my IPv4 connection?).

    Edit: Right after I posted this, I successfully pinged the primary Google DNS server from the CLI. I'd still appreciate any help in resolving this issue on my home network. Thanks!

Reply
  • Hi Jørgen, I'm currently using version 0.10.0 of the SDK for Thread and version 0.10.0-1.alpha on the OpenWRT build with the Thread stack. I moved the setup to my work network today and was able to resolve the dns for ipv4.google.com. The border router is connected to the internet via ethernet and both my work and home connection are IPv4. Also, I still can't ping the primary google dns server (limited because of my IPv4 connection?).

    Edit: Right after I posted this, I successfully pinged the primary Google DNS server from the CLI. I'd still appreciate any help in resolving this issue on my home network. Thanks!

Children
No Data
Related