<Glossary>
<Section Letter="A">
	<Entry>
		<Term>ACL</Term>
		<Definition>Access Control List</Definition>
	</Entry>
	<Entry>
		<Term>ACL statement</Term>
		<Definition>Statement in the named.conf file that defines an address-match-list to control which hosts may or may not perform certain operations on the name server.</Definition>
	</Entry>
	<Entry>
		<Term>AD</Term>
		<Definition>Active Directory</Definition>
	</Entry>
	<!--  2 AES defs ? -->
	<Entry>
		<Term>AES</Term>
		<Definition>Advanced Encryption Standard is one of the symmetric algorithms adopted by the United States as an encryption standard.</Definition>
	</Entry>
	<Entry>
		<Term>ARP</Term>
		<Definition>Address Resolution Protocol is used to map IP addresses to hardware resources on a network.</Definition>
	</Entry>
	<Entry>
		<Term>Asymmetric Cryptography</Term>
		<Definition>As used in DNS, asymmetric cryptography uses a private key to sign data, and the corresponding public key is used to verify the signature. In one frequent example of asymmetric cryptography, User A can encrypt a message with the public key for User B, and only User B can decrypt it using his/her private key.</Definition>
	</Entry>
	<Entry>
		<Term>AUTHCONF, NOAUTHCONF, NOAUTH, or NOCONF.</Term>
		<Definition>One of the flags (- t) in dnssec-keygen syntax that indicates the required use of the generated key.  AUTH refers to the ability to authenticate data, and CONF to the ability to encrypt data.</Definition>
	</Entry>
	<Entry>
		<Term>Authenticity</Term>
		<Definition>Refers to verification that data is published by a zone's actual authoritative server. See integrity for related information.</Definition>
	</Entry>
	<Entry>
		<Term>Authoritative Server</Term>
		<Definition>Authoritative servers contain the DNS mappings, such as mappings of names to IP addresses, for all of the domains under their authoritative control. These servers are identified as the top of the authority chain for the domains they serve. They provide definitive answers to resource queries.</Definition>
	</Entry>
</Section>
<Section Letter="B">
	<Entry>
		<Term>BIND</Term>
		<Definition>Berkeley Internet Name Domain</Definition>
	</Entry>
	<Entry>
		<Term>Blackhole</Term>
		<Definition>Blackholing of DNS traffic refers to redirecting DNS query traffic to an unused IP address, in order to prevent malicious use of DNS for command, control, and communications (also referred to as botnet). See sinkhole for related information.</Definition>
	</Entry>
</Section>
<Section Letter="C">
	<Entry>
		<Term>+ cd</Term>
		<Definition>Dig switch that sets the "checking disabled" bit on the query.  You would typically use this when your validating recursive name server reports a SERVFAIL, and you need to establish if this is due to DNSSEC marking this data as improper.</Definition>
	</Entry>
	<Entry>
		<Term>Cache-poisoning DNS Attacks</Term>
		<Definition>Type of DNS attack that places incorrect data in the cache of a recursive server</Definition>
	</Entry>
	<Entry>
		<Term>Clients</Term>
		<Definition>Clients are the entities on the network that make requests of the DNS to find the location of the desired resources.</Definition>
	</Entry>
	<Entry>
		<Term>CNAME</Term>
		<Definition>Canonical Name (domain name system record)</Definition>
	</Entry>
	<Entry>
		<Term>COMSEC</Term>
		<Definition>United States Communications Security</Definition>
	</Entry>
	<Entry>
		<Term>Configuration File</Term>
		<Definition>Defines whether the name server is a master (primary) or slave (secondary) for its delegated zone or zones or a cache-only server, defines the zone or zones for which the name server has authority, and specifies which data file or files will provide zone data.  </Definition>
	</Entry>
	<Entry>
		<Term>CPU</Term>
		<Definition>Central Processing Unit</Definition>
	</Entry>
