On 08/28/2009 05:11 PM, Matt Domsch wrote:
From: Matt Domsch<mdomsch@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
---
modules/bind/files/master/fedoraproject.org | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/modules/bind/files/master/fedoraproject.org b/modules/bind/files/master/fedoraproject.org
index 2327080..14eb8c3 100644
--- a/modules/bind/files/master/fedoraproject.org
+++ b/modules/bind/files/master/fedoraproject.org
@@ -168,8 +168,9 @@ posse8 IN A 209.132.178.18
posse9 IN A 209.132.178.20
proxy3 IN A 66.35.62.162
proxy4 IN A 152.46.7.221
-proxy4 IN AAAA 2610:28:200:1:216:3eff:fe62:9fdd
+proxy4 IN AAAA 2610:28:200:1::fed0:1
proxy4-2 IN A 152.46.7.222
+proxy4-2 IN AAAA 2610:28:200:1::fed0:2
proxy5 IN A 80.239.156.214
publictest1 IN A 152.46.7.227
publictest2 IN A 152.46.7.228
Tangential issue...
How are IPv6 addresses assigned to proxy4[-2] ?
If they are statically set on the machine, all good.
If they are assigned via radvd or DHCPv6, you might want to consider
some setup where the machine's IPv6 address is proactively pushed to the
DNS servers. One method is nsupdate + TSIG, which is pretty easy to set
up on a fine-grained basis (ie. give a DNS key DNS update perms for
_only_ the proxy4 AAAA addresses).
Otherwise, the dynamically-assigned IPv6 address on the host may not
match the IPv6 address in DNS.
Jeff
_______________________________________________
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
