Topic: Contribs.org

[Randy]

anybody know what happened to contribs.org? I have not been able to get on it all week.

randy

[Bob]

Not sure what the problem is, gut I just checked it, and it is up and running just fine

Bob

[Randy]

intersting i still cant get there.  Any chance you can do a tracert and tell me the ip? i think mabey i have a routing problem.

[Jim Huneycutt]

204.17.35.130

[Brad]

Randy,
I can get to contribs.org useing IE 6 for WinXP, but tracert barfs on HOP13.



C:\Documents and Settings\Brad>tracert contribs.org

Tracing route to contribs.org [207.182.33.22]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  ***[192.168.1.6]
  2    1 ms       1 ms    1 ms  ***

  3    1 ms       1 ms    1 ms  ***

  4    1 ms       3 ms    2 ms  GIG2-0.tor-core-a.peer1.net [216.187.68.45]
  5    49 ms    23 ms    24 ms  GIG4-0.chi-gsr-a.peer1.net [216.187.68.58]
  6    24 ms    24 ms    25 ms  eqix.chcg.twtelecom.net [206.223.119.36]
  7    22 ms    24 ms    23 ms  core-01-so-1-1-0-0.chcg.twtelecom.net [66.192.244.53]
  8    66 ms    66 ms    67 ms  core-02-so-0-0-0-0.phnx.twtelecom.net [66.192.255.91]
  9    70 ms    71 ms    69 ms  dist-01-so-3-0-0-0.tcsn.twtelecom.net [216.136.127.14]
 10    72 ms    70 ms    70 ms  hagg-01-ge-0-3-0-0.tcsn.twtelecom.net [66.162.41.2]
 11    80 ms    78 ms    82 ms  66.162.41.18
 12    83 ms    80 ms    83 ms  fa1-1.tus2.LOGIN.COM [204.17.35.82]
 13     *        *     Login-GW.Opus1.COM [204.17.35.130]  reports: Destination net unreachable.

Trace complete.

[Randy]

207.182.33.22  this ip works for me. : ) bit contribs.org does not resolv. maybe they had an ip change.

thanks a bunch

[Randy]

well ok 207.182.33.22 will take me to the home page but the download page will not load. i will try again tomarrow, to day must not be my day.

[Ron]

This is what I have to do. It's been that way since Oct24.(when they made some changes)
http://207.182.33.22/contribs
I think eventually it will correct itself.

[Kurt]

Randy,

Check your squid settings.

[Jeff C]

Contribs.org is indeed at 207.182.33.22.  If you are having trouble gettingthere it is probable that the dns server you are utilizing is not updating its cache often enough.

The contribs.org zone record was set to a low TTL in order to guarantee minimum confusion when we moved last month.  While it has been moved back  to a more reasonable TTL now, any nameserver that has not yey updated has been either set to WAY too long a caching period or is not responding to the refresh info in the zone records.

I hope this helps a little.

[Charlie Brady]

Jeff C wrote:

> The contribs.org zone record was set to a low TTL in order to
> guarantee minimum confusion when we moved last month.  While
> it has been moved back  to a more reasonable TTL now, any
> nameserver that has not yey updated has been either set to
> WAY too long a caching period

Nameservers aren't configured with caching periods, but use the TTL info included with the records they cache. Or at least they should. Any which doesn't is fundamentally broken.

> or is not responding to the refresh info in the zone records.

Only contribs.org secondaries should be transferring zones, and AIUI, there is only one secondary, and that is under your control.

If contribs.org is unresolvable or unreachable, I'd be looking for a cause other than name server caching (especially without direct evidence of lookup errors).

Charlie

[Jeff C]

Charlie wrote:

>Nameservers aren't configured with caching periods, but use >the TTL info included with the records they cache. Or at least >they should. Any which doesn't is fundamentally broken.

> or is not responding to the refresh info in the zone records.

You are correct as to the RFCs.  But AOL, for example, will not allow their servers to update in under a certain amount of time regardless of the zone record TTL.  I agree that this is a fundamentally broken process, just one that 20+ million users rely on.

>Only contribs.org secondaries should be transferring zones, >and AIUI, there is only one secondary, and that is under your >control.

>If contribs.org is unresolvable or unreachable, I'd be looking >for a cause other than name server caching (especially without >direct evidence of lookup errors).

Again we agree.  Contribs.org resolves properly from ALMOST everywhere.  We have resolved several specific issues for users where we established that the ISPs name servers were not updating properly.

So, the only place we disagree is that there are nameservers running out there that DO cache longer than zone records indicate.

Thanks for your participation.

-jeff

[Charlie Brady]

Jeff C wrote:

> Charlie wrote:
>
> >Nameservers aren't configured with caching periods, but use
> >the TTL info included with the records they cache.
[...]
> You are correct as to the RFCs.  But AOL, for example, will
> not allow their servers to update in under a certain amount
> of time regardless of the zone record TTL.

Not according to their FAQ (http://webmaster.info.aol.com/faq.html) which says:

    Q. Our IP address was just changed and our AOL visitors are experiencing a DNS error. When does AOL update it's [sic] DNS to see new IP's [sic]?

    A. AOL's DNS servers respect TTL (the Time To Live). Check with your previous Internet service provider as to the setting value of the old TTL. When that value expires, AOL's DNS will then propagate the new IP address.

Can you point me to any evidence that AOL are doing other than as they say they are?

Charlie