Any DNS experts out there want to take a crack at this? In DHCPv4, the DNS domain string was just a plain old string. dhcpinfo assumes it's plain text and spits it out without much examination. If it happens to contain embedded ASCII NUL bytes, that's too bad; the string printed will stop at the first of these.
In DHCPv6, the DNS search path is a list of entries, each of is encoded as in section 3.1 of RFC 1035. This means that arbitrary byte codes can be part of the resulting string. My plan is to decode these into strings delimited by '.' between elements and '\n' between list entries on standard output. Users who really want to see the raw bytes provided by the server can use the existing '-c' flag to spit out canonical (hex string) form. If there's a "best practice" or standard for encoding these things in a scripting environment such that i18n and the like are respected, please do let me know. -- James Carlson, KISS Network <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
