…sical label form used, albeit with some additional restrictions, in hostnames [ RFC0952 ]. Its syntax is identical to that described as the "preferred name syntax" in Section 3.5 of RFC 1034 RFC1034 ] as modified by RFC 1123 RFC1123 ]. Briefly, it is a Klensin Standards Track [Pa…

…rver, with the additional restriction that every label MUST meet the rules of [ RFC0952 ]. The latter restriction means that, if the query is for an internationalized domain name, it MUST use the A-label form as defined in [ RFC5890 ]. For example, to request a TLSA resource reco…

…e character, the underscored name is distinguishable from all legal host names [RFC0952]. Effectively, this convention for naming leaf nodes creates a space for the listing of "attributes" -- in the form of resource record types -- that are associated with the parent domain above…

…ange 0 to 255, separated by "."), as described in [ RFC1123 ] by reference to [ RFC0952 ]. Note that other forms of dotted notation may be interpreted on some platforms, as described in Section 7.4 , but only the dotted-decimal form of four octets is allowed by this grammar. IPv4…

…ange 0 to 255, separated by "."), as described in [ RFC1123 ] by reference to [ RFC0952 ]. Note that other forms of dotted notation may be interpreted on some platforms, as described in Section 7.4 , but only the dotted-decimal form of four octets is allowed by this grammar. IPv4…

… character, the underscored name is distinguishable from all legal host names [ RFC0952 ]. Effectively, this convention for naming leaf nodes creates a space for the listing of "attributes" -- in the form of resource record types -- that are associated with the parent domain abov…

…ange 0 to 255, separated by "."), as described in [ RFC1123 ] by reference to [ RFC0952 ]. Note that other forms of dotted notation may be interpreted on some platforms, as described in Section 7.4 , but only the dotted-decimal form of four octets is allowed by this grammar. IPv4…

…ange 0 to 255, separated by "."), as described in [ RFC1123 ] by reference to [ RFC0952 ]. Note that other forms of dotted notation may be interpreted on some platforms, as described in Section 7.4 , but only the dotted-decimal form of four octets is allowed by this grammar. IPv4…

…ange 0 to 255, separated by "."), as described in [ RFC1123 ] by reference to [ RFC0952 ]. Note that other forms of dotted notation may be interpreted on some platforms, as described in Section 7.4 , but only the dotted-decimal form of four octets is allowed by this grammar. IPv4…

…ange 0 to 255, separated by "."), as described in [ RFC1123 ] by reference to [ RFC0952 ]. Note that other forms of dotted notation may be interpreted on some platforms, as described in Section 7.4 , but only the dotted-decimal form of four octets is allowed by this grammar. IPv4…

…e range 0 to 255, separated by "."), as described in [RFC1123] by reference to [RFC0952]. Note that other forms of dotted notation may be interpreted on some platforms, as described in Section 7.4, but only the dotted-decimal form of four octets is allowed by this grammar. IPv4ad…

…ange 0 to 255, separated by "."), as described in [ RFC1123 ] by reference to [ RFC0952 ]. Note that other forms of dotted notation may be interpreted on some platforms, as described in Section 7.4 , but only the dotted-decimal form of four octets is allowed by this grammar. IPv4…

…ange 0 to 255, separated by "."), as described in [ RFC1123 ] by reference to [ RFC0952 ]. Note that other forms of dotted notation may be interpreted on some platforms, as described in Section 7.4 , but only the dotted-decimal form of four octets is allowed by this grammar. IPv4…

…e range 0 to 255, separated by "."), as described in [RFC1123] by reference to [RFC0952]. Note that other forms of dotted notation may be interpreted on some platforms, as described in Section 7.4, but only the dotted-decimal form of four octets is allowed by this grammar. IPv4ad…

…t with some additional restrictions, reflects the early syntax of "hostnames" [ RFC0952 ] and limits those names to ASCII letters, digits, and embedded hyphens. The hostname syntax is identical to that described as the "preferred name syntax" in Section 3.5 of RFC 1034 RFC1034 ] …