| From: | "John Hansen" <john(at)geeknet(dot)com(dot)au> |
|---|---|
| To: | "Magnus Hagander" <mha(at)sollentuna(dot)net>, "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>, <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: Search machine is ready |
| Date: | 2006-03-13 09:00:02 |
| Message-ID: | 34F8F335525CB14C95CF92BE2194858E0128A3@pdc.geeknet.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
Hmmm,.... Odd
The expire timeout for the SOA record is 5 hrs.
It was added way longer ago than that.
My own DNS has picked it up, but I know my ISP's DNS hasn't,.
(and hence I can't test it myself yet, as they do transparent proxying)
Would most ISP's be conservative and specify a minimum TTL for ALL records, regardless of what they have been configured to?
... John
> -----Original Message-----
> From: Magnus Hagander [mailto:mha(at)sollentuna(dot)net]
> Sent: Monday, March 13, 2006 7:45 PM
> To: Dave Page; John Hansen; pgsql-www(at)postgresql(dot)org
> Subject: RE: [pgsql-www] Search machine is ready
>
> > > Okay folks...
> > >
> > >
> > > http://search2.postgresql.org/ is now ready for testing...
> > >
> > > Please report any issues you may find,..
> >
> > "Firefox can't find the server at search2.postgresql.org"
> >
> > :-(
>
> That would be that thing called DNS caching with timeout...
> Be patient!
>
> //MAgnus
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Hansen | 2006-03-13 09:03:02 | Re: Search machine is ready |
| Previous Message | Magnus Hagander | 2006-03-13 08:57:40 | Re: Search machine is ready |