felix/master_thesis
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

updated tex

Browse Source
This commit is contained in:
Felix Steghofer
2017-11-28 11:07:41 +01:00
parent fdf54ae7e0
commit 42fce4f17c
16 changed files with 208 additions and 44 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
Thesis/content/Technical_Background/DNS/DNS.tex
View File

@@ -1,4 +1,4 @@
\section{\glsentrytext{dns}}
\section{Domain Name System}
\label{sec:DNS}
The \gls{dns} is one of the cornerstone of the internet as it is known today. \todo{statistic about usage}. Initial designs have been proposed in 1983 and evolved over the following four years into the first globally adapted standard RFC 1034 \fsCite{rfc1034} (RFC 1035 for implementation and specification details \fsCite{rfc1035}). The main idea of the \gls{dns} is translating human readable domain names to network addresses. There are many extensions to the initial design including many security related features and enhancements or the support for \gls{ipv6} in 1995.
@@ -41,22 +41,23 @@ The \gls{dns} is based on a naming system that consists of a hierarchical and lo
\subsubsection{\gls{dns} Resource Records}
\label{subsubsec:dns_resource_records}
TODO blabla
\todo{TODO}
\begin{table}[]
\centering
\caption{Common \gls{dns} Resource Record}
\label{tab:dns_resource_record}
\begin{tabular}{@{}cccc@{}}
Value & Text Code & Type & Description \\
1 & A & Address & Returns the 32 bit IPv4 address of a host. Most commonly used for name resolution of a host. \\
28 & AAAA & IPv6 address & Similar to the A record, this returns the address of an host. For IPv6 this has 128 bit. \\
2 & NS & \begin{tabular}[c]{@{}c@{}}Name\\ Server\end{tabular} & \begin{tabular}[c]{@{}c@{}}Specifies the name of a DNS name server that is authoritative for the zone.\\ Each zone must have at least one NS record that points to its primary name server.\end{tabular} \\
5 & CNAME & \begin{tabular}[c]{@{}c@{}}Canonical\\ Name\end{tabular} & \begin{tabular}[c]{@{}c@{}}The CNAME records allows to define aliases that point to the real canonical name of the node. \\ This can e.g. be used to hide internal \gls{dns} structures and provide a stable interface for outside users.\end{tabular} \\
6 & SOA & \begin{tabular}[c]{@{}c@{}}Start of\\ Authority\end{tabular} & \begin{tabular}[c]{@{}c@{}}The SOA record marks the start of a \gls{dns} zone and provides important information about the zone.\\ Every zone must have exactly one SOA records containing e.g. name of the zone, primary authoritative server name\\ and the administration email address.\end{tabular} \\
12 & PTR & Pointer & Provides a pointer to a different record in the name space. \\
15 & MX & Mail Exchange & Returns the host that is responsible for handling emails sent to this domain. \\
16 & TXT & Text String & Record which allows arbitrary additional texts to be stored that are related to the domain.
\caption{Resource Record Types}
\label{tab:resource_record_types}
\begin{tabular}{@{}llll@{}}
\toprule
Value & Text Code & Type & Description \\ \midrule
1 & A & Address & \begin{tabular}[c]{@{}l@{}}Returns the 32 bit IPv4 address of a host. \\ Most commonly used for name resolution \\ of a host.\end{tabular} \\
28 & AAAA & IPv6 address & \begin{tabular}[c]{@{}l@{}}Similar to the A record, this returns the \\ address of an host. For IPv6 this has 128 bit.\end{tabular} \\
2 & NS & \begin{tabular}[c]{@{}l@{}}Name\\ Server\end{tabular} & \begin{tabular}[c]{@{}l@{}}Specifies the name of a \gls{dns} name server \\ that is authoritative for the zone. Each \\ zone must have at least one NS record \\ that points to its primary name server.\end{tabular} \\
5 & CNAME & \begin{tabular}[c]{@{}l@{}}Canonical\\ Name\end{tabular} & \begin{tabular}[c]{@{}l@{}}The CNAME records allows to define \\ aliases that point to the real canonical \\ name of the node. This can e.g. be used\\ to hide internal \gls{dns} structures and \\ provide a stable interface for outside users.\end{tabular} \\
6 & SOA & \begin{tabular}[c]{@{}l@{}}Start of\\ Authority\end{tabular} & \begin{tabular}[c]{@{}l@{}}The SOA record marks the start of a \gls{dns} \\ zone and provides important information \\ about the zone. Every zone must have \\ exactly one SOA records containing \\ e.g. name of the zone, primary \\ authoritative server name and the \\ administration email address.\end{tabular} \\
12 & PTR & Pointer & \begin{tabular}[c]{@{}l@{}}Provides a pointer to a different record\\ in the name space.\end{tabular} \\
15 & MX & Mail Exchange & \begin{tabular}[c]{@{}l@{}}Returns the host that is responsible for\\ handling emails sent to this domain.\end{tabular} \\
16 & TXT & Text String & \begin{tabular}[c]{@{}l@{}}Record which allows arbitrary \\ additional texts to be stored that are\\ related to the domain.\end{tabular} \\ \bottomrule
\end{tabular}
\end{table}
@@ -186,10 +187,10 @@ Table~\ref{tab:message_header} shows the template of a \gls{dns} message header.
\begin{itemize}
\item \textbf{Question Name:} Contains a variably sized payload payload including the domain, zone name or general object that is subject of the query. Encoded using standard \gls{dns} name notation.
\item \textbf{Question Name:} Contains a variably sized payload payload including the domain, zone name or general object that is subject of the query. Encoded using standard \gls{dns} name notation. Depending on the Question Type, for example requesting an A Record will typically require an host part, such as www.domain.tld. A MX query will usually only contain a base domain name (domain.tld).
\todo{\url{http://www.tcpipguide.com/free/t_DNSNameNotationandMessageCompressionTechnique.htm}}
\item \textbf{Question Type:} Specifies the type of question being asked. This field may contain a code number corresponding to a particular type of resource being requested, see Table~\ref{tab:dns_resource_record} for common resource types. TODO more blabla, the following special values blabla
\item \textbf{Question Type:} Specifies the type of question being asked. This field may contain a code number corresponding to a particular type of resource being requested, see Table~\ref{tab:resource_record_types} for common resource types. TODO continue here (special values)
\item \textbf{Question Class} \todo{TODO}
\end{itemize}
@@ -222,19 +223,20 @@ QType & Type & Description \\
\subsection{Domain Names}
\label{subsec:domain_names}
\todo{TODO structure of a domain, etc.}
\subsection{Resolution}
\label{subsec:resolution}
\subsubsection{Recursive}
\label{subsubsec:recursive}
\label{TODO subsubsec:recursive}
\begin{figure}[htbp]
\begin{figure}[!htbp]
\centering
\includegraphics[scale=.5, clip=true]{content/Technical_Background/DNS/DNS_address-resolution.pdf}
\caption{Address Resolution}
\label{fig:address_resolution}
\end{figure}
\todo{not referenced atm}