After working on a proposal for introduc ... / 2007-10-25

2007-10-25 After working on a proposal for introduc ...
After working on a proposal for introducing IPv6 at work it suddenly dawned on me that pushing ipv6 at home wasn't going to work with a separate DNS zone for IPv6 addresses. The best way is to integrate ipv6 addresses in the main zone and have the "legacy ipv4 nat range" as second thing to try (for things that are still ipv4-only like nfs). But I found something weird in certain applications: for unqualified names, ipv4 is preferred, for qualified names ipv6. Forcing ipv6 works, but I want ipv6 to happen naturally.

Telnet shows best what happens:
$ telnet gosper
Trying 10.42.2.1...
Trying 2001:888:1011::694...
$ telnet gosper.idefix.net
Trying 2001:888:1011::694...
Trying 82.95.196.202...
Something weird happening here, so I asked the debian-ipv6 mailing list.

Tags: , ,

IPv6 check

Running test...
, reachable as koos+website@idefix.net. PGP encrypted e-mail preferred. PGP key 5BA9 368B E6F3 34E4 local copy PGP key 5BA9 368B E6F3 34E4 via keyservers

RSS
Meningen zijn die van mezelf, wat ik schrijf is beschermd door auteursrecht. Sommige publicaties bevatten een expliciete vermelding dat ze ongevraagd gedeeld mogen worden.
My opinions are my own, what I write is protected by copyrights. Some publications contain an explicit license statement which allows sharing without asking permission.
Other webprojects: Camp Wireless, wireless Internet access at campsites, The Virtual Bookcase, book reviews
This page generated by $Id: newsitem.cgi,v 1.55 2021/11/09 13:09:49 koos Exp $ in 0.006398 seconds.