From: boite-a-spam@plouf.fr.eu.org   
      
   Hello,   
      
   Aaron Spiteri a écrit :   
   >   
   > ;; ANSWER SECTION:   
   > azzmosphere.azzmos.com.au. 0    IN      AAAA    fe80::216:cbff:feb3:87cf   
      
   This is a link-local address. Also the TTL is zero, could this be the   
   source of the problem ?   
      
   > ping6 fe80::216:cbff:feb3:87cf   
   > PING6(56=40+8+8 bytes) fe80::216:cbff:feb3:87cf%en1 -->   
   > fe80::216:cbff:feb3:87cf   
   > 16 bytes from fe80::216:cbff:feb3:87cf%en1, icmp_seq=0 hlim=64   
   > time=2.656 ms   
      
   A link-local address alone is ambiguous and does not specify a unique   
   destination because it may be reachable on different links connected to   
   the host ; so it must be completed with the local interface connected to   
   the link connected to the destination, for exemple by appending a suffix   
   %interface to it, which your ping6 seems to do automatically. Mine does   
   not, it requires I specify the interface explicitly.   
      
   > $ ping6  azzmosphere.azzmos.com.au   
   > ping6: No address associated with nodename   
      
   Maybe the local resolver discards link-local addresses because they are   
   ambiguous. Did you try with a global or unique local address instead ?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)