INTERACT FORUM
More => Music, Movies, Politics, and Other Cheap Thrills => Topic started by: antenna on March 17, 2025, 11:36:59 pm
-
... please move it as appropriate.
OK, I usually access this forum by typing jriver.com into the browser, and then following the links to get to interact.
But this evening, when I enter jriver.com into my browser, I see...
The following error was encountered while trying to retrieve the URL: http://jriver.com/
Connection to 216.14.187.161 failed.
The system returned: (61) Connection refused
The remote host or network may be down. Please try the request again.
So, then i tried www.jriver.com, and, well, here I am.
More info ...
% telnet jriver.com 80
Trying 216.14.187.161...
telnet: Unable to connect to remote host: Connection refused
% telnet www.jriver.com 80
Trying 216.14.187.173...
Connected to www.jriver.com.
Escape character is '^]'.
Connection closed by foreign host.
jriver.com had always worked for me, now it seems to have issues.
What changed?
-
The servers moved over night, it should hopefully all settle soon.
-
Your old DNS record had a TTL of 6 or 7 days, so access may be disrupted for some users for up to a week depending on which DNS server they use and how old their DNS cache is :/
You may want to add a temporary 'newyabb.jriver.com' and use it on the main jriver page link until this settles. A new SSL certificate may be needed for that.
Alternatively, set up 216.14.187.174 as a transparently router/forwarder to 216.14.187.173.
Access works for me with 8.8.8.8 as the DNS server, but not with my ISP's DNS.
QUESTIONS:
yabb.jriver.com, type = ANY, class = IN
ANSWERS:
-> yabb.jriver.com
internet address = 216.14.187.174
ttl = 534366 (6 days 4 hours 26 mins 6 secs)
New server has 6 hours TTL, more sensible.
QUESTIONS:
yabb.jriver.com, type = ANY, class = IN
ANSWERS:
-> yabb.jriver.com
internet address = 216.14.187.173
ttl = 21600 (6 hours)
-
Your old DNS record had a TTL of 6 or 7 days, so access may be disrupted for some users for up to a week depending on which DNS server they use and how old their DNS cache is :/
Thanks for that.
Before I make such changes on my servers, I always lower the TTL of the DNS entries to an hour or so to reduce these types of issues.
Once things settle, I then increase the TTL of the DNS entries.
-
... New server has 6 hours TTL, more sensible.
Long term? I'd say, questionable.
But during transition evens, a TTL of an hour (or less, if your DNS provider supports it) is more sensible, imo. That's how I handle my server. The question becomes, how much difficulty do you want the users of your site to experience?
But I will say, YMMV.
It depends upon how the site owner wants to enable or restrict site access.
-
Another server change? Now it's 50.211.23.185.
TTL for the old one was still set to 7 days, so we can expect another week of instability :/
My corporate DNS servers still see the old record with 6d15h TTL, and so does my ISP... not good. Only 8.8.8.8 seems to see the new record.
-
Another server change? Now it's 50.211.23.185.
TTL for the old one was still set to 7 days, so we can expect another week of instability :/
My corporate DNS servers still see the old record with 6d15h TTL, and so does my ISP... not good. Only 8.8.8.8 seems to see the new record.
Sorry, I'll see if I can change the SOA and TTL so the old entries expire.
The good news is that the new internet connection is at least 10 times faster.
Edit: It should settle down in about 10 minutes if the internet servers pick up the changes. Should since the SOA updated.
-
Better to change that 1 week before the server move to prevent these issues.
- set ttl to 5 minutes (or desired max downtime)
- wait 1 week for change to propagate and old records to expire
- switch to new server
- raise TTL again
-
Better to change that 1 week before the server move to prevent these issues.
- set ttl to 5 minutes (or desired max downtime)
- wait 1 week for change to propagate and old records to expire
- switch to new server
- raise TTL again
Yes.
Obviously it's changed now. There are still a few to do which will speed that up.