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. > ________________________________ >
