Skip to Content.
Sympa Menu

dns-operations - Re: [opennic-dns-operations] Addition of location fields to T2 server configs

dns-operations AT lists.opennicproject.org

Subject: Dns-operations mailing list

List archive

Re: [opennic-dns-operations] Addition of location fields to T2 server configs


Chronological Thread 
  • From: Alex Hanselka <alex AT opennicproject.org>
  • To: dns-operations AT lists.opennicproject.org
  • Subject: Re: [opennic-dns-operations] Addition of location fields to T2 server configs
  • Date: Fri, 27 Jul 2012 00:35:42 -0500

Well, the problem is, even though the endpoint is in texas, the server is
still in IN. The IPv6 packets will just travel over IPv4 from the tunnel
server in Texas to your VPS in IN. This adds a few extra hops, but it is the
same as if suddenly all traffic were routed through Canada. You wouldn't list
Canada as the location of your server just because someone changed a router.
At least, that's how I see it. Your traffic to an IPv6 tunnel is being routed
through a tunnel server but that is still no indication of where your server
is.


On Jul 26, 2012, at 10:36 PM, Jeff Taylor <shdwdrgn AT sourpuss.net> wrote:

> See? The tunnels confuse everything. Honestly I have no idea what
> would give a more accurate map for trying to find the shortest network path.
>
> On 07/26/2012 01:14 PM, Brian Koontz wrote:
>> On Thu, Jul 26, 2012 at 12:59:56AM -0600, Jeff Taylor wrote:
>>> We have found that by using geoIP to map out servers, many are pinned to
>>> the wrong locations (sometimes to the wrong country). And there is no
>>> way to map out IPv6 locations since many people are using tunnels. By
>>> manually entering the correct location of your server(s), you help
>>> increase the usefulness of any mapping projects for OpenNic.
>> Actually, wouldn't it be more useful to map the endpoint of your ipv6
>> tunnel? For instance, my server is in IN, but the endpoint is in
>> TX.
>>
>> --Brian
>>
>
>
>
> ----
> To unsubscribe, email dns-operations-unsubscribe AT lists.opennicproject.org




Archive powered by MHonArc 2.6.19.

Top of Page