</Section>
<Section Letter="D">
	<Entry>
		<Term>+ dnssec</Term>
		<Definition>Dig switch that forces the server being queried to include the DNSSEC related data.  Use in combination with the +cd to establish if data from a zone is signed at all or if you want to determine if the validity intervals on the signatures are correct. </Definition>
	</Entry>
	<Entry>
		<Term>Daemon</Term>
		<Definition>Processes that run in the background and perform specific functions at specified times or in response to specific events (for example, email handlers and printer spoolers).</Definition>
	</Entry>
	<Entry>
		<Term>Data Files</Term>
		<Definition>Data files describe zone operations and contain the resource records that make up the smallest unit of information available through DNS.</Definition>
	</Entry>

	<Entry>
		<Term>Data Replacement DNS Attack</Term>
		<Definition>Also called spoofing, type of DNS attack that Replaces a legitimate IP address with an incorrect one.  As a result, when users enter a URL, they are connected with a fraudulent web site or resource.</Definition>
	</Entry>
	<Entry>
		<Term>Denial-of-Service DNS Attack</Term>
		<Definition>Type of DNS attack in which DNS servers are flooded with requests and responses, and cannot resolve legitimate requests. (See intentional crashing for related information.)</Definition>
	</Entry>
	<Entry>
		<Term>DES</Term>
		<Definition>Data Encryption Standard</Definition>
	</Entry>
	<Entry>
		<Term>Dig</Term>
		<Definition>Domain information groper, or dig, is a flexible tool for querying DNS name servers.</Definition>
	</Entry>
	<Entry>
		<Term>DKIM</Term>
		<Definition>Domain Keys Identified Mail</Definition>
	</Entry>
	<Entry>
		<Term>DNS</Term>
		<Definition>Domain Name System</Definition>
	</Entry>
	<Entry>
		<Term>DNSKEY</Term>
		<Definition>Domain Name System Key is one of four resource record types added by DNSSEC that carries the public key. (DNSSEC also added RRSIG, DS, and NSEC.)</Definition>
	</Entry>

	<Entry>
		<Term>DNSSEC</Term>
		<Definition>Domain Name System Security Extensions use signatures generated with a public/private key algorithm to verify data authenticity and integrity. </Definition>
	</Entry>
	<Entry>
		<Term>dnssec-keygen</Term>
		<Definition>When configuring TSIG between two servers, the command dnssec-key is used to generate the TSIG key for a pair.</Definition>
	</Entry>
	<Entry>
		<Term>DoD</Term>
		<Definition>Department of Defense</Definition>
	</Entry>
	<Entry>
		<Term>DoDD 8500.01E</Term>
		<Definition>Department of Defense Directive 8500.01E</Definition>
	</Entry>
	<Entry>
		<Term>DoDI 8500.2</Term>
		<Definition>Department of Defense Instruction 8500.2</Definition>
	</Entry>
	<Entry>
		<Term>Domain</Term>
		<Definition>Each branch of the domain name system hierarchy is either a domain or a sub-domain. Domains and sub-domains are relative. Any given domain is a child to the domain above it, and a parent to the sub-domains below it. </Definition>
	</Entry>
	<Entry>
		<Term>Domain Name</Term>
		<Definition>Unique name given to a domain or sub-domain of the DNS (e.g., irs.gov).</Definition>
	</Entry>
	<Entry>
		<Term>Domain Name System</Term>
		<Definition>The DNS is a database that maps fully qualified domain names, or FQDN's, to IP addresses, and vice-versa (maps IP addresses to FQDN's). The DNS also stores records that facilitate other applications, such as e-mail. Many applications, including databases, web-based applications, and Instant Messenger, rely on DNS services, including mail delivery agents such as sendmail. The DNS database is distributed among multiple servers, so that no single server contains the entire set of data. The information is stored on machines that are spread logically across the DNS and geographically across the world. This allows the massive DNS database to be decentralized.</Definition>
	</Entry>
	<Entry>
		<Term>DoS</Term>
		<Definition>Denial of Service</Definition>
	</Entry>
	<Entry>
		<Term>Double-Signing Rollover Method</Term>
		<Definition>Method used during the KSK overlap period to sign a zone, with both the KSK about to expire and the new KSK. (See pre-publish method for related information.)</Definition>
	</Entry>
	<Entry>
		<Term>Drill</Term>
		<Definition>A command line debugging tool</Definition>
	</Entry>
	<Entry>
		<Term>DS</Term>
		<Definition>One of four resource record types added by DNSSEC, Delegation Signer carries the signed hash of the key. (DNSSEC also added RRSIG, DNSKEY, and NSEC.)</Definition>
	</Entry>
	<Entry>
		<Term>DSA</Term>
		<Definition>An algorithm for generation of DNSSEC signatures using the Digital Signature Standard.  Although DSA is generally recommended for US Government use as a NIST standard, DSA is not commonly used for DNSSEC due to the amount of computer CPU time that is required to authenticate its signatures.</Definition>
	</Entry>
