.\" Man page generated from reStructuredText.
.
.TH "SPLITDNS.CONFIG" "5" "Mar 08, 2019" "7.1" "Apache Traffic Server"
.SH NAME
splitdns.config \- Traffic Server split DNS configuration file
.
.nr rst2man-indent-level 0
.
.de1 rstReportMargin
\\$1 \\n[an-margin]
level \\n[rst2man-indent-level]
level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
-
\\n[rst2man-indent0]
\\n[rst2man-indent1]
\\n[rst2man-indent2]
..
.de1 INDENT
.\" .rstReportMargin pre:
. RS \\$1
. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
. nr rst2man-indent-level +1
.\" .rstReportMargin post:
..
.de UNINDENT
. RE
.\" indent \\n[an-margin]
.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
.nr rst2man-indent-level -1
.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
..
.sp
The \fI\%splitdns.config\fP file enables you to specify the DNS server that
Traffic Server should use for resolving hosts under specific conditions.
For more information, refer to admin\-split\-dns\&.
.sp
To specify a DNS server, you must supply the following information in
each active line within the file:
.INDENT 0.0
.IP \(bu 2
A primary destination specifier in the form of a destination domain,
a destination host, or a URL regular expression
.IP \(bu 2
A set of server directives, listing one or more DNS servers with
corresponding port numbers
.UNINDENT
.sp
You can also include the following optional information with each DNS
server specification:
.INDENT 0.0
.IP \(bu 2
A default domain for resolving hosts
.IP \(bu 2
A search list specifying the domain search order when multiple
domains are specified
.UNINDENT
.sp
After you modify the \fI\%splitdns.config\fP file,
run the \fBtraffic_ctl config reload\fP
command to apply the changes. When you apply changes to a node in a
cluster, Traffic Server automatically applies the changes to all other
nodes in the cluster.
.SH FORMAT
.sp
Each line in the \fI\%splitdns.config\fP file uses one of the following
formats:
.INDENT 0.0
.INDENT 3.5
.sp
.nf
.ft C
dest_domain=dest_domain | dest_host | url_regex named=dns_server def_domain=def_domain search_list=search_list
.ft P
.fi
.UNINDENT
.UNINDENT
.sp
The following list describes each field.
.INDENT 0.0
.TP
.B \fBdest_domain\fP
A valid domain name. This specifies that DNS server selection will
be based on the destination domain. You can prefix the domain with
an exclamation mark (\fB!\fP) to indicate the NOT logical operator.
.UNINDENT
.INDENT 0.0
.TP
.B \fBdest_host\fP
A valid hostname. This specifies that DNS server selection will be
based on the destination host. You can prefix the host with an
exclamation mark (\fB!\fP) to indicate the \fBNOT\fP logical operator.
.UNINDENT
.INDENT 0.0
.TP
.B \fBurl_regex\fP
A valid URL regular expression. This specifies that DNS server
selection will be based on a regular expression.
.UNINDENT
.INDENT 0.0
.TP
.B \fBnamed\fP
This is a required directive. It identifies the DNS server that
Traffic Server should use with the given destination specifier. You
can specify a port using a colon (\fB:\fP). If you do not specify a
port, then 53 is used. Specify multiple DNS servers with spaces or
semicolons (\fB;\fP) as separators.
.sp
You must specify the domains with IP addresses in CIDR ("dot")
notation.
.UNINDENT
.INDENT 0.0
.TP
.B \fBdef_domain\fP
A valid domain name. This optional directive specifies the default
domain name to use for resolving hosts. Only one entry is allowed.
If you do not provide the default domain, the system determines its
value from \fB/etc/resolv.conf\fP
.UNINDENT
.INDENT 0.0
.TP
.B \fBsearch_list\fP
A list of domains separated by spaces or semicolons (;). This
specifies the domain search order. If you do not provide the search
list, the system determines the value from \fBresolv.conf(5)\fP
.UNINDENT
.SH EXAMPLES
.sp
Consider the following DNS server selection specifications:
.INDENT 0.0
.INDENT 3.5
.sp
.nf
.ft C
dest_domain=internal.company.com named=255.255.255.255:212 255.255.255.254 def_domain=company.com search_list=company.com company1.com
dest_domain=!internal.company.com named=255.255.255.253
.ft P
.fi
.UNINDENT
.UNINDENT
.sp
Now consider the following two requests:
.INDENT 0.0
.INDENT 3.5
.sp
.nf
.ft C
http://minstar.internal.company.com
.ft P
.fi
.UNINDENT
.UNINDENT
.sp
This request matches the first line and therefore selects DNS server
\fB255.255.255.255\fP on port \fB212\fP\&. All resolver requests use
\fBcompany.com\fP as the default domain, and \fBcompany.com\fP and
\fBcompany1.com\fP as the set of domains to search first.
.INDENT 0.0
.INDENT 3.5
.sp
.nf
.ft C
http://www.microsoft.com
.ft P
.fi
.UNINDENT
.UNINDENT
.sp
This request matches the second line. Therefore, Traffic Server selects
DNS server \fB255.255.255.253\fP\&. Because no \fBdef_domain\fP or
\fBsearch_list\fP was supplied, Traffic Server retrieves this information
from \fBresolv.conf(5)\fP
.SH COPYRIGHT
2019, dev@trafficserver.apache.org
.\" Generated by docutils manpage writer.
.