public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] IPv6 not ready here;  Hmmm
Date: Wed, 08 Jun 2011 13:59:36 -0500	[thread overview]
Message-ID: <4DEFC698.5010004@gmail.com> (raw)
In-Reply-To: <3624690.VRYPZsnpLZ@localhost>

Volker Armin Hemmann wrote:
> On Tuesday 07 June 2011 20:27:45 Dale wrote:
>
>
> 1&1:
>
> Test mit IPv4 DNS Eintrag	  	
> ok (0.712s) verwende ipv4
> Test mit IPv6 DNS Eintrag	  	
> ok (0.712s) verwende ipv6 6to4
> Test mit Dual Stack DNS Eintrag	  	
> ok (0.726s) verwende ipv4
> Test mit Dual Stack und grosse Pakete	  	
> ok (0.665s) verwende ipv4
> Test IPv4 ohne DNS	  	
> ok (0.417s) verwende ipv4
> Test IPv6 ohne DNS	  	
> ok (0.440s) verwende ipv6 6to4
> Test grosse IPv6 Pakete	  	
> ok (0.734s) verwende ipv6 6to4
> Test ob der DNS server des ISP IPv6 unterstützt	  	
> bad (1.401s)
>
> as the site explains the dns test is a goodie and failing it is not a big
> deal.
>
>    

Well, I have to ask this.  If the DNS fails, how will my browser know 
where to go?  From my understanding, when I type in abc.com and hit 
enter or go, the first thing it does is go to a DNS server to see what 
the actual number is.

Another question.  Mine failed on some of the ones yours passed on.  Is 
that a local setting or something between me and the site I am going 
to?  In other words, can I change something here or is it outside my 
control?  I think it is outside my control but want to make sure.

Dale

:-)  :-)



  reply	other threads:[~2011-06-08 19:01 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08  1:27 [gentoo-user] IPv6 not ready here; Hmmm Dale
2011-06-08  1:53 ` Dale
2011-06-08  2:18   ` Adam Carter
2011-06-08  5:31     ` Mick
2011-06-08  5:29 ` [gentoo-user] " Hans de Graaff
2011-06-08 17:01 ` [gentoo-user] " Volker Armin Hemmann
2011-06-08 18:59   ` Dale [this message]
2011-06-09  3:25     ` Volker Armin Hemmann
2011-06-09  4:56       ` Dale
2011-06-09  6:59         ` Volker Armin Hemmann
2011-06-08 19:51   ` Paul Hartman
2011-06-08 22:04     ` Mick
2011-06-09  1:25       ` Paul Hartman
2011-06-09  5:46         ` Mick
2011-06-09 15:06           ` Paul Hartman
2011-06-09 15:51           ` Paul Hartman
2011-06-09 20:27             ` Mick
2011-06-09 20:52               ` Paul Hartman
2011-06-09 11:16         ` Tanstaafl
2011-06-09 14:23           ` Mick
2011-06-09 16:21           ` Paul Hartman
2011-06-08 19:45 ` Paul Hartman
2011-06-08 20:08   ` Alan McKinnon
2011-06-08 20:01 ` Paul Hartman
2011-06-09  2:15   ` Dale
2011-06-09  3:23     ` Pandu Poluan
2011-06-09  4:50       ` Dale
2011-06-09  5:14         ` Paul Hartman
2011-06-09  6:52           ` Dale
2011-06-09  7:46             ` Alan McKinnon
2011-06-09  8:48               ` Dale
2011-06-10 15:46                 ` Dale
2011-06-10 16:03                   ` Paul Hartman
2011-06-10 17:39                     ` Dale
  -- strict thread matches above, loose matches on Subject: below --
2011-06-09  1:52 Pandu Poluan
2011-06-10  1:52 Pandu Poluan
2011-06-10  7:22 ` Joost Roeleveld
2011-06-10 10:08   ` Pandu Poluan
2011-06-10 13:17     ` Joost Roeleveld
2011-06-10 14:30       ` Alan McKinnon
2011-06-10 15:59         ` Joost Roeleveld
2011-06-10 16:04         ` Paul Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DEFC698.5010004@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox