Los Angeles Free-Net Information

restarted everything, even went to a another router, no connections at this time to lafn....
 

am I the only one not able to access mail?
 

No luck over here either. I'm in Venice CA. Restarted everything. Can't connect to lafn.org or mail. I'm on a Mac running Firefox
 

Same here. Attempting to load LAFN homepage. Started second computer--nothing. Rebooted router and DSL modem--nothing. Tried several combinations of rebooting browser and rebooting computer--nothing.

Email not working, either.

(rickvandusen)
 

Still no mail. 8:48 pm.
 

Decided to try tracert and see what happens. This happens:

Mon 08/30/2010 20:48:56.12
D:\>tracert www.lafn.org

Tracing route to zoom.lafn.org [206.117.18.8]
over a maximum of 30 hops:

1 30 ms 11 ms 11 ms 208-106-59-1.adsl.dynamic.lafn.org [208.106.59.1
]
2 12 ms 11 ms 11 ms 208-106-59-1.adsl.dynamic.lafn.org [208.106.59.1
]
3 12 ms 11 ms 21 ms 102.at-0-0-0.gw.lax1.sonic.net [208.106.123.73]

4 19 ms 17 ms 11 ms sonic-oc768.lax.layer42.net [216.129.102.37]
5 14 ms 13 ms 11 ms ln.net.any2ix.coresite.com [206.223.143.43]
6 176 ms 57 ms 13 ms 130.152.181.82
7 14 ms 23 ms 15 ms rand.ln.net [130.152.80.2]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 ^C
Mon 08/30/2010 20:50:04.50
D:\>


(rickvandusen)
 

Raffaello, have you restarted your computer? I had to do that, even after restarting our router ... the router showed the new DNS but I couldn't connect until I restarted the machine. ;-)
 

So, does anyone have mail coming to their mail program?

I'm now able to access LAFN and get online mail but that's it.
 

The issue here is that DNS has not propagated to the ISP you are using. You can see this in the traceroute that was in one of the previous comments. It shows attempts to access 206.117.18.x which are the old IP addresses. The original test we made last week showed it took 5 minutes to propagate. Today its taking considerably longer. I have no explanation for that. Most DNS servers should have retried and obtained the new DNS values after 20 minutes. Clearly they are not following the refresh times we published.

To check on the DNS status enter the following command into either Command LIne (windows) or Terminal (Mac):

dig www.lafn.org

If you get 206.117.18.8 then the DNS change has not reached you. If you get 75.101.116.66 then the DNS update has completed for you. If you still can't access mail etc., then you will need to restart routers or computers.
 

Tried "dig" (in Windows); get:

'dig' is not recognized as an internal or external command,
operable program or batch file.



(rickvandusen)
 

206.117.18.8

is what I get at 9:50 pm;
what now?
 

For Windows OS, instead of "dig" try "ping www.lafn.org"

I get this as a result:

"C:\>ping www.lafn.org

Pinging zoom.lafn.org [75.101.116.66] with 32 bytes of data:

Reply from 75.101.116.66: bytes=32 time=20ms TTL=61
Reply from 75.101.116.66: bytes=32 time=19ms TTL=61
Reply from 75.101.116.66: bytes=32 time=20ms TTL=61
Reply from 75.101.116.66: bytes=32 time=19ms TTL=61

Ping statistics for 75.101.116.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 20ms, Average = 19ms"

Which indicates we are on the new servers, but now we are suddenly getting errors with the mail ... am going to try rebooting the computer again.

(Diane ... as730)