From: Mike Lane on
Jeffrey Goldberg wrote on Jun 20, 2010:

> On 10-06-20 6:55 AM, Mike Lane wrote:
>> Gavin Richardson wrote on Jun 20, 2010:
>>
>>> It is a known problem and 1password have posted this message on their
>>> twitter account.
>>>
>>> Customers of some ISPs in NW Europe have been having trouble reaching
>>> our site. We're still here! Please try GoogleDNS or OpenDNS instead.
>
>> THANKS!!
>
>> I've switched my DNS setting to use GoogleDNS (8.8.8.8, 8.8.4.4) and this
>> has
>> solved the problem.
>
> I'm glad that that works. Now that you've switched, there's no reason
> to run the tests that I suggested in my previous post.
>
>> Are there any issues with using this setting permanently, does anyone know?
>
> I've been using Google DNS for my home network since it was first
> announced. It's been fine.
>
> If you want to make the change permanent, you should probably make the
> change in your local router. That will be the thing that is either
> using your ISP's name servers or telling machines on your network to use
> those name servers.
>
> (And to help me track down the DNS problems, I would love to know what
> the current settings on your router are.)
>

Sorry, but I'm not sure what you're asking here. I don't have a home network
or a router. My computer simply connects directly via an ethernet cable to a
cable modem which plugs into my local cable company's socket.


--
Mike Lane
UK North Yorkshire
email: mike_lane at mac dot com

From: Jeffrey Goldberg on
On 10-06-20 5:06 PM, Mike Lane wrote:
> Jeffrey Goldberg wrote on Jun 20, 2010:

>> (And to help me track down the DNS problems, I would love to know what
>> the current settings on your router are.)

> Sorry, but I'm not sure what you're asking here. I don't have a home network
> or a router. My computer simply connects directly via an ethernet cable to a
> cable modem which plugs into my local cable company's socket.

Thanks Mike. That does, actually, help answer my question. I had made
incorrect assumptions about your set-up. As a consequence my comments
made no sense.

Would you mind running one command for me in Terminal (Terminal.app can
be found in the Utilities Folder in Applications)

Just paste the following into the Terminal window and hit return.

traceroute agile.ws

Could you then paste the response back into a message here or to me? If
you don't feel comfortable sharing that data with the world then could
you send it to support(a)agile.ws and just add a note referencing this
discussion?

You are under no obligation to do this, but it would help us try to
figure out what has been going on with people not being able to reach us.

Also if you remember your old settings for DNS servers (before you
switched to Google DNS) that would be helpful, too.

I'm sorry for pestering you, it's just that we want to know as much as
possible about the state of the network between ourselves and people
who've seen this problem.

Cheers,

-j


--
Jeffrey Goldberg http://goldmark.org/jeff/
I rarely read HTML or poorly quoting posts
Reply-To address is valid
From: Mike Lane on
Jeffrey Goldberg wrote on Jun 20, 2010:

> On 10-06-20 5:06 PM, Mike Lane wrote:
>> Jeffrey Goldberg wrote on Jun 20, 2010:
>
>>> (And to help me track down the DNS problems, I would love to know what
>>> the current settings on your router are.)
>
>> Sorry, but I'm not sure what you're asking here. I don't have a home network
>> or a router. My computer simply connects directly via an ethernet cable to
>> a
>> cable modem which plugs into my local cable company's socket.
>
> Thanks Mike. That does, actually, help answer my question. I had made
> incorrect assumptions about your set-up. As a consequence my comments
> made no sense.
>
> Would you mind running one command for me in Terminal (Terminal.app can
> be found in the Utilities Folder in Applications)
>
> Just paste the following into the Terminal window and hit return.
>
> traceroute agile.ws
>
OK, the response to this is:

