Cloud Services

This is an old revision of the document!

---

Her følger de mest vanlige pekerne for DNS:

A Brukes til å peke domenet til en webside. Legges inn både med og uten www.
CNAME Brukes til å peke til et alias.
MX Brukes til å peke på ønsket mailserver.
SRV Brukes til å peke på tjenester på et domene, eks Lync.
TXT og SPF Brukes på et domene for å angi servere som får lov til å sende på vegne av maildomenet. Legges inn i DNS for å forhindre spam/spoofing av epost. Best practices er å legge til både TXT og SPF.
PTR Revers oppslag,dvs fra IP til navn.

Tabell:

Type	Defining RFC	Description	Function
A	RFC 1035[1]	Address record	Returns a 32-bit IPv4 address, most commonly used to map hostnames to an IP address of the host, but also used for DNSBLs, storing subnet masks in RFC 1101, etc.
AAAA	RFC 3596[2]	IPv6 address record	Returns a 128-bit IPv6 address, most commonly used to map hostnames to an IP address of the host.
CNAME	RFC 1035[1]	Canonical name record	Alias of one name to another: the DNS lookup will continue by retrying the lookup with the new name.
MX	RFC 1035[1]	Mail exchange record	Maps a domain name to a list of message transfer agents for that domain
NS	RFC 1035[1]	Name server record	Delegates a DNS zone to use the given authoritative name servers
PTR	RFC 1035[1]	Pointer record	Pointer to a canonical name. Unlike a CNAME, DNS processing does NOT proceed, just the name is returned. The most common use is for implementing reverse DNS lookups, but other uses include such things as DNS-SD.
SOA	RFC 1035[1] and RFC 2308[9]	Start of [a zone of] authority record	Specifies authoritative information about a DNS zone, including the primary name server, the email of the domain administrator, the domain serial number, and several timers relating to refreshing the zone.
SPF	RFC 4408	Sender Policy Framework	Specified as part of the SPF protocol as an alternative to storing SPF data in TXT records, using the same format. It was later found that the majority of SPF deployments lack proper support for this record type, and support for it was discontinued.
SRV	RFC 2782	Service locator	Generalized service location record, used for newer protocols instead of creating protocol-specific records such as MX.
TXT	RFC 1035[1]	Text record	Originally for arbitrary human-readable text in a DNS record. Since the early 1990s, however, this record more often carries machine-readable data, such as specified by RFC 1464, opportunistic encryption, Sender Policy Framework, DKIM, DMARC, DNS-SD, etc.