Summary
A TXT (Text) Entry was created with human-readable text in mind. These dynamic records can be used for a variety of things.
Frequently, TXT records are utilized for Google Verification.
The record 'pointers to' the TXT Value, although no traffic is directed by these records. Instead, they are employed to supply vital data to outside sources.
The first record is used for SPF, or Sender Policy Framework, data. Many email systems use these records to determine whether an email is coming from a reliable source and to filter out spam and messages that are spoofing your domain (a practice known as spoofing).
DomainKeys, which is also used to confirm that email came from a reliable source, uses the second record.
DNS Glossary
Zone File: This is where a domain's DNS records are kept, according to the DNS glossary.
Host Record: The domain or subdomain you want to utilise is listed in the host record. The root domain itself is denoted by the @ sign. In our illustration, the Host Record 'ftp' would be for the subdomain ftp.google.com and '@' would be the actual domain name google.com.
Points To: This is the server that the domain or subdomain is sending traffic to, as indicated by the pointing arrow.
TTL: The 'time to live' number describes how long a DNS server, such as your Internet service provider, will keep a record in its cache. The default value is 14400 seconds, which is the smallest acceptable amount. Normally, there is no need to change this value.
Action: You can edit or delete existing records with this.
Weight: This regulates the use of several records in a manner similar to priority. Records that share the same Priority value are grouped together. Lower numbers are used before larger numbers, much like with MX Entries.
Port: The server or computer uses this port to process traffic to particular services, ensuring that all traffic enters the correct door.
Target: The location to which the record is sending traffic. This record would transmit data over port 5060 from service.example.com to listerning.otherexample.com. The use of SRV records typically requires expert server management skills.
