buglwIP - A Lightweight TCP/IP stack - Bugs: bug #56280, lwIP DNS need to support CNAME...


You are not allowed to post comments on this tracker with your current authentication level.

bug #56280: lwIP DNS need to support CNAME Resource Record

Submitted by:  Gao Qingshui <kevingao>
Submitted on:  Tue 07 May 2019 07:32:55 AM UTC  
Category:  DNS Severity:  3 - Normal
Item Group:  Feature Request Status:  Fixed
Privacy:  Public Assigned to:  Simon Goldschmidt <goldsimon>
Open/Closed:  Closed Planned Release:  None
lwIP version:  git head

Fri 26 Jun 2020 06:04:43 AM UTC, comment #5: 

Hi, I attached a file to address CNAME DNS resolution in DNS responses.  Is this what I was meant to do?

Chris Nocker <nocker>
Mon 18 May 2020 02:37:34 PM UTC, comment #4: 

There are situations in which the CNAME is required. I'm currently working on one such project. Each unit of my product cooks up a hostname using a unique secret number as part of the name. It then does a DNS lookup to get the CNAME, which it then stores for future use. That CNAME is periodically refreshed by another DNS lookup. The CNAME must also be added to our client's whitelist of allowed external destinations. So the CNAME is certainly need for this case.

Jeff Thompson <jeffthompson>
Tue 04 Feb 2020 09:18:49 PM UTC, comment #3: 

> Ping?

No answer -> closing as invalid. Just continue to post here if you think otherwise...

Simon Goldschmidt <goldsimon>
Project AdministratorIn charge of this item.
Tue 14 May 2019 07:36:47 PM UTC, comment #2: 


Simon Goldschmidt <goldsimon>
Project AdministratorIn charge of this item.
Tue 07 May 2019 06:04:09 PM UTC, comment #1: 

I don't see why. A recursive DNS server should do the recursion and answer all records up to A/AAAA (or whatever asked) records.

Sylvain Rochet <gradator>
Project Member
Tue 07 May 2019 07:32:55 AM UTC, original submission:  

As most of the DNS Standard query response contains CNAME resource record to declare the alias name of the domain name which need to be resolved, so I think lwIP need to support CNAME RR, else most of the DNS domain name resolution would be failed to make the DNS APIs unusable, such as getaddrinfo.

Gao Qingshui <kevingao>


Attached Files
file #49395:  0001-DNS-Allowed-processing-of-a-DNS-response-that-contai.patch added by nocker (1KiB - application/octet-stream - This is the "git format-patch" file for my previously attached file)
file #49374:  dns.c added by nocker (54KiB - text/plain - DNS: Allowed processing of a DNS response that contains a CNAME as the first answer.)


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by nocker (Updated the item)
  • -email is unavailable- added by jeffthompson (Posted a comment)
  • -email is unavailable- added by goldsimon (Posted a comment)
  • -email is unavailable- added by gradator (Posted a comment)
  • -email is unavailable- added by kevingao (Submitted the item)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.




    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-06-30 nocker Attached File- => Added 0001-DNS-Allowed-processing-of-a-DNS-response-that-contai.patch, #49395
    2020-06-26 nocker Attached File- => Added dns.c, #49374
    2020-02-04 goldsimon StatusNone => Fixed
        Assigned toNone => goldsimon
        Open/ClosedOpen => Closed

    Back to the top

    Powered by Savane 3.6