summaryrefslogtreecommitdiff
path: root/README.SrvRecords
diff options
context:
space:
mode:
authorMichael Vogt <mvo@debian.org>2016-01-05 20:48:56 +0100
committerMichael Vogt <mvo@debian.org>2016-01-05 20:48:56 +0100
commitca5cbc96a5a297fb41c973c93f2089ac058a08eb (patch)
tree0e0de7996003cd2ca96720f59756aed139f4a68b /README.SrvRecords
parent5ef35b188f3f35ab948da87e78bc6255ebf9d658 (diff)
Add documentation about the SrvRecords support in apt
Git-Dch: ignore
Diffstat (limited to 'README.SrvRecords')
-rw-r--r--README.SrvRecords22
1 files changed, 22 insertions, 0 deletions
diff --git a/README.SrvRecords b/README.SrvRecords
new file mode 100644
index 000000000..2ba7ff52e
--- /dev/null
+++ b/README.SrvRecords
@@ -0,0 +1,22 @@
+DNS SRV record support in apt
+=============================
+
+Apt supports a subset of the DNS SRV server records protocol as
+described in RFC 2782 for service discovery.
+
+Before connecting to the requested server APT will send a SRV
+record request of the form "_$protocol._tcp._$host", e.g.
+"_http._tcp.ftp.debian.org" or "_http._tcp.security.debian.org".
+
+If the server sends SRV records
+as a reply APT will use those to connect to the server(s) in
+this reply. It will honor the "priority" field in the reply.
+
+However it does not implement the "weight" alogrithm as described
+in RFC 2782. It will use an equal weight for each server of the
+same priority.
+
+If connecting to a server fails APT will retry with the next one
+and remove the server from the list of valid servers for this
+session.
+