[ipv6-wg] RIPE Atlas and NAT64 (Was: IPv6-only network during RIPE 71)
- Previous message (by thread): [ipv6-wg] RIPE Atlas and NAT64 (Was: IPv6-only network during RIPE 71)
- Next message (by thread): [ipv6-wg] ripemtg-nat64 network at RIPE71: complain here ;)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Tue Nov 3 16:44:09 CET 2015
Hi, On Tue, Nov 03, 2015 at 03:23:29PM +0100, Jen Linkova wrote: > I think there is a dirty hack to do it now: run a measurements from > v6-enabled probes to v4-only host, check the results for the > destination address they were using. Haha, I know something you don't :-) $ host ipv4only.arpa ipv4only.arpa has address 192.0.0.171 ipv4only.arpa has address 192.0.0.170 ... if that host ever resolves to a v6 address, you're behind a DNS64. (It won't *ping*, but it will give away DNS64 and the prefix used - of course pinging a well-known-ipv4-only-host would even validate whether the NAT64 is working...) Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 811 bytes Desc: not available URL: <https://lists.ripe.net/ripe/mail/archives/ipv6-wg/attachments/20151103/4c132eb6/attachment.sig>
- Previous message (by thread): [ipv6-wg] RIPE Atlas and NAT64 (Was: IPv6-only network during RIPE 71)
- Next message (by thread): [ipv6-wg] ripemtg-nat64 network at RIPE71: complain here ;)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]