Hi Surya and Greg, Doing more some tests I discovered something that appears an issue on NuttX nslookup:
NuttShell (NSH) NuttX-8.2 nsh> ifconfig eth0 192.168.15.113 nsh> nslookup google.com Host: google.com IPv4 Addr: 216.58.222.78 nsh> nslookup receiver-producao.xpdia9pary.sa-east-1.elasticbeanstalk.com Host: receiver-producao.xpdia9pary.sa-east-1.elasticbeanstalk.com IPv4 Addr: 18.231.71.100 nsh> nslookup receiver.followenergy.com nsh: nslookup: gethostbyname failed: 2 nsh> The domain name "receiver.followenergy.com" redirects to "receiver-producao.xpdia9pary.sa-east-1.elasticbeanstalk.com" that point to 18.231.71.100. In this case NuttX nslookup fails. Doing the same test on Linux: $ nslookup receiver.followenergy.com Server: 127.0.0.53 Address: 127.0.0.53#53 Non-authoritative answer: receiver.followenergy.com canonical name = receiver-producao.xpdia9pary.sa-east-1.elasticbeanstalk.com. Name: receiver-producao.xpdia9pary.sa-east-1.elasticbeanstalk.com Address: 18.228.162.209 Name: receiver-producao.xpdia9pary.sa-east-1.elasticbeanstalk.com Address: 18.231.71.100 I used the same Freedom-K64F board to test it. What you do think? BR, Alan On 3/24/20, Alan Carvalho de Assis <acas...@gmail.com> wrote: > Hi Surya, > > I just tested nslookup on freedom-k64f board and it worked fine: > > NuttShell (NSH) NuttX-8.2 > nsh> ifconfig eth0 192.168.15.85 > nsh> nslookup google.com > Host: google.com IPv4 Addr: 216.58.222.78 > nsh> nslookup youtube.com > Host: youtube.com IPv4 Addr: 172.217.29.78 > nsh> ping google.com > PING 216.58.222.78 56 bytes of data > 56 bytes from 216.58.222.78: icmp_seq=0 time=20 ms > 56 bytes from 216.58.222.78: icmp_seq=1 time=20 ms > 56 bytes from 216.58.222.78: icmp_seq=2 time=20 ms > 56 bytes from 216.58.222.78: icmp_seq=3 time=20 ms > 56 bytes from 216.58.222.78: icmp_seq=4 time=20 ms > 56 bytes from 216.58.222.78: icmp_seq=5 time=20 ms > 56 bytes from 216.58.222.78: icmp_seq=6 time=20 ms > 56 bytes from 216.58.222.78: icmp_seq=7 time=20 ms > 56 bytes from 216.58.222.78: icmp_seq=8 time=20 ms > 56 bytes from 216.58.222.78: icmp_seq=9 time=20 ms > 10 packets transmitted, 10 received, 0% packet loss, time 10100 ms > nsh> > > So, probably it is some issues on your configuration. > > BR, > > Alan > > On 3/24/20, Surya prakash Verma <surya.prak...@tataelxsi.co.in.invalid> > wrote: >> Hello Greg, >> >> Thank you for your reply. >> >> We have checked CONFIG_NET_ARP_SEND configuration and it is already >> enabled >> but still getting same issue. >> >> Thanks & Regards, >> Surya >> ________________________________ >> From: Gregory Nutt <spudan...@gmail.com> >> Sent: 17 March 2020 20:31 >> To: dev@nuttx.apache.org <dev@nuttx.apache.org> >> Subject: Re: nslookup issue in DNS name resolution >> >> ________________________________ >> **This is an external email. Please check the sender’s full email >> address >> (not just the sender name) and exercise caution before you respond or >> click >> any embedded link/attachment.** >> ________________________________ >> >> Try adding CONFIG_NET_ARP_SEND if you are using IPv4 >> >> On 3/17/2020 8:50 AM, Surya prakash Verma wrote: >>> Hello All, >>> >>> I am trying to configure and test DNS Name resolution on RX65N. We are >>> facing hang issue when running "nslookup google.com". >>> >>> After step debugging, We have observed, it is hanging at below code: >>> >>> ret = psock->s_sockif->si_recvfrom(psock, buf, len, flags, from, >>> fromlen); >>> in file recvfrom.c >>> >>> We have done some experiment around it and observed "nslookup >>> google.com" >>> works fine if execute ping prior to nslookup execution. >>> >>> After debugging observed that psock-> s_conn is NULL in not working >>> case. >>> >>> Let me know if anyone facing same issue. >>> >>> Please find related configuration: >>> CONFIG_LIBC_NETDB=y >>> CONFIG_NETDB_DNSCLIENT=y >>> CONFIG_NETDB_DNSCLIENT_ENTRIES=8 >>> CONFIG_NETDB_DNSCLIENT_NAMESIZE=32 >>> CONFIG_NETDB_DNSCLIENT_LIFESEC=3600 >>> CONFIG_NETDB_DNSCLIENT_MAXRESPONSE=96 >>> CONFIG_NETDB_DNSCLIENT_MAXIP=1 >>> CONFIG_NETDB_DNSCLIENT_RECV_TIMEOUT=30 >>> CONFIG_NETDB_DNSCLIENT_RETRIES=3 >>> CONFIG_NETDB_DNSSERVER_NOADDR=y >>> CONFIG_NSH_DISABLE_NSLOOKUP is not set >>> >>> Thanks & Regards, >>> Surya >>> >>> >>> >>> >>> ________________________________ >>> Disclaimer: This email and any files transmitted with it are >>> confidential >>> and intended solely for the use of the individual or entity to whom they >>> are addressed. If you are not the intended recipient of this message , >>> or >>> if this message has been addressed to you in error, please immediately >>> alert the sender by reply email and then delete this message and any >>> attachments. If you are not the intended recipient, you are hereby >>> notified that any use, dissemination, copying, or storage of this >>> message >>> or its attachments is strictly prohibited. Email transmission cannot be >>> guaranteed to be secure or error-free, as information could be >>> intercepted, corrupted, lost, destroyed, arrive late or incomplete, or >>> contain viruses. The sender, therefore, does not accept liability for >>> any >>> errors, omissions or contaminations in the contents of this message >>> which >>> might have occurred as a result of email transmission. If verification >>> is >>> required, please request for a hard-copy version. >>> ________________________________ >>> >> >> >
