Server up or down? (dns - server ip may change rarely!)

03 Oct 23: One server has been relocated, the server currently doesn't have a public IP address in the meantime. I wrote some additional tunnel code running separately to handle this. When the server is engaged the connection is 5600+ days uniform (since around 24 July 2008). In the unlikely case I disengaged the server because of some problem the retention is 1200-3800 days depending on newsgroup. If you experience any issue please let me know.

29 Nov 23: Because of encrypted and "obfuscated" flood mass posted by few nzb websites and newzbin-like communities using usenet servers as private storage for their members to download the posts - the situation with the content is pretty chaotic, since posts are disguised in such a way, that users must use the satellite ecosystem (whish is not a part of Usenet) exclusively to download them, when the website disappears - the encrypted scattered posts just eat usenet providers' disk space uselessly. If you can't find something specific please let me know what exactly you can't find for me to check how it is possible to retain the posts. Legible posts shouldn't be affected at all, let me know if you notice anything missing.

08 Aug 24: After being unchanged for many years the search service communication protocol had to be updated a few times in part to resolve a server side set feature limitation and properly handle trial searches on the relocated server. The searches themselves are not affected and it looks like the work is now complete.

15 Mar 25: It looks like the search service is currently down as there are no pings. The other server is no more on starlink, but the search requests are still routed and the access to it is through the first server, since it is safer, but the direct access is no problem if this will be a repeated issue. The connection will be restored or server restarted as soon as possible.

16 Mar 25: One server is currently still down, the other server was reconfigured and already connected directly, so the search service is running with minimum possible retention gaps.
Post Reply
Josef K
Posts: 534
Joined: Thu Feb 27, 2003 7:29 pm

Server up or down? (dns - server ip may change rarely!)

Post by Josef K »

Searching has been timing out for me all day (about seven hours since I first attempted) with the message about 'connected party did not respond'.

All other network related connections running fine, downloading with UE is fine, etc. and UE has been running overnight until now apart from one restart but that was after searching had already failed. I was searching with no issues last night but now nothing but that message. I reset configuration but it didn't resolve the issue. I've allowed UE full trusted access through my firewall even though it doesn't need it since it was already properly configured but no joy.

Has something been changed on the server in the last 24 hours?
alex
Posts: 4547
Joined: Thu Feb 27, 2003 5:57 pm

Post by alex »

nothing changed, does it work now?
maybe some temporary connectivity problem from your location.
Josef K
Posts: 534
Joined: Thu Feb 27, 2003 7:29 pm

Post by Josef K »

Ah.

My firewall caches IP addresses. I've deleted the two entries (ueservice.dyndns.org and ueservice2.dyndns.org) and upon making a new search after that, my firewall popped up. OK, issue sorted and I'll exclude the search server from the cache from now on.

Are you sure the server's IP hasn't changed because my firewall was passing UE its cached IP, disallowing a DNS request for the actual one and presumably this problem arose because the server's IP has changed since then.

Also, should I just allow ueservice.dyndns.org or ueservice2.dyndns.org as well in my firewall rules? Making a search earlier to test things showed me two connections to ueservice2.dyndns.org but only one to ueservice.dyndns.org and that was the only that appeared to be using bandwidth while the other two were open but dormant. Is ueservice2.dyndns.org still being used?
alex
Posts: 4547
Joined: Thu Feb 27, 2003 5:57 pm

Post by alex »

yes, i see now the ip address of the new server has changed, i kept the prior ip here for some case, i see now it is different, but the configuration file doesn't contain numberic ip addresses so if they are resolved normally - everything should work.

it changed Aug. 15, 2007 3:21 AM, i'm not sure what time maybe UTC, at the moment it is Aug. 16, 2007 6:26 AM the same time, in short about 23 hours ago.

usually ip addresses don't change but they may change. yes, you need to allow ueservice and useservice2 dyndns.org
Josef K
Posts: 534
Joined: Thu Feb 27, 2003 7:29 pm

Post by Josef K »

OK, the problem is sorted then. At least now it's something to keep in mind in case people mention in future that they lost access to searches. IP caching has been very useful for me in the past (sites changing hosts or DNS) where I couldn't access them other than through their IP address. For the record I'm using Outpost Firewall.
Post Reply