XPost: comp.os.linux.networking   
   From: root@127.0.0.1   
      
   Ivan Shmakov wrote:   
      
   > Noob wrote:   
   >   
   >> Obviously, the STB is not able to talk directly to ipv6.google.com   
   >> since it does not support IPv6.   
   >>   
   >> I see several work-arounds.  The server could be dual stack, and   
   >> provide ALSO an IPv4 address, but 1) IPv4 address space is running   
   >> out and 2) the STB might be confused by the IPv6 addresses in the DNS   
   >> reply, even if it should just ignore them.   
   >   
   > 	Let's check it out:   
   >   
   > $ dig ipv6.google.com A   
      
   OK, you limited the request to "A" records, while I requested   
   "ANY" record.   
      
   I suppose legacy apps will be using gethostbyname() right?   
   And it seems gethostbyname will only request A records?   
      
   > As could be seen from the above, no AAAA (IPv6 address) resource   
   > records were returned by the server.   
      
   Obviously, since you requested only "A" records.   
      
   > So, there's nothing to confuse the device in question.   
      
   Thus the IPv4-only device is unable to talk to the   
   IPv6-only server, right?   
      
   > (Of course, it's unlikely that an IPv4-only device will ever   
   > request AAAA records from the DNS server.  Neither should it   
   > request ANY.)   
      
   I mistakenly believed gethostbyname would issue a request   
   for "ANY" record.   
      
   But in the scenario where the modem is trying to provide   
   "transparent" compatibility with IPv6-only nodes, does   
   that mean that some DNS-ALG is supposed to rewrite   
   outgoing DNS requests?   
      
   Regards.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)