<?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>OpenThread border router DNS - use domain directive from resolve.conf</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/102677/openthread-border-router-dns---use-domain-directive-from-resolve-conf</link><description>I am using the border router&amp;#39;s upstream DNS and $ sudo ot-ctl nat64 state shows that it is active. My Thread child device can resolve hosts like google.com without issue. The upstream DNS uses &amp;quot;iot-edge&amp;quot; as an alias for &amp;quot;pc7.ab.cd.com.&amp;quot; However, if my</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 17 Aug 2023 12:29:51 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/102677/openthread-border-router-dns---use-domain-directive-from-resolve-conf" /><item><title>RE: OpenThread border router DNS - use domain directive from resolve.conf</title><link>https://devzone.nordicsemi.com/thread/441862?ContentTypeID=1</link><pubDate>Thu, 17 Aug 2023 12:29:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:879f4463-2899-4352-9fd2-538c188ef919</guid><dc:creator>brown27</dc:creator><description>&lt;p&gt;I was able to talk with an OpenThread developer via discussion post on their GitHub repository page. He clarified that the command line interface&amp;#39;s &amp;quot;srp domain&amp;quot; commands are for the OpenThread network itself - not the upstream network that the border router is connected to.&lt;/p&gt;
&lt;p&gt;As a result, my Thread child will need to use fully qualified domain names in its DNS lookups to get things working. This is OK - I have some ideas for alternative means of communicating the domain name to the Thread child and can use that to compose fully qualified domain names.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: OpenThread border router DNS - use domain directive from resolve.conf</title><link>https://devzone.nordicsemi.com/thread/441348?ContentTypeID=1</link><pubDate>Tue, 15 Aug 2023 11:03:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:39f4b593-15f9-44b9-9217-b59d85a64dca</guid><dc:creator>Charlie</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I looked at the source codes from openthread github, it seems the upstream resolver is configured in prosix running on RPI. Could you follow the following discussion to check?&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/openthread/openthread/issues/9021"&gt;Update the list of upstream dns server when resolv.conf is modified · Issue #9021 · openthread/openthread (github.com)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Charlie&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: OpenThread border router DNS - use domain directive from resolve.conf</title><link>https://devzone.nordicsemi.com/thread/441200?ContentTypeID=1</link><pubDate>Mon, 14 Aug 2023 14:32:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:42212310-78a6-4762-8e50-964b06dc436c</guid><dc:creator>brown27</dc:creator><description>&lt;p&gt;Unfortunately `srp server domain [domain-name]` did not solve my issue. If my Thread child device does a DNS lookup for &amp;quot;example&amp;quot; it gets&amp;nbsp;the following response:&lt;/p&gt;
&lt;p&gt;&amp;quot;Standard query response 0xabcd No such name A example SOA a.root-servers.net&amp;quot;&lt;/p&gt;
&lt;p&gt;However, `$ nslookup example` and `$ dig +search example` on the border router yield the desired IPv4 address. Is there anything else I should be trying or investigating?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: OpenThread border router DNS - use domain directive from resolve.conf</title><link>https://devzone.nordicsemi.com/thread/440685?ContentTypeID=1</link><pubDate>Thu, 10 Aug 2023 09:37:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:64a96320-182e-457a-9a54-17e4e65079a7</guid><dc:creator>Charlie</dc:creator><description>&lt;p&gt;Thanks for the update!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: OpenThread border router DNS - use domain directive from resolve.conf</title><link>https://devzone.nordicsemi.com/thread/440497?ContentTypeID=1</link><pubDate>Wed, 09 Aug 2023 12:31:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1a619e07-08b0-4f0c-8c95-edcf04614bb4</guid><dc:creator>brown27</dc:creator><description>&lt;p&gt;I am currently sending DNS requests to the border router and using its upstream DNS server to fulfil requests. I have set up the border router as instructed&amp;nbsp;&lt;a href="https://openthread.io/codelabs/openthread-border-router-nat64#1"&gt;here&lt;/a&gt;&amp;nbsp;and use `&lt;span&gt;otDnsClientResolveIp4Address()` on the Thread child to initiate these requests.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I think that I might want to use `$ sudo ot-ctl srp server domain [domain-name]` on the border router and `grep` the domain name from `/etc/resolv.conf`. Otherwise, the border router seems to use `&lt;/span&gt;default.service.arpa.` as the default domain. I will try this and report back on how it works.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: OpenThread border router DNS - use domain directive from resolve.conf</title><link>https://devzone.nordicsemi.com/thread/440465?ContentTypeID=1</link><pubDate>Wed, 09 Aug 2023 10:40:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:47b6156a-490c-4680-a1de-8bc263f45372</guid><dc:creator>Charlie</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;This may be related to the&amp;nbsp;&lt;span&gt;aConfig argument initialization on your codes.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Could you test the CLI DNS resolution commands similar to&amp;nbsp;&lt;a href="https://groups.google.com/g/openthread-users/c/6uYzwjk6VHo/m/KPgjb_3PCQAJ"&gt;https://groups.google.com/g/openthread-users/c/6uYzwjk6VHo/m/KPgjb_3PCQAJ&lt;/a&gt;&amp;nbsp;first with your OTBR as DNS server?&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/openthread/openthread/blob/main/src/cli/cli.cpp"&gt;openthread/src/cli at main · openthread/openthread (github.com)&lt;/a&gt;&amp;nbsp;has the source codes about how this command is implemented, which should show the process of aConfig initialization.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Charlie&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>