</Section>
<Section Letter="E">
	<Entry>
		<Term>EDNS0</Term>
		<Definition>Extension mechanisms for DNS (version zero)</Definition>
	</Entry>
	<Entry>
		<Term>ERS</Term>
		<Definition>Enterprise Recursive Service</Definition>
	</Entry>
	<Entry>
		<Term>Ethereal</Term>
		<Definition>GUI-based packet sniffing tool, now called Wireshark</Definition>
	</Entry>
</Section>
<Section Letter="F">
	<Entry>
		<Term>FDDI</Term>
		<Definition>Fiber Distributed Data Interface</Definition>
	</Entry>
	<Entry>
		<Term>FISMA</Term>
		<Definition>Federal Information Security Management Act of 2002</Definition>
	</Entry>
	<Entry>
		<Term>foundation DNS attacks</Term>
		<Definition>Type of DNS attack that targets the operating system of an authoritative server on which the DNS runs, and prevents the server from responding to requests effectively (See denial-of-service, cache-poisoning, packet interception, and data replacement or spoofing for related information.)</Definition>
	</Entry>
	<Entry>
		<Term>FQDN</Term>
		<Definition>Fully Qualified Domain Name</Definition>
	</Entry>
	<Entry>
		<Term>Fragmentation Offset</Term>
		<Definition>Value used to help reconstruct a fragmented packet</Definition>
	</Entry>
	<Entry>
		<Term>Fully Qualified Domain Name</Term>
		<Definition>A Fully Qualified Domain Name is the unambiguous name for a resource that specifies its exact location in the DNS hierarchy (for example, www.irs.gov), or a resource on a local network (for example, workstation1.example.com).</Definition>
	</Entry>
</Section>
<Section Letter="G">
	<Entry>
		<Term>$GENERATE</Term>
		<Definition>A BIND-specific directive used to create a series of resource records</Definition>
	</Entry>
</Section>
<Section Letter="H">
	<Entry>
		<Term>HINFO</Term>
		<Definition>Host Information</Definition>
	</Entry>
	<Entry>
		<Term>HMAC256</Term>
		<Definition>Hashed Message Authentication Code Message Digest 256</Definition>
	</Entry>
	<Entry>
		<Term>HMAC-MD5</Term>
		<Definition>Hashed Message Authentication Code Message Digest 5</Definition>
	</Entry>
