From 113d455c70a0aa5cebb1f51d1ecaca70fdd2c211 Mon Sep 17 00:00:00 2001 From: Jeremy Stanley Date: Mon, 9 Apr 2018 21:56:05 +0000 Subject: [PATCH] Note missing AAAA records for AFS servers Document why we don't maintain AAAA resource records in DNS for our OpenAFS servers. Change-Id: Ib295e79b32af43f26782e4277464bd130f4318e4 --- doc/source/afs.rst | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/doc/source/afs.rst b/doc/source/afs.rst index 81a402d5cf..5456cbe1f9 100644 --- a/doc/source/afs.rst +++ b/doc/source/afs.rst @@ -547,4 +547,8 @@ AFS uses the following DNS entries:: _afs3-vlserver._udp.openstack.org. 300 IN SRV 10 10 7003 afsdb01.openstack.org. _afs3-vlserver._udp.openstack.org. 300 IN SRV 10 10 7003 afsdb02.openstack.org. -Be sure to update them if volume location and PTS servers change. +Be sure to update them if volume location and PTS servers change. Also note +that only A (IPv4 address) records are used in the SRV data. Since OpenAFS +lacks support for IPv6, avoid entering corresponding AAAA (IPv6 address) +records for these so that it won't cause fallback delays for other +v6-supporting AFS client implementations.