{{reference}} The layer 3 interface over which the test is to be
performed. Example: ''Device.IP.Interface.1''.
{{template|INTERFACE-ROUTING}}
Specifies the Host Name that NS Lookup is to look for. The current
domain name MUST be used unless the name is a fully qualified name.
Specifies the DNS Server name or IP address that NS Lookup is to use
for the lookup. The name of this server will be resolved using the
default DNS server unless an IP address is provided.
If {{empty}} is specified, the device's default DNS server will be
used.
Timeout in {{units}} that indicates that a request has failed.
The number of times the device SHOULD repeat the execution of the
NSLookup using the same input parameters. If the diagnostics test fails
the CPE MAY terminate the test without completing the full number of
repetitions.
Each repetition will use a Result instance to hold the NSLookup result
data.
{{numentries}}
Total number of Result entries from the most recent invocation of the
test.
Number of successfully executed repetitions.
Results from the most recent invocation of the test, one instance per
repetition.
Result Parameter to represent whether the NS Lookup was successful or
not.
Errors for individual Result instances do not get bubbled up to
{{param|#.DiagnosticsState}}.
A failure on a specific attempt does not mean that the overall test
failed, but a failure on all attempts means that
{{param|#.DiagnosticsState}} SHOULD be
{{enum|Error_Other|#.DiagnosticsState}}.
Result parameter to represent whether the answer is Authoritative or
not.
Indicates that the NS Lookup failed to find the host.
Result parameter to represent the fully qualified name for the Host
Name in the calling parameter (e.g. HostName.DomainName); if no
response was provided, then this parameter is {{empty}}.
{{list}} Indicates the IP Address results returned by the NS Lookup;
if no response was provided, then this parameter is {{empty}}.
Result parameter to represent the actual DNS Server IP address that
the NS Lookup used.
Response time (for the first response packet) in {{units}}, or 0 if
no response was received.
Properties for Domain Name Service (DNS).
The DNS record types that are supported by the device. {{enum}}
{{bibref|RFC1035}}
{{bibref|RFC3596}}
{{bibref|RFC2782}}
{{bibref|RFC1035}}
{{numentries}}
This object specifies Zone file configuration of the DNS server.
Enables or disables the DNS zone.
Domain name that is associated with the zone.
The mechanism via which the Zone was created.
Note: This parameter was changed to writeOnceReadOnly in the Device:2.18 version.
Used for indicating that the entry was created by the end-user.
For example through the web user interface.
Used for indicating that the entry was created by the system itself.
Used for indicating that the entry was created by a Controller.
Specifies the Layer 3 interface on which the zone should be available.
Example: ''Device.IP.Interface.1'' or ''Device.Logical.Interface.1''.
{{numentries}}
This object specifies the resource records (RR) of the DNS zone.
Enables or disables the entry in the zone file.
List of hostnames that are associated with the {{object}}.
Indicates the owner of the {{object}} instance.
Note: This parameter was changed to writeOnceReadOnly in the Device:2.18 version.
Used for indicating that the entry was created by the end-user.
For example through the web user interface.
Used for indicating that the entry was created by the system itself.
Used for indicating that the entry was created by a Controller.
Host table entries associated with the device.
The date and time in UTC when the entry was last changed.
Client properties for Domain Name Service (DNS). The DNS client
resolves FQDN on behalf of device internal (client) applications.
Enables or disables the DNS client.
The status of the DNS client. {{enum}}
The {{enum|Error}} value MAY be used by the CPE to indicate a locally
defined error condition.
{{numentries}}
This table contains the DNS Server IP address to be used by the DNS
Client (it does ''not'' model a DNS Server). Entries are either
automatically created as result of DHCP (v4 or v6), IPCP, 3GPP-NAS (3GPP Non Access Stratum), or RA
received DNS server information, or are statically configured by the
Controller.
Enables or disables this entry.
The status of this entry. {{enum}}
The {{enum|Error}} value MAY be used by the CPE to indicate a locally
defined error condition.
DNS server IP address.
Note: {{param}} is only writable when {{param|Type}} is
{{enum|Static|Type}}; otherwise, {{param}} is automatically
configured as result of DHCP, IPCP, 3GPP-NAS, or RA received DNS server
information.
{{reference}} This parameter specifies the IP interface over which
the DNS query is sent.
{{template|INTERFACE-ROUTING}}
Note: {{param}} is only writable when {{param|Type}} is
{{enum|Static|Type}}; otherwise, {{param}} is automatically
configured as result of DHCP, IPCP, 3GPP-NAS, or RA received DNS server
information.
Method used to assign the {{param|DNSServer}} address. {{enum}}
Table entries that are automatically created as result of DHCP, IPCP,
3GPP-NAS, or RA received DNS server information will have {{param}} set to
{{enum|DHCPv4}}, {{enum|DHCPv6}}, {{enum|IPCP}}, {{enum|3GPP-NAS}} or
{{enum|RouterAdvertisement}}, as the case may be. Manually created
table entries will have their {{param}} set to {{enum|Static}}.
{{obsoleted|2.14|because it's been replaced by
{{enum|DHCPv4}}}}
{{deleted|2.16}}
Assigned by the core network (fixed or cellular) using 3GPP NAS signalling methods.
e.g. PDU Session Establishment Request using the extended Protocol Configuration Options,
PDN Connectivity Request using the Protocol Configuration Options,
PDP Context Activation Request using the Protocol Configuration Options {{bibref|3GPP-TS.24.008|clause 10.5.6.3}}, ...
This information is available from the AT commands {{bibref|3GPP-TS.27.007|Clause 10.1.23}} PDP context read dynamic parameters +CGCONTRDP.
DNS Relay object. The DNS proxy (or relay) function allows the
forwarding of local network DNS queries to local or external DNS
server(s) {{bibref|RFC5625}}.
Enables or disables the DNS Relay function.
The status of the DNS relay. {{enum}}
The {{enum|Error}} value MAY be used by the CPE to indicate a locally
defined error condition.
{{numentries}}
{{numentries}}
This object is used to specify the cache configuration for each Forwarding relay.
Specifies the list of the DNS forwarders to be used.
{{reference}} Specifies the IP interface over which the DNS query is
received. This is usually the LAN interface.
{{template|INTERFACE-ROUTING}}
Specifies the size of cache in kilobytes.
When '0' is specified, no DNS results will be cached.
Specifies the minimum TTL amount of time, in {{units}},
that an entry MUST be kept in the cache regardless of what has been specified by the domain owner.
When '0' is specified, then the TTL chosen by the domain owner will be applied.
Specifies the maximum TTL amount of time, in {{units}},
than an entry MUST be kept in the cache regardless of what has been specified by the domain owner.
When '0' is specified, then the TTL chosen by the domain owner will be applied.
DNS Server forwarding policy to be used by the DNS Relay. Entries are
either automatically created as result of DHCP (v4 or v6), IPCP, 3GPP-NAS (3GPP Non Access Stratum) or RA
received DNS server information, or are statically configured by the
Controller.
Note: Management of re-directing queries to the device embedded DNS
server is not defined in this version of the specification.
Enables or disables this entry.
The status of this entry. {{enum}}
The {{enum|Error}} value MAY be used by the CPE to indicate a locally
defined error condition.
DNS server IP address.
Note: {{param}} is only writable when {{param|Type}} is
{{enum|Static|Type}}; otherwise, {{param}} is automatically
configured as result of DHCP, IPCP, 3GPP-NAS or RA received DNS server
information.
{{reference}} Specifies the IP interface over which the DNS query is
sent.
{{template|INTERFACE-ROUTING}}
Note: {{param}} is only writable when {{param|Type}} is
{{enum|Static|Type}}; otherwise, {{param}} is automatically
configured as result of DHCP, IPCP, 3GPP-NAS or RA received DNS server
information.
Method used to assign the {{param|DNSServer}} address. {{enum}}
Table entries that are automatically created as result of DHCP, IPCP,
3GPP-NAS, or RA received DNS server information will have {{param}} set to
{{enum|DHCPv4}}, {{enum|DHCPv6}}, {{enum|IPCP}}, {{enum|3GPP-NAS}}, or
{{enum|RouterAdvertisement}}, as the case may be. Manually created
table entries will have their {{param}} set to {{enum|Static}}.
{{obsoleted|2.14|because it's been replaced by
{{enum|DHCPv4}}}}
{{deleted|2.16}}
Assigned by the core network (fixed or cellular) using 3GPP NAS signalling methods.
e.g. PDU Session Establishment Request using the extended Protocol Configuration Options,
PDN Connectivity Request using the Protocol Configuration Options,
PDP Context Activation Request using the Protocol Configuration Options {{bibref|3GPP-TS.24.008|clause 10.5.6.3}}, ...
This information is available from the AT commands {{bibref|3GPP-TS.27.007|Clause 10.1.23}} PDP context read dynamic parameters +CGCONTRDP.
The DNS Diagnostics object containing the
{{object|NSLookupDiagnostics}} test.
This object contains the DNS Service Discovery {{bibref|DNS-SD}} object
and parameters necessary to discover services and their associated
devices.
Upon reboot the the contents of the service table are repopulated. When
the DNS-SD service is disabled, the contents of the service table is
implementation specific.
The parameter, when {{true}}, enables the discovery of DNS-SD
services hosted by other devices.
The status of the DNS service discovery.
Indicates that the DNS-SD service is disabled.
Indicates that the DNS-SD service is enabled.
MAY be used to define an error condition.
{{numentries}}
{{numentries}}
{{reference|the {{object|##.IP.Interface}} object instance from which
DNS-SD services are advertised}}
If this parameter is not supported by an implementation then DNS-SD
services are advertised on all LAN interfaces.
{{deprecated|2.17|in favor of {{param|Advertise.{i}.Interface}}}}
{{obsoleted|2.19}}
{{deleted|2.20}}
The {{object}} table contains DNS-SD services that MUST be advertised. DNS.SD
service information is provided in DNS RR SRV records
{{bibref|RFC2782}}. The Service Instance Name {{bibref|DNS-SD|Section
4.1 Structured Instance Names}} further specifies information about the
service name (RFC2782 Service field) and domain name (RFC2782 Name
field) in the form:
Service Instance Name = [InstanceName] . [Service] . [Domain]
[Service] = _[ApplicationProtocol] . _[TransportProtocol]
RFC2782 Service field will always be equal to [InstanceName]. [Service]
RFC2782 Name field will always be equal to [Domain]
For example, an SSH service might have:
*{{param|InstanceName}} = "Secure Shell (SSH))"
*{{param|ApplicationProtocol}} = "ssh"
*{{param|TransportProtocol}} = "TCP"
*{{param|Port}} = 22
Enables or disables the advertisement of the DNS-SD service.
The status of the advertised {{object}}.
Indicates that the DNS-SD service advertisement is disabled.
Indicates that the DNS-SD service advertisement is enabled.
Indicates that a necessary configuration value is undefined or invalid.
MAY be used to define an error condition.
{{reference}} The layer 3 interface on which the DNS-SD service MUST be advertised.
Example: ''Device.IP.Interface.1'' or ''Device.Logical.Interface.1''.
{{template|INTERFACE-ROUTING}}
Human-readable instance name {{bibref|DNS-SD|Section 4.1.1 Instance
Names}} (i.e. The "[{{param}}]" portion of the '"Service
Instance Name'").
Note: This parameter was promoted to readWrite in the Device:2.18 version.
The Application Protocol, without the leading underscore, associated
with the service (e.g., daap) as defined by the DNS-SD service
{{bibref|DNS-SD|Section 7 Application Protocol Names}}.
Note: This parameter was promoted to readWrite in the Device:2.18 version.
The Transport Protocol associated with the service as defined by the
DNS-SD service {{bibref|DNS-SD|Section 4.1.2 Service Names}}.
Note: This parameter was promoted to readWrite in the Device:2.18 version.
The value to be entered into the Name field of the DNS SRV record
{{bibref|RFC2782}} which represents the fully qualified domain name
(FQDN) associated with the service as defined by the DNS-SD service
{{bibref|DNS-SD|Section 4.1.3 Domain Names}}.
Note: This parameter was promoted to readWrite in the Device:2.18 version.
The value to be entered into the Port field of the DNS SRV record
{{bibref|RFC2782}} that is used to contact the service.
Note: This parameter was promoted to readWrite in the Device:2.18 version.
{{numentries}}
This object maintains an instance of a (key/value pairs) of the
service. The information is to be provided in the DNS TXT records
{{bibref|RFC1035}} of the advertised service.
When multiple instances of the {{object}} table have the same value for
the {{param|Key}} parameter, the implementation is CPE specific.
Note: This object was promoted to readWrite in the Device:2.18 version.
The key that identifies the text record
The value of the text record.
The {{object}} table contains discovered DNS-SD services. DNS.SD
service information is provided in DNS RR SRV records
{{bibref|RFC2782}}. The Service Instance Name {{bibref|DNS-SD|Section
4.1 Structured Instance Names}} further specifies information about the
service name (RFC2782 Service field) and domain name (RFC2782 Name
field) in the form:
Service Instance Name = [InstanceName] . [Service] . [Domain]
[Service] = _[ApplicationProtocol] . _[TransportProtocol]
RFC2782 Service field will always be equal to [InstanceName]. [Service]
RFC2782 Name field will always be equal to [Domain]
For example, an SSH service might have:
*{{param|InstanceName}} = "Secure Shell (SSH))"
*{{param|ApplicationProtocol}} = "ssh"
*{{param|TransportProtocol}} = "TCP"
*{{param|Domain}} = "example.com"
*{{param|Port}} = 22
*{{param|Target}} = "ssh.example.com."
Human-readable instance name {{bibref|DNS-SD|Section 4.1.1 Instance
Names}} (i.e. The "[{{param}}]" portion of the '"Service
Instance Name'").
The Application Protocol, without the leading underscore, associated
with the service (e.g., daap) as defined by the DNS-SD service
{{bibref|DNS-SD|Section 7 Application Protocol Names}}.
The Transport Protocol associated with the service as defined by the
DNS-SD service {{bibref|DNS-SD|Section 4.1.2 Service Names}}.
The value extracted from the Name field of the DNS SRV record
{{bibref|RFC2782}} which represents the fully qualified domain name
(FQDN) associated with the service as defined by the DNS-SD service
{{bibref|DNS-SD|Section 4.1.3 Domain Names}}.
The value extracted from the Port field of the DNS SRV record
{{bibref|RFC2782}} that is used to contact the service.
The fully qualified domain name (FQDN) with the trailing dot "." of
the target host implementing the service as in the DNS SRV record
{{bibref|RFC2782}}.
The status of the discovered {{object}} at {{param|LastUpdate}} time.
{{enum}}
The ability to instantiate an inactive {{object}} is OPTIONAL.
The time an inactive {{object}} remains listed in this table is a
local matter to the device.
The {{object}} has received a response record with TTL > 0
and the {{param|#.Service.{i}.TimeToLive}} has not expired yet.
The {{object}} is considered active.
The device has received a response record containing TTL=0
indicating a goodbye message and the
{{param|#.Service.{i}.TimeToLive}} has not expired yet. The
{{object}} is considered inactive.
The {{param|#.Service.{i}.TimeToLive}} has expired. The
{{object}} is considered inactive
The date and time at which the last advertisement for this {{object}}
was received.
Includes all Host table entries, active or inactive, that correspond
to this discovered DNS.SD service.
The value extracted from the TTL field of the DNS SRV record
{{bibref|RFC2782}}.
The value extracted from the Priority field of the DNS SRV record
{{bibref|RFC2782}}.
A server selection mechanism. The value extracted from the Weight
field of the DNS SRV record {{bibref|RFC2782}} that specifies the
relative weight for entries with the same {{param|Priority}}.
{{numentries}}
This object maintains an instance of a (key/value pairs) of the
service. The information is extracted from DNS TXT records
{{bibref|RFC1035}} of the discovered service.
When multiple instances of the {{object}} table have the same value for
the {{param|Key}} parameter, the implementation is CPE specific.
The key that identifies the text record
The value of the text record.
The DNS Rebind Protection object contains parameters to enable or disable
protection against DNS rebind attacks.
It prevents DNS-based malicious software that tries to bypass the browser’s policies, by
filtering or refusing DNS answers that point to private or local IP addresses, it stops external
sites from reaching LAN devices.
Enables or Disables protection against DNS rebind attacks
Each item of the list represents an IP address or a CIDR notation
that should not be protected against rebind attacks.
Each item of the list represents a domain name and its subdomain names
that should not be protected against rebind attacks.