Summary: | geo.freebsd.org domain has no ipv6 nameservers | ||
---|---|---|---|
Product: | Services | Reporter: | Måns Nilsson <mansaxel> |
Component: | Core Infrastructure | Assignee: | Philip Paeps <philip> |
Status: | Closed FIXED | ||
Severity: | Affects Some People | CC: | 2khramtsov, clusteradm, crest, mansaxel, philip |
Priority: | --- | ||
Version: | unspecified | ||
Hardware: | Any | ||
OS: | Any | ||
Bug Depends on: | |||
Bug Blocks: | 229538 |
Description
Måns Nilsson
2021-04-04 07:29:57 UTC
Looks like gdnsd is not listening on IPv6. I'll try to figure out why. This is probably not intentional. Trying to enable IPv6 support breaks with: # fatal: Failed to bind() UDP DNS socket to [::]:53 I'll need to look into this in more detail when I have a little more brainspace. Assign this bug to me. Keep clusteradm in Cc:. Good that there is work going on! Please remember that there need to be AAAA glue records in freebsd.org as well as AAAA records in geo.freebsd.org. /Måns, former ccTLD DNS admin. Thanks for the reminder. :) We actually have commented out glue records in the FreeBSD.org zone already. As soon as I can convince gdnsd to listen on IPv6, I'll uncomment those. I hope to get around to this somewhen this week ... but no promises. (In reply to Philip Paeps from comment #4) I had a similar problem with a jail not wanting to bind to IPv6 address. If you have things like: ip6.addr = "2001:db8:2:10f::f/64" then you may want to do net.inet6.ip6.dad_count=0 on a host. I initially found this here: https://forums.freebsd.org/threads/iocage-ipv6-jail-network-services-cant-bind-to-address.52096/ I just took a look at gdnsd, since the problem seems to remain. There are fixes in gdnsd 3.5.1 for what looks to be exactly this issue. I can't tell which version is on gns[12].freebsd.org, but I can see that 3.5.1 is in ports. Maybe a update is what it takes. Oh! That does look interesting. I'll see if I can upgrade the gns[12].freebsd.org machines and whether the IPv6 support works for us. Thanks for the pointer (and for keeping our feet close to the fire)! I have installed gdnsd3 on gns1.freebsd.org and added its AAAA record to the DNS. I will monitor this for a couple of days. If nothing breaks, I'll do the same on gns2.freebsd.org. *** Bug 247503 has been marked as a duplicate of this bug. *** Since gns1.freebsd.org has been behaving well, I installed gdnsd3 on gns2.freebsd.org too and added its AAAA record to the freebsd.org zone. IPv6++. :-) Yes, it works! Thanks. |