Comments on: bxr.su announced https://www.dragonflydigest.com/2013/04/04/bxr-su-announced/ A running description of activity related to DragonFly BSD. Thu, 04 Apr 2013 18:59:30 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: Constantine A. Murenin https://www.dragonflydigest.com/2013/04/04/bxr-su-announced/comment-page-1/#comment-48931 Thu, 04 Apr 2013 18:59:30 +0000 http://www.shiningsilence.com/dbsdlog/?p=11527#comment-48931 Yeap, and also, there are no IPv4 glue records until 2013-04-24, so, the IPv4 address that is published in the A record today and also from 2013-04-14 onwards, can only be had if your resolver has IPv6 connectivity.

If you don’t have IPv6, this is nonetheless mostly not a problem if your ISP already has at least some partial IPv6 deployment to some users — most of the national ISPs (at least in the U.S.) already have each resolver dual stacked all across.

However, if your ISP has no IPv6 network whatsoever, you could still use Google Public DNS at 8.8.8.8, or ordns.he.net at 74.82.42.42, which should not have any problems with contacting IPv6-only NS, and can resolve A-records of domains with IPv6-only delegations (e.g. IPv6-only NS), when requested by an IPv4-only client, without any problems.

]]>