DNS Fields
Different DNS fields can disclose information to attackers. For example, any host listed in the MX field runs a mail server on port 25/TCP. Similarly, hosts listed in the NS field run DNS servers. Although less common today, the HINFO field is intended to store host information. This may include operating system, architecture, or contact information. Finally, the TXT field is used for generic comments. This information may provide additional insight for an attacker.
Information Hiding
Each piece of DNS information is associated with a 2-byte type field. NS, MX, and TXT are three of the 65,536 possible values (they are 2, 15, and 16, respectively) [RFC1035]. Because new types may be defined in the future, many DNS servers permit caching unknown field types. These undefined fields can be used to store covert information-only clients that know to ask for the information will receive it.
In this tutorial:
- Domain Name System (DNS)
- DNS Common Uses
- Hostname-to-Address Mapping
- Common Lookup Tools
- Naming Confusion Attack Vectors
- Dotted Names
- Name Formatting
- Exploited Anonymity
- Mail Servers
- Sender Policy Framework Overloading
- Domain Keys Overloading
- DNS Protocol
- Packet Information
- Simple DNS Server
- Distributed Architecture
- Top Level Domain Servers
- Generic Top Level Domain (gTLD)
- Secondary Level Domain (SLD)
- Primary and Secondary Servers
- Caching Servers
- DNS Management
- DNS Direct Risks
- DNS Performance versus Security
- DNS Cache Poisoning
- Corrupt DNS Packets
- DNS Domain Hijacking
- DNS Server Hijacking
- Dynamic DNS
- Similar Hostnames
- Domain Renewals
- Hostnames
- Zone Transfers
- Host Listing
- DNS Fields
- Mitgation Option
- Technical Threat Mitigation
- Social Threat Mitigation
- Defining Trusted Replies