| Attributes |
string
key
mandatory
noNotification
restricted |
-
applicationName
-
The name of the application. The attribute name and value of is used in the applications RDN.
|
DnsMaxNumberCachedRecordsDT |
-
dnsCacheSize
=
20000
-
This attribute defines the maximum number of cached resource records.
|
DnsDscpValueDT |
-
dnsDscpValue
=
CS0
-
This attribute defines the DSCP(Differentiated Services Code Point) value used for all DNS sockets,this applies both TCP and UDP sockets used by DNS Resolver.
DnsDscpValue accepts a decimal value in the range 0..63 or the following names as specified in IANA registry( for decimal values and RFC references, refer https://www.iana.org/assignments/dscp-registry/dscp-registry.xhtml#dscp-registry-1)
-Class Selector(CS) code points : CS0(0),CS1(8),CS2(16),CS3(24),CS4(32),CS5(40),CS6(48),CS7(56) -for more information on these names, refer to RFC2474.
-Assured Forwarding(AF) code points: AF11(10),AF12(12),AF13(14),AF21(18),AF22(20),AF23(22),AF31(26),AF32(28),AF33(30),AF41(34),AF42(36),AF43(38) -for more information on these names, refer to RFC2597.
-Expedited Forwarding code points : EF(46) -for more information on these names, refer to RFC3246.
-Capacity Admitted Voice Traffic code points: VOICE-ADMIT(44) -for more information on these names, refer to RFC5865.
Format: [0..63] or [names as specified in IANA registry]
Access : Read-Write
Change effect: Immediate
Dependencies : None
Requirement: Optional
Specification: RFC2474,RFC2597,RFC3246,RFC5865
|
DnsExpiredCacheBehaviorDT |
-
dnsExpiredCacheBehavior
=
REMOVED
-
This attribute defines the life cycle management of cached resource records.
|
DnsLocalAddressDT[0..10] nonUnique ordered |
-
dnsLocalAddress
=
0.0.0.0
-
The IP address of the local host. Used as source IP address in DNS queries.
Note1: If no attributes have been specified the system will select a local address.
Note2: To make the system less vulnerable to cache poisoning it is recommended that multiple entries are specified.
|
DnsRetransmissionTimerDT |
-
dnsRetransmissionTimer
=
10
-
This attribute defines the retransmission timer for the DNS stack, to retransmit queries to the external DNS server.
|
DnsServerEntryDT[0..] nonUnique ordered |
-
dnsServerEntry
=
0:0.0.0.0
-
This attribute defines the following properties of a DNS server:
- lookup
- priority
- address
- port
address is mandatory. The address is either an IPv4 address or an IPv6 address enclosed in square brackets. It is possible to configure several attributes. There may be a mix of IPv4 and IPv6 attributes.
port is optional. No colon (':') separator shall be used if port is left out. If not configured, port is assigned a default value of 53 by the system.
Example: 10.1.1.1
[::6]:53
lookup is optional. No colon (':') separator shall be used if lookup is left out. When a DNS Server is configured with a specific lookup, the DNS Server is dedicated to handle DNS queries for that lookup. If lookup is not specified, the server is considered as a general server handling all sorts of DNS queries for which no specific DNS server is applicable. Several lookups can be specified for a given server.
Example: 10.1.1.1
[::6]:53
http:[2000::4:1]
tel:[2000::4:1]
priority is optional. No colon (':') separator shall be used if priority is left out. The priority controls which distribution mechanism to be used. Two distribution mechanisms are supported: Primary/Standby and Load Sharing. If a Primary/Standby distribution mechanism is required, the Primary Server shall be assigned the lowest priority value; the first Standby server shall be assigned the second lowest priority value; the second Standby server shall be assigned the third lowest priority value; etc. The Primary/Standby distribution mechanism is relevant to DNS servers of the same lookup (or no lookup). If a Load Sharing distribution mechanism is required, the same priority value shall be assigned to these DNS Servers. These servers form a load sharing group. The load sharing distribution mechanism is relevant to DNS servers of the same lookup (or no lookup). In case priority is not specified, Primary/Standby distribution mechanism will apply, and the system will assign a priority (next available value) for that lookup.
Example: 0:10.1.1.1
1:[::6]:53
http:0:[2000::4:1]
tel:0:[2000::4:1]
Within each lookup both distribution mechanisms can be applied as it is possible to specify several load sharing groups for a certain lookup. Then the servers with the same lowest priority constitute a Primary group, the servers with the same second lowest priority constitute a Standby group, etc.
Example: 0:10.1.1.1
0:10.1.1.2
0:10.1.1.3
1:[::6]:53
1:[::7]
http:0:[2000::4:1]
http:0:[2000::4:2]
http:1:[2000::4:3]
http:1:[2000::4:4]
http:2:[2000::4:5]
http:2:[2000::4:6]
tel:0:[2000::4:1]
tel:0:[2000::4:2]
tel:0:[2000::4:3]
tel:1:[2000::4:4]
tel:1:[2000::4:5]
Note: Attribute DnsServerEntry is used together with attribute DnsLocalAddress. This means that some entries of DnsServerEntry may be ruled out. A DnsServerEntry entry is ruled out if the IP version does not match the IP version of any DnsLocalAddress entry. For example if multiple DnsServerEntry entries have been specified with a mix of IPv4/IPv6 entries while attribute DnsLocalAddress only consists of IPv4 addresses, then none of the IPv6 entries for DnsServerEntry will be used.
|
uint32[0..1]
noNotification |
-
groupId
=
0
-
Relevant only in TSP.
Independently from the permissions, this attribute can always be modified by the MO
owner and by the Super Administrator.
|
uint32[0..1]
noNotification |
-
ownerId
=
0
-
Relevant only in TSP.
Independently from the permissions, this attribute can always be modified by the MO
owner and by the Super Administrator.
|
integer[0..1]
noNotification |
-
permissions
=
9
-
Relevant only in TSP.
The operations allowed for the group members and for other administrators are represented
as a bitmap: groupRead(1), groupUpdate(2), groupManage(4), otherRead(8), otherUpdate(16),
otherManage(32). Read permission means to read the MO attributes and to see the children of the MO;
write permission allows to modify the MO attributes and manage permission allows to create and
delete children of the MO. The owner of the MO has all the permissions. The attribute can only be
modified by the owner of the MO or by the Super Administrator. By default, the MO is created with the
permissions determined by the defaultPermissions attribute of the owner administrator.
|
DN[0..1]
noNotification |
-
shareTree
=
nodeName=jambala
-
Relevant only in TSP.
This attribute refers to a container object and implies that all administrators defined
under this shareTree value have the privileges set as share permissions over the container and its leaf object. Obsolete, must not be used.
|