</Section>
<Section Letter="I">
	<Entry>
		<Term>$INCLUDE</Term>
		<Definition>Any file identified by a $INCLUDE statement in a data file</Definition>
	</Entry>
	<Entry>
		<Term>IA</Term>
		<Definition>Information Assurance</Definition>
	</Entry>
	<Entry>
		<Term>IAM</Term>
		<Definition>Information Assurance Manager</Definition>
	</Entry>
	<Entry>
		<Term>IAO</Term>
		<Definition>Information Assurance Officer</Definition>
	</Entry>
	<Entry>
		<Term>ICMP</Term>
		<Definition>Internet Control Message Protocol</Definition>
	</Entry>
	<Entry>
		<Term>ID</Term>
		<Definition>Identification</Definition>
	</Entry>
	<Entry>
		<Term>IETF</Term>
		<Definition>Internet Engineering Task Force</Definition>
	</Entry>
	<Entry>
		<Term>IGMP</Term>
		<Definition>Internet Group Management Protocol</Definition>
	</Entry>
	<Entry>
		<Term>INCLUDE statement</Term>
		<Definition>Statement in the named.conf file used to break the named.conf file into more easily manageable chunks</Definition>
	</Entry>
	<Entry>
		<Term>Integrity</Term>
		<Definition>Verification that data being received is the same as the data that was published. (See authenticity for related information.)</Definition>
	</Entry>
	<Entry>
		<Term>Intentional Crashing DNS Attack</Term>
		<Definition>Type of DNS attack that Intercepts a DNS packet en route to a server and returns a response designed to crash the resolver.  This type of attack may be confused with a denial-of-service attack, since both prevent the name server from resolving the request.  However, intentional crashing attacks take advantage of bugs to crash resolvers, whereas denial-of-service attacks are generally brute-force attacks that overload the network with requests and responses. (See denial-of-service for related information.)</Definition>
	</Entry>
	<Entry>
		<Term>IP</Term>
		<Definition>Internet Protocol</Definition>
	</Entry>
	<Entry>
		<Term>IPv4</Term>
		<Definition>Current internet address protocol that consists of a series of four numbers from 0 to 255, representing 32 bits of address data (which is over 4.2 billion possible addresses).</Definition>
	</Entry>
	<Entry>
		<Term>IPv6</Term>
		<Definition>Newer internet address protocol that consists of eight sets of numbers representing 128 bits of address data, which is over 3.4 times 10 to the 38th power possible addresses.</Definition>
	</Entry>
	<Entry>
		<Term>ISSM</Term>
		<Definition>Information System Security Manager</Definition>
	</Entry>
	<Entry>
		<Term>ISSO</Term>
		<Definition>Information System Security Officer</Definition>
	</Entry>
</Section>
<Section Letter="J">
	<Entry>
		<Term>JWICS</Term>
		<Definition>Joint Worldwide Intelligence Communications System</Definition>
	</Entry>
</Section>
<Section Letter="K">

	<Entry>
		<Term>Key Effectivity Period</Term>
		<Definition>The key effectivity period is the time span during which a particular DNSSEC key is in effect. The keys themselves do not contain any information about their effectivity period-the effectivity period must be set and tracked by administrators based on policy.</Definition>
	</Entry>
	<Entry>
		<Term>KEY Statement</Term>
		<Definition>Statement in the named.conf file that specifies a key ID used for authentication and authorization on a particular name server</Definition>
	</Entry>
	<Entry>
		<Term>KMI</Term>
		<Definition>Key Management Infrastructure</Definition>
	</Entry>
	<Entry>
		<Term>KMP</Term>
		<Definition>Key Management Policy</Definition>
	</Entry>
	<Entry>
		<Term>KSK</Term>
		<Definition>Key Signing Keys are a type of DNSSEC key pair used to sign one or more zone signing keys (ZSKs) for a zone. KSKs normally have a relatively long effectivity period (several months to a year) than ZSKs.  The public part of a KSK pair can be configured as a Secure Entry Point to allow validation of keys and signatures in that zone and child zones.</Definition>
	</Entry>
</Section>
<Section Letter="L">
	<Entry>
		<Term>Leaf Node</Term>
		<Definition>The section at the end of a branch of the DNS hierarchy is referred to as a leaf node when it is a named device, such as a printer or computer.</Definition>
	</Entry>
	<Entry>
		<Term>LOGGING Statement</Term>
		<Definition>Statement in the named.conf file that specifies how the name server will log event information by using pre-defined or user-defined channels and associating categories of event information with those channels.</Definition>
	</Entry>
