Has gpxeditor died

[Ian H]

It's not loading.  Have I missed something?

[vorsprung]

The DNS whois records for gpxeditor.co.uk was updated yesterday but is not apparently resolving

So on a server somewhere on the Internet, gpxeditor is running quite happily but with broken DNS no one knows where

[DDCyclist]

Ping request could not find host www.gpxeditor.co.uk

Suggests a possible dns problem.

Domain name is registered until Nov 2015. A brief scan suggests no problems on SourceForge. Did not see any hints of problems on other forums.

I think it's a 'try again later' sort of problem.

[321up]

As a subscriber I got an email yesterday.  It can be accessed here...
http://gpxeditor.azurewebsites.net/

[DDCyclist]

Also back on www.gpxeditor.co.uk

[Ben T]

It's fine now, I was just transferring the domain, sorry. I had hoped the records would maintain during the transfer but they dropped for a while.

As said can also use http://gpxeditor.azurewebsites.net/ but should be fine now.

[Ben T]

As a subscriber I got an email yesterday.  It can be accessed here...
http://gpxeditor.azurewebsites.net/

The email mailing list isn't necessarily only subscribers,  but those subscribers whose email I know (not all, believe it or not) plus any other "interested parties" so if anyone wants to be added to it (feature updates, etc) please pm me.

[Phil W]

DNS changes usually take about 24 hours before all the DNS caches are refreshed  out there. Usually best to keep old site up , but turn off updates during this period. Then you can shut down old site and turn updates back on.

[vorsprung]

DNS changes usually take about 24 hours before all the DNS caches are refreshed  out there. Usually best to keep old site up , but turn off updates during this period. Then you can shut down old site and turn updates back on.

Or you can alter the TTL as explained here https://www.dnswatch.info/articles/dns-update

[Phil W]

DNS changes usually take about 24 hours before all the DNS caches are refreshed  out there. Usually best to keep old site up , but turn off updates during this period. Then you can shut down old site and turn updates back on.

Or you can alter the TTL as explained here https://www.dnswatch.info/articles/dns-update

You can but that doesn't force all DNS caches to update to that timescale.  If you do at time of update they will still look according to the old refresh time interval set. So you need to update TTL in advance of the actual change of IP. Some DNS caches still don't look more frequently than every 24 hours regardless of TTL values.

[vorsprung]

DNS changes usually take about 24 hours before all the DNS caches are refreshed  out there. Usually best to keep old site up , but turn off updates during this period. Then you can shut down old site and turn updates back on.

Or you can alter the TTL as explained here https://www.dnswatch.info/articles/dns-update

You can but that doesn't force all DNS caches to update to that timescale.  If you do at time of update they will still look according to the old refresh time interval set. So you need to update TTL in advance of the actual change of IP.

I thought the page I linked explained all that.  *looks again* Oh yes, it does.  Never mind

Some DNS caches still don't look more frequently than every 24 hours regardless of TTL values.

Then they are broken and their users are unfortunate victims of mismanagement