On 28-Nov-05, at 2:43 PM, Steven Fisher wrote: > It works fine with Safari 2.0.2 (Tiger latest) from here. It's > probably just a DNS caching issue. Well, it did work. I stand by that. But it doesn't now. Strange one. -- Steve