At 08:34 AM 16/07/2009, Leyne, Sean wrote:

>Mark,
>
>> Are there problems with the firebirdsql.org nameservers? For a while now
>> I have intermittent problems accessing various *.firebirdsql.org sites
>> due to nameservers not resolving the hostnames.
>>
>> After a few reload attempts or trying at a different time the address
>> will eventually be resolved and the site loads normally. From my home I
>> have the problem intermittently, while on work (totally different
>> provider) I am usually unable to access any firebirdsql.org address.
>
>I don't know what to say.
>
>I host the firebirdsql.org servers (DNS is handled via another group which Helen deals with).
>
>I can say that the IP/DNS information for the hosts hasn't changed in several months... so, I can't think of any reason why you would be having problems.

Once in a while (perhaps once in six months) we do get some temporary stand-down when our DNS host moves things about the farm. I usually get advance warning of that - in hours rather than days - so usually by the time I get any message the deed is done.

Occasionally, tracker.firebirdsql.org stalls, due to a bug in the rather ancient version of the Atlassian Jira/Java framework it runs off. Love it or hate it, we just have to live with it for now. Newer versions won't run on the version of Linux we run.

In recent days, some people have reported DNS problems from some European ISPs that haven't been experienced by the rest of us.

I suggest that, if you're getting persistent http access problems, you try refreshing browser cache and/or bypassing any proxy http server that you have configured.

All that said, reverse DNS does NOT work (according to our DNS host provider, Sean's services are not configured to enable it) so nslookup won't help you find the breakages. A tracert could be slightly helpful.

Helen