<?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>NRF9160 DNS resolution issue</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/69175/nrf9160-dns-resolution-issue</link><description>Hi, We were trying with a new n/w carrier in Canada ( Maxim ). nrf9160 is able to connect to the network, but it is not able to resolve our server URL ipv4 address. Below error is coming when &amp;#39;getaddrinfo()&amp;#39; function is called. getaddrinfo failed, ERR</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 08 Dec 2020 09:29:19 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/69175/nrf9160-dns-resolution-issue" /><item><title>RE: NRF9160 DNS resolution issue</title><link>https://devzone.nordicsemi.com/thread/283734?ContentTypeID=1</link><pubDate>Tue, 08 Dec 2020 09:29:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:91635395-aa3e-4893-8b5b-93197cbcd663</guid><dc:creator>Didrik Rokhaug</dc:creator><description>&lt;p&gt;Yes, it is %XEPCO, my apologies.&lt;/p&gt;
&lt;p&gt;EAI_SYSTEM does not give much information in itself. Instead, it instructs you to check errno, to get the &amp;quot;real&amp;quot; error code.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF9160 DNS resolution issue</title><link>https://devzone.nordicsemi.com/thread/283731?ContentTypeID=1</link><pubDate>Tue, 08 Dec 2020 09:14:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b659fc0b-ff77-42e5-8847-3c64433de45d</guid><dc:creator>Aswin P V</dc:creator><description>&lt;p&gt;We are using the Nb-IoT network.&lt;/p&gt;
&lt;p&gt;We will try the XPCO command, just to confirm is it XPCO or XEPCO as i can see one more command in AT manual.&lt;/p&gt;
&lt;p&gt;&lt;span&gt;DNS_EAI_SYSTEM is the error code getting for&amp;nbsp;getaddrinfo() function&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF9160 DNS resolution issue</title><link>https://devzone.nordicsemi.com/thread/283562?ContentTypeID=1</link><pubDate>Mon, 07 Dec 2020 13:39:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:46ebe92a-bf61-40e8-a3ba-a5c8dac97a26</guid><dc:creator>Didrik Rokhaug</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Are you using LTE-M or NB-IoT?&lt;/p&gt;
&lt;p&gt;If you are using NB-IoT, you can try to disable ePCO either with the %XPCO AT command, or by setting CONFIG_LTE_LEGACY_PCO_MODE=y in prj.conf (if you are building with SES, you must re-open the project or use &amp;#39;Project-&amp;gt;Run CMake...&amp;#39; for the change to take effect).&lt;/p&gt;
&lt;p&gt;That has solved some DNS related issues in other networks.&lt;/p&gt;
&lt;p&gt;If that does not help, can you print the value of &lt;em&gt;errno&lt;/em&gt;?&lt;/p&gt;
&lt;p&gt;But, to debug this properly, I would probably end up needing a &lt;a href="https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/getting-started-cellular/posts/how-to-get-modem-trace-using-trace-collector-in-nrf-connect"&gt;modem trace&lt;/a&gt;. Can you capture one showing the error?&lt;/p&gt;
&lt;p&gt;You can set the DNS server with &lt;a href="https://github.com/nrfconnect/sdk-nrfxlib/blob/master/bsdlib/include/nrf_socket.h#L1510"&gt;nrf_setdnsaddr&lt;/a&gt; in NCS v1.2.0 and newer.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Didrik&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>