traceroute to agile.ws (74.208.8.44), 64 hops max, 52 byte packets
1 * 10.133.140.1 (10.133.140.1) 4091.687 ms 18.836 ms
2 midd-cam-1a-v115.network.virginmedia.net (213.106.238.13) 25.948 ms
50.729 ms 12.963 ms
3 midd-core-1a-ae1-0.network.virginmedia.net (195.182.176.97) 9.728 ms
17.520 ms 50.713 ms
4 leed-bb-1a-as7-0.network.virginmedia.net (213.105.75.45) 12.202 ms
50.563 ms 13.219 ms
5 nrth-bb-1b-as2-0.network.virginmedia.net (62.253.185.101) 11.976 ms
16.835 ms 49.211 ms
6 tele-ic-1-as0-0.network.virginmedia.net (62.253.184.2) 15.205 ms 38.564
ms 24.724 ms
7 linx.bb-c.the.lon.gb.oneandone.net (195.66.224.98) 38.192 ms 28.253 ms
28.730 ms
8 ae-0-0.bb-a.the.lon.gb.oneandone.net (212.227.120.26) 43.209 ms 40.104
ms 26.441 ms
9 so-2-0-0-0.bb-a.tlx.nyc.us.oneandone.net (212.227.120.32) 104.934 ms
116.559 ms 105.428 ms
10 ge-1-13.bb-c.tlx.nyc.us.oneandone.net (74.208.1.37) 128.931 ms 110.060
ms 106.209 ms
11 te-3-3.bb-b.cr.chi.us.oneandone.net (74.208.6.81) 114.867 ms 132.985 ms
114.183 ms
12 * * te-2-4.bb-b.ws.mkc.us.oneandone.net (74.208.1.54) 3540.704 ms
13 te-1-2.bb-a.slr.lxa.us.oneandone.net (74.208.1.89) 3522.410 ms 3715.195
ms 3771.665 ms
14 te-1-1.gw-distp-b.slr.lxa.oneandone.net (74.208.1.118) 3861.081 ms
4021.576 ms
te-1-2.gw-distp-b.slr.lxa.oneandone.net (74.208.1.102) 4152.459 ms
15 ae-1.gw-prtr-r5-b.slr.lxa.oneandone.net (74.208.1.168) 4369.388 ms
4499.589 ms 4631.935 ms
16 agilewebsolutions.com (74.208.8.44) 4709.127 ms 4917.589 ms 4811.596
ms
cpc1-mars1-0-0-cust855:~ mike_lane$


> Also if you remember your old settings for DNS servers (before you
> switched to Google DNS) that would be helpful, too.

The previous DNS settings were:
194.168.4.100, 194.168.8.100

>
> I'm sorry for pestering you, it's just that we want to know as much as
> possible about the state of the network between ourselves and people
> who've seen this problem.
>
No problem!

--
Mike Lane
UK North Yorkshire
email: mike_lane at mac dot com

From: Jeffrey Goldberg on
On 10-06-20 6:07 PM, Mike Lane wrote:
> Jeffrey Goldberg wrote on Jun 20, 2010:

>> Would you mind running [...]

> No problem!

Thank you very much. Until now I thought the problem in the UK was
limited to Sky and Tiscali. Now I see Virgin Media as well.

I don't really have a good enough sample, but I think that all of the UK
reports I've seen for which I have a location are in The North. You are
in Yorkshire, I've seen a problem from "near Manchester" and I think
there was another somewhere east of Liverpool (I'll have to go back and
check on these reports). One of our staff is in Leeds, but he hasn't
been able to duplicate the problem.

We've also know that there some users in Ireland, Norway and Italy have
been affected. (We had declared this a problem in "northwest Europe"
before we saw the reports from Italy).

Anyway, thanks for your help.

Cheers,

-j

--
Jeffrey Goldberg http://goldmark.org/jeff/
I rarely read HTML or poorly quoting posts
Reply-To address is valid
From: Phillip Jones on
Mike Lane wrote:
> Jeffrey Goldberg wrote on Jun 20, 2010:
>
>> On 10-06-20 6:55 AM, Mike Lane wrote:
>>> Gavin Richardson wrote on Jun 20, 2010:
>>>
>>>> It is a known problem and 1password have posted this message on their
>>>> twitter account.
>>>>
>>>> Customers of some ISPs in NW Europe have been having trouble reaching
>>>> our site. We're still here! Please try GoogleDNS or OpenDNS instead.
>>
>>> THANKS!!
>>
>>> I've switched my DNS setting to use GoogleDNS (8.8.8.8, 8.8.4.4) and this
>>> has
>>> solved the problem.
>>
>> I'm glad that that works. Now that you've switched, there's no reason
>> to run the tests that I suggested in my previous post.
>>
>>> Are there any issues with using this setting permanently, does anyone know?
>>
>> I've been using Google DNS for my home network since it was first
>> announced. It's been fine.
>>
>> If you want to make the change permanent, you should probably make the
>> change in your local router. That will be the thing that is either
>> using your ISP's name servers or telling machines on your network to use
>> those name servers.
>>
>> (And to help me track down the DNS problems, I would love to know what
>> the current settings on your router are.)
>>
>
> Sorry, but I'm not sure what you're asking here. I don't have a home network
> or a router. My computer simply connects directly via an ethernet cable to a
> cable modem which plugs into my local cable company's socket.
>
>
Ugh! That a no-no that about the most insecure way to have an internet
connection over cable or DSL. You always use a router in between. This
adds layer of protection.

You not sure your cable modem doesn't a Router built in

--
Phillip M. Jones, C.E.T. "If it's Fixed, Don't Break it"
http://www.phillipmjones.net mailto:pjones1(a)kimbanet.com