>> MIB - Management Information Base
|
>> Table: ip6DhcpClientFqdnOptTable - (.1.3.6.1.4.1.272.4.5.100.4.7.1) Description: Statically assigned client-FQDNs (see 4 of RFC-4704). If router is configured as DNS-server then related (name, address) entries are added also into DNS-cache, independently from whether FQDN-option is requested or not. In case of FQDN-request, at most one entry may be replied. Thus, following rule applies. If entry with empty 'Name' matches and if client provides own name then it is simply confirmed. Otherwise, 'first' matching one is taken according to sorting-order defined via 'ip6DhcpClientFqdnOptListIdx'. |
Id | Internal identifier of this FQDN-entry. |
AdminStatus | Activate/deactivate/delete this FQDN-entry. Enumerations: - enabled (1)
- disabled (2)
- delete (3)
|
Description | Textual description of this FQDN-entry. Length: 0 to 255 |
OptionSetId | 'Id' value of related 'ip6DhcpOptionSet' entry. If no 'ip6DhcpOptionSetId' matches, this FQDN-entry is ignored. 'ClientDUID' must be specified in related 'ip6DhcpOptionSet' entry in order to avoid that same FQDN is assigned to multiple clients. Range: 1 to 65535 |
ListIdx | Defines sorting-order in case of several matching FQDN-entries. Lower number means 'earlier in list'. Range: 0 to 255 |
Name | Fully qualified domain-name, or empty. If empty, 'Name' field of related 'ip6DhcpStatefulClient' is used instead, if not also empty. At most one entry with empty 'Name' should be specified per client. Fully qualified domain-names must have trailing dot for distinction from relative/partial domain-names. However, many users/admins tend to forget this. Thus, 'proper version' of this field is stored in field 'FullName'. Length: 0 to 255 |
FullName | 'Proper' fully qualified domain-name, or empty. See description of field 'Name'. Length: 0 to 255 |
|