</Section>
<Section Letter="M">
	<Entry>
		<Term>+ multiline</Term>
		<Definition>Dig switch that structures the output of a dig so that it is easily readable.  As a bonus, the keyid will be printed as a comment behind the DNSKEY RRs.</Definition>
	</Entry>
</Section>
<Section Letter="N">
	<Entry>
		<Term>Name Chaining DNS Attack</Term>
		<Definition>Type of DNS attack that replaces the additional section of an intercepted packet with other information.  When the resolver receives the packet, it mistakenly accepts the improper information, and stores it in its cache.  As a result, the improper data can be propagated throughout the DNS whenever the resolver returns its response.</Definition>
	</Entry>
	<Entry>
		<Term>named.ca</Term>
		<Definition>A file that establishes the names of root servers and lists their addresses</Definition>
	</Entry>
	<Entry>
		<Term>named.conf configuration file</Term>
		<Definition>BIND-specific configuration file that defines whether a name server is a master (primary) or slave (secondary) for its delegated zones, or a cache-only server. This file defines the zone or zones for which the name server has authority, and specifies data files that provide zone data.  </Definition>
	</Entry>
	<Entry>
		<Term>named.local</Term>
		<Definition>A file that specifies the local loopback interface</Definition>
	</Entry>
	<Entry>
		<Term>NAT</Term>
		<Definition>Network Address Translation</Definition>
	</Entry>
	<Entry>
		<Term>NIPRNET</Term>
		<Definition>Non-secure Internet Protocol Router Network</Definition>
	</Entry>
	<Entry>
		<Term>NIST</Term>
		<Definition>National Institute of Standards and Technology</Definition>
	</Entry>
	<Entry>
		<Term>NS</Term>
		<Definition>Name Server</Definition>
	</Entry>
	<Entry>
		<Term>NSEC</Term>
		<Definition>One of four resource record types added by DNSSEC that signs any gaps to assure the non-existence of a resource or domain name. (DNSSEC also added RRSIG, DNSKEY, and DS.)</Definition>
	</Entry>
	<Entry>
		<Term>Nslookup</Term>
		<Definition>Tool for testing and troubleshooting DNS servers, which can be used non-interactively from the command line to issue simple queries, or interactively from a shell for more complex queries.</Definition>
	</Entry>
	<Entry>
		<Term>NTP</Term>
		<Definition>Network Time Protocol</Definition>
	</Entry>
	<Entry>
		<Term>NXDOMAIN</Term>
		<Definition>Error code indicating that a domain does not exist</Definition>
	</Entry>
</Section>
<Section Letter="O">
	<Entry>
		<Term>$ORIGIN</Term>
		<Definition>A command that changes the origin of a data file</Definition>
	</Entry>
	<Entry>
		<Term>Options statement</Term>
		<Definition>Statement in the named.conf file that controls global server configuration options and sets default values for other statements</Definition>
	</Entry>
	<Entry>
		<Term>OS</Term>
		<Definition>Operating System</Definition>
	</Entry>
</Section>
<Section Letter="P">
	<Entry>
		<Term>Packet</Term>
		<Definition>Any unit of data that is sent over the Internet, or any other packet switched network, between an origin and a destination. There are three main sections of a packet: a set of headers, the actual data being transmitted, and a footer.  </Definition>
	</Entry>

	<Entry>
		<Term>Packet Capture Tool</Term>
		<Definition>Tool that allows the complete capture of traffic that is traveling between networked computers. Generally used to capture the data being passed between clients and servers, and to analyze traffic on your network</Definition>
	</Entry>
	<Entry>
		<Term>Packet Interception DNS Attack</Term>
		<Definition>Type of DNS attack that intercepts queries in DNS packets between the sender and the destination.  </Definition>
	</Entry>

	<Entry>
		<Term>Packet-Sniffing Tool</Term>
		<Definition>Refer to packet capture tool</Definition>
	</Entry>
	<Entry>
		<Term>Path MTU</Term>
		<Definition>For any network path, there is a maximum transfer unit size, or MTU, that is derived from a combination of hardware capabilities, protocol limitations, and local configuration.  Any packet larger than this MTU size must be fragmented.  Common MTUs for LANs are on the order of 1500 bytes for conventional Ethernet or 9000 bytes for "jumbo" packets.  WANs often have much different constraints on their MTUs.</Definition>
	</Entry>
	<Entry>
		<Term>PKI</Term>
		<Definition>Public Key Infrastructure</Definition>
	</Entry>
	<Entry>
		<Term>POP</Term>
		<Definition>Post Office Protocol (Internet e-mail protocol)</Definition>
	</Entry>
	<Entry>
		<Term>Pre-Publish Method</Term>
		<Definition>Involves publishing a new ZSK prior to the actual rollover from the current ZSK. Method allows new keys to be pre-staged, cached, and available when older keys are no longer effective. (See double-signing rollover method for related information.)</Definition>
	</Entry>
	<Entry>
		<Term>Private key</Term>
		<Definition>Private keys are used to generate cryptographic signatures for zone data. In DNSSEC, pairs of public and private keys combine with data signature records (RRSIGs) and Delegation Signer (DS) records to establish a chain of trust down the DNS data hierarchy.</Definition>
	</Entry>
	<Entry>
		<Term>Protocol</Term>
		<Definition>Type of packet (for example, TCP, UDP, ICMP, IGMP)</Definition>
	</Entry>
	<Entry>
		<Term>PTR</Term>
		<Definition>Pointer (as used in DNS records)</Definition>
	</Entry>
	<Entry>
		<Term>Public key</Term>
		<Definition>Public keys are published within zones. In DNSSEC, pairs of public and private keys combine with data signature records (RRSIGs) and Delegation Signer (DS) records to establish a chain of trust down the DNS data hierarchy.</Definition>
	</Entry>
</Section>
<Section Letter="Q">
	<Entry>
		<Term>Query</Term>
		<Definition>A request for information by a client, such as "What is the IP address for this FQDN?" or "What is the FQDN for this IP address?"</Definition>
	</Entry>
</Section>
<Section Letter="R">
	<Entry>
		<Term>Recursive server</Term>
		<Definition>Recursive servers are often non-authoritative servers, and are used to relay requests from clients to authoritative servers to fully resolve the request. In addition, recursive servers often keep a copy of, or cache, of the answer from the authoritative server, in case another client makes the same request.</Definition>
	</Entry>
	<Entry>
		<Term>resolv.conf</Term>
		<Definition>A resolver file</Definition>
	</Entry>
	<Entry>
		<Term>RR</Term>
		<Definition>Resource Record</Definition>
	</Entry>
	<Entry>
		<Term>RRSIG</Term>
		<Definition>One of four resource record types added by DNSSEC, the RRSIG carries the signature of the DNS information being sent. (DNSSEC also added DNSKEY, DS, and NSEC.)</Definition>
	</Entry>
	<Entry>
		<Term>RSA</Term>
		<Definition>An algorithm for public key encryption, named for its inventors (Rivest, Shamir, Adleman)</Definition>
	</Entry>
	<Entry>
		<Term>RSAMD5</Term>
		<Definition>An algorithm for generation of DNSSEC signatures using the RSA public-private algorithm and the MD5 hash algorithm. Previously used as the primary recommended algorithm for DNSSEC, but has been deprecated due to concerns about the vulnerability of MD5 to cryptographic attacks</Definition>
	</Entry>
	<Entry>
		<Term>RSASHA-1</Term>
		<Definition>An algorithm for generation of DNSSEC signatures using the RSA public-private algorithm and the SHA-1 hash algorithm. Currently, RSASHA-1 is recommended for DoD usage, because it provides the best combination of interoperability and security. Other supported algorithms include RSAMD5 and DSA.  </Definition>
	</Entry>
</Section>
<Section Letter="S">
	<Entry>
		<Term>+sigchase</Term>
		<Definition>Dig switch that traces the signature chain.  You will also need to have a ./trusted-keys.keys or /etc/trusted-keys.keys available that contains trusted key entries.  The trusted-keys.keys file, or another file of a similar name, is used to store Secure Entry Point keys (that is, trust anchors), which can be used by dig and other DNSSEC-aware interactive tools.  These files can also be included in the named.conf file for a recursive DNSSEC-aware DNS server/resolver.</Definition>
	</Entry>
	<Entry>
		<Term>-S</Term>
		<Definition>Debugging option provided by drill to the signatures from the leaf node back to the root, looking for the relevant records</Definition>
	</Entry>
	<Entry>
		<Term>SA</Term>
		<Definition>System Administrator</Definition>
	</Entry>
	<Entry>
		<Term>SEP</Term>
		<Definition>secure entry point</Definition>
	</Entry>
	<Entry>
		<Term>SERVER statement</Term>
		<Definition>Statement in the named.conf file that specifies the behavior of the server when accessing or responding to the defined remote server</Definition>
	</Entry>
	<Entry>
		<Term>SHA</Term>
		<Definition>Secure Hash Algorithm</Definition>
	</Entry>
	<Entry>
		<Term>shared.keys</Term>
		<Definition>Example of a recommended file for maintaining a list of secret keys when configuring for TSIG. For security purposes, it is recommended to maintain a list of secret keys in a file other than named.conf, such as /etc/bind/shared.keys.</Definition>
	</Entry>
	<Entry>
		<Term>Signature Validity Period</Term>
		<Definition>The signature validity period is the time span during which the signature or RRSIG corresponding to a particular resource record is valid.</Definition>
	</Entry>
	<Entry>
		<Term>Sinkhole</Term>
		<Definition>Sinkholing of DNS traffic implies redirecting the traffic to a system that is configured to act in place of the botnet controller.  This requires reverse engineering of the malware, but allows computer network defense personnel to use the malware's own tools to track infections.</Definition>
	</Entry>
	<Entry>
		<Term>SIPRNET</Term>
		<Definition>Secret Internet Protocol Router Network</Definition>
	</Entry>
	<Entry>
		<Term>SOA</Term>
		<Definition>Start of Authority</Definition>
	</Entry>
	<Entry>
		<Term>SP</Term>
		<Definition>Special Publication</Definition>
	</Entry>
	<Entry>
		<Term>Source Address</Term>
		<Definition>IP address of where a DNS packet originated</Definition>
	</Entry>
	<Entry>
		<Term>Spoofing</Term>
		<Definition>Type of DNS attack, also called data replacement, that replaces a legitimate IP address with an incorrect one.  As a result, when users enter a URL, they are connected with a fraudulent web site or resource. </Definition>
	</Entry>
	<Entry>
		<Term>SRC</Term>
		<Definition>Source (tcpdump abbreviation)</Definition>
	</Entry>
	<Entry>
		<Term>SRV</Term>
		<Definition>Service recource record</Definition>
	</Entry>
	<Entry>
		<Term>SRVFAIL</Term>
		<Definition>Serve fail error</Definition>
	</Entry>

	<Entry>
		<Term>STIG</Term>
		<Definition>Security Technical Implementation Guides</Definition>
	</Entry>
	<Entry>
		<Term>Syslog</Term>
		<Definition>System log</Definition>
	</Entry>
	<Entry>
		<Term>Systems Administrators</Term>
		<Definition>Systems administrators are the people who configure, operate, maintain, and troubleshoot the hardware and software components of the DNS.</Definition>
	</Entry>
</Section>
<Section Letter="T">
	<Entry>
		<Term>+ trace</Term>
		<Definition>Dig switch that traces a delegation chain.  This option may be helpful if you are trying to figure out where the delegation points are.</Definition>
	</Entry>
	<Entry>
		<Term>-T</Term>
		<Definition>Debugging option provided by drill to follow the chain of trust from the root to the leaves. Indicates the security status</Definition>
	</Entry>
	<Entry>
		<Term>TASO</Term>
		<Definition>Terminal Area Security Officer</Definition>
	</Entry>
	<Entry>
		<Term>TCP/IP</Term>
		<Definition>Transmission Control Protocol/Internet Protocol</Definition>
	</Entry>
	<Entry>
		<Term>tcpdump</Term>
		<Definition>Utility that is a command-line tool for collecting and dumping data on TCP/IP networks. Most Linux distributions come with tcpdump installed by default. </Definition>
	</Entry>
	<Entry>
		<Term>Time to Live</Term>
		<Definition>The time to live, or TTL, is the time span during which a resolver is encouraged to cache DNS data.</Definition>
	</Entry>
	<Entry>
		<Term>Transaction Authentication</Term>
		<Definition>(see TSIG)</Definition>
	</Entry>
	<Entry>
		<Term>Transaction Signature</Term>
		<Definition>(see TSIG)</Definition>
	</Entry>
	<Entry>
		<Term>Trust anchor</Term>
		<Definition>Trust anchors are public keys that are configured into the DNS resolvers to validate the signatures of incoming data. Since zones may have multiple keys, a zone administrator designates certain keys to serve as a trust anchor for a resolver.  Normally, the public half of a KSK pair is designated as the trust anchor. These trust anchors are called the Secure Entry Point keys.</Definition>
	</Entry>
	<Entry>
		<Term>TSIG</Term>
		<Definition>Transaction Signature or transaction authentication, which enables point-to-point security usually on a network. </Definition>
	</Entry>

	<Entry>
		<Term>TTL</Term>
		<Definition>Time To Live</Definition>
	</Entry>
	<Entry>
		<Term>TXT</Term>
		<Definition>Text</Definition>
	</Entry>
</Section>
<Section Letter="U">
	<Entry>
		<Term>UDP</Term>
		<Definition>User Datagram Protocol</Definition>
	</Entry>
	<Entry>
		<Term>UEM</Term>
		<Definition>DNS User Experience Monitor (UEM) </Definition>
	</Entry>
	<Entry>
		<Term>URL</Term>
		<Definition>Uniform Resource Locator is a unique and uniform way to locate a resource, such as a file or a device, on the Internet or other network.</Definition>
	</Entry>
	<Entry>
		<Term>US COMSEC</Term>
		<Definition>United States Communications Security</Definition>
	</Entry>
</Section>
<Section Letter="W">
	<Entry>
		<Term>WINS</Term>
		<Definition>Windows Internet Naming Service</Definition>
	</Entry>
	<Entry>
		<Term>Wireshark</Term>
		<Definition>Formerly known as Ethereal, this GUI-based packet-capture tool performs many of the same tasks as tcpdump. </Definition>
	</Entry>
</Section>
<Section Letter="X">
	<Entry>
		<Term>\X</Term>
		<Definition>Indicates that a character's special meaning does not apply</Definition>
	</Entry>
</Section>
<Section Letter="Z">
	<Entry>
		<Term>ZONE statement</Term>
		<Definition>Statement in the named.conf file that defines a zone for which a server is authoritative, and applies options to describe how the zone functions</Definition>
	</Entry>
	<Entry>
		<Term>ZSK</Term>
		<Definition>Zone Signing Keys are a type of DNSSEC key pair used to sign data or records in a zone. ZSKs are used more often than KSKs to sign more data, and so are more susceptible to certain cryptographic-cracking attacks than KSKs.  ZSKs normally have a shorter effectivity period (weeks or a month).</Definition>
	</Entry>
</Section>
</Glossary>
