In our constant efforts to provide the best service, our DNS records system now support 2 more DNS records: AFSDB and KEY record,
adding to our existing A, AAAA, CNAME, MX, HINFO, SRV, TXT, SPF records and web redirect records.
If you haven't heard about AFSDB and KEY records yet, here's a quick explanation:
AFSDB record explained
AFSDB records give information about either the location of an AFS cell database server (subtype 1)
or of a DCE cell's authenticated name server (subtype 2).
It specifies which style of distributed service is provided with the given hostname.
An AFS cell database server runs the process that tracks the location of groups of files on various AFS fileservers within a cell.
Locating the AFS cell database server is essential to locate files in the cell.
The DCE Naming service uses the DNS to map from the domain name of a cell to authenticated name servers for that cell.
AFSDB record has a similar format as MX records.
Say a test.com systems administrator developed a DCE cell to use distributed processing to load graphics faster.
He runs a DCE name server on bigbird.test.com, two AFS cell database servers on green.test.com and orange.test.com.
The following setup need to be configured:
test.com. AFSDB 1 green.test.com.
test.com. AFSDB 1 orange.test.com.
test.com. AFSDB 2 bigbird.test.com.
KEY record explained
In DNSSEC, each zone has a public/private key pair.
A DNSKEY record holds a public key that is used in the DNSSEC authentication process to verify DNSSEC signatures in RRSIG records.
DNSSEC uses public key cryptography to sign DNS record sets.
When a record with DDSSEC records is received by a security-aware resolver,
the public key must also be sent in order for the signatures of each record set to be verified.
These two DNS records are provided for free for top level domain names (yourdomain.com).
If you have any questions or comments, feel free to contact us or comment!
DNS records now supports ...