> > Here's a theoretical solution to this problem that I'd like to open for
> > discussion.
> >
> > In each location where a provider hosts their anycasted service, there
> > is likely a local, non-anycasted IP address for each server.
There should be, yes.
> > When
> >
In message , Peter Beckman
writes:
> After a few emails traded with David Ulevitch from OpenDNS, it is clear to
> me that they do NOT suffer from this issue, and have a work-around. My
> apologies to David and to OpenDNS for lumping them in and not doing better
> due dilligence when rese
After a few emails traded with David Ulevitch from OpenDNS, it is clear to
me that they do NOT suffer from this issue, and have a work-around. My
apologies to David and to OpenDNS for lumping them in and not doing better
due dilligence when researching this issue.
On Sat, 7 Feb 2009, TJ wrot
@nanog.org
>Subject: RE: L3: Google from DC via the Netherlands?
>
>On Fri, 6 Feb 2009, Peter Beckman wrote:
>
>> I'm OK to that IP as well, but when I query www.google.com, I get
>> multiple IPs, but here are the ones that in in 147:
>>
>> DNS Server
> On Fri, Feb 06, 2009 at 12:05:41PM -0500, Peter Beckman wrote:
> > I'm OK to that IP as well, but when I query www.google.com, I get multiple
> > IPs, but here are the ones that in in 147:
> >
> > DNS Server IP Route (for me)
> > 205.234.170.217 (tiggee)74.125.79
On Fri, Feb 06, 2009 at 12:05:41PM -0500, Peter Beckman wrote:
> I'm OK to that IP as well, but when I query www.google.com, I get multiple
> IPs, but here are the ones that in in 147:
>
> DNS Server IP Route (for me)
> 205.234.170.217 (tiggee)74.125.79.147 Amste
On 2009-02-06, Peter Beckman wrote:
> On Fri, 6 Feb 2009, Peter Beckman wrote:
>
>> I'm OK to that IP as well, but when I query www.google.com, I get multiple
>> IPs, but here are the ones that in in 147:
>>
>> DNS Server IP Route (for me)
>> 205.234.170.217 (tiggee)
Peter Beckman wrote:
SO. Who's problem is this to fix? Is it:
1. Me? Am I a dope for using a very reliable but anycasted resolving
name service? Clearly, I could just use the handy dandy easy to
remember because I worked there 198.6.1.x, or is that an Internet
faux
On Fri, 6 Feb 2009, Peter Beckman wrote:
I'm OK to that IP as well, but when I query www.google.com, I get multiple
IPs, but here are the ones that in in 147:
DNS Server IP Route (for me)
205.234.170.217 (tiggee)74.125.79.147 Amsterdam
208.67.222.222 (opendns
om: Peter Beckman [mailto:beck...@angryox.com]
Sent: Friday, February 06, 2009 11:01 AM
To: nanog@nanog.org
Subject: L3: Google from DC via the Netherlands?
Seems strange. Had a partial outage on Verizon network this morning
around
9:50am EST, then when it came back around 10:05am, google routed via
-f100.google.com
(74.125.67.100) 28.393 ms 209.85.255.194 (209.85.255.194) 35.464 ms
-Original Message-
From: Peter Beckman [mailto:beck...@angryox.com]
Sent: Friday, February 06, 2009 11:01 AM
To: nanog@nanog.org
Subject: L3: Google from DC via the Netherlands?
Seems strange. Had a
Seems strange. Had a partial outage on Verizon network this morning around
9:50am EST, then when it came back around 10:05am, google routed via the
Netherlands. My guess is that there's some sort of routing problem making
my fastest or least cost route go to the Netherlands, but I wanted to find
12 matches
Mail list logo
