tasklwIP - A Lightweight TCP/IP stack - Tasks: task #14129, DNS: implement domain search list...

 
 

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

task #14129: DNS: implement domain search list (e.g. filled via DHCP)

Submitter:  Simon Goldschmidt <goldsimon>
Submitted:  Tue 23 Aug 2016 07:49:58 AM UTC
   
 
Category:  None Should Start On:  Tue 23 Aug 2016 12:00:00 AM UTC
Should be Finished on:  Tue 23 Aug 2016 12:00:00 AM UTC Priority:  5 - Normal
Status:  None Privacy:  Public
Assigned to:  None Percent Complete:  0%
Open/Closed:  Open Planned Release:  None
Effort:  0.00

Wed 14 Nov 2018 07:47:32 PM UTC, comment #4: 

Re comment #2:
I know. Comment #1 was meant as a reminder that we need to filter out '.local' from the DNS search list, even if someone sets it (e.g. via DHCP).

Re comment #3:
Yes, do you want to provide a patch?

 Simon Goldschmidt <goldsimon>
Group administrator
Wed 14 Nov 2018 01:41:58 AM UTC, comment #3: 

A single domain can be obtained from DHCP option 15.

A domain search list could also be obtained from DHCP option 119. However, from what I've read, Windows doesn't request option 119, and Windows DHCP servers don't provide it. Linux and MacOS do request it though. See: Which DHCP Client OS Support DHCP Option 119 Domain Suffix Search? - Server Fault.

Note that getting the domain from DHCP option 15 may be useful for other things besides DNS domain. For example, RFC 3958 defines DDDS which does DNS look-ups of services (using NAPTR, SRV) for the local domain which can be discovered with DHCP option 15. E.g. RFC 6011 SIP User Agent Configuration can use this. So, adding DHCP option 15 support can be useful even before DNS adds support for a domain search list.

 Craig McQueen <cmcqueen1975>
Wed 14 Nov 2018 12:25:40 AM UTC, comment #2: 

I have not seen PC systems (Windows or Linux) in which ".local" is a DNS search domain. So ".local" must be explicitly in the hostname in order to do an mDNS lookup.

See here for a usage example for Mac: Adding “local” to the DNS Search Domains has no effect

 Craig McQueen <cmcqueen1975>
Wed 07 Dec 2016 11:19:42 AM UTC, comment #1: 

Important when used with mDNS: ".local" shall not be added to domains (not ending with ".") with 2 or more parts to prevent "stealing" identity when the normal DNS server does not reply.

 Simon Goldschmidt <goldsimon>
Group administrator
Tue 23 Aug 2016 07:49:58 AM UTC, original submission:  


 Simon Goldschmidt <goldsimon>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by cmcqueen1975 (Posted a comment)
  • -email is unavailable- added by goldsimon (Submitted the item)

    •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    No changes have been made to this item

    Back to the top

    Copyright © 2024 Free Software Foundation, Inc.
    Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
    The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team.
    Page source code

    Powered by Savane 3.13-5884.
    Corresponding source code