My system has not been able to connect to Vert in two days, and
now CVS, IRC, QWK, and Verts FTP are all down. Does anyone know
if they will be back up sometime soon?
My system has not been able to connect to Vert in two days, and now CVS, IRC, QWK, and Verts FTP are all down.
Does anyone know if they will be back up sometime soon?
cable/internetMy system has not been able to connect to Vert in two days, and
now CVS, IRC, QWK, and Verts FTP are all down. Does anyone know
if they will be back up sometime soon?
You must have missed the announcement that DM was moving his
service to the new house today. It'll be back up as soon as he gets everything up and running again at the new place. So just hang tight.
You must have missed the announcement that DM was moving hiscable/internet
service to the new house today. It'll be back up as soon as he
gets everything up and running again at the new place. So just
hang tight.
Including his DNS servers, so everybody that uses a xxx.synchro.net hostname, is unreachable. Talking about a SPOF. :-(
Including his DNS servers, so everybody that uses a xxx.synchro.net
hostname, is unreachable. Talking about a SPOF. :-(
That is not the fault of the person providing the service. That is the fault of the sysops who rely on only that one single service. While he provides a DNS service, he is still indeed just a sysop like everyone else. *shrug*
You must have missed the announcement that DM was moving his cable/internet service to the new house today. It'll be back up as soon as he gets everything up and running again at the new place. So just hang tight.
Interestingly, my BBS is apparently still exchanging Dove-Net messages from VERT (I keep seeing new messages posted on Dove-Net). I know his systems are down, and his BBS web site at vert.synchro.net isn't
loading, so I'm wondering how my BBS is able to connect & exchange Dove-Net messages right now.
else.You must have missed the announcement that DM was moving his
cable/internet
service to the new house today. It'll be back up as soon as he
gets everything up and running again at the new place. So just
hang tight.
Including his DNS servers, so everybody that uses a xxx.synchro.net
hostname, is unreachable. Talking about a SPOF. :-(
That is not the fault of the person providing the service. That is the fault of the sysops who rely on only that one single service. While he provides a DNS service, he is still indeed just a sysop like everyone
That is not the fault of the person providing the service. That is the
fault of the sysops who rely on only that one single service. While he
provides a DNS service, he is still indeed just a sysop like everyone
else.
It's still a spof. So maybe this could be an incentive to improve that?
The irc network was down too. If there were some more links between the different systems (fidoweb style ;)), that might not have happend...
Mine wasn't down, but my (and everyone else's) link to Rob's IRC service is/was. We can link our IRC service to any server we want, but most of us choose to use the default and link to Rob's system because it is, well.. the Synchronet IRC network.
With that said, if Rob really wanted to - he could setup all the services that are linkable at a hosting facility or something, where uptime wouldn't be affected if he himself were to move his systems and/or internet, but that's completely up to him and then more money is involved.
That is not the fault of the person providing the service. That is
the fault of the sysops who rely on only that one single service.
While he provides a DNS service, he is still indeed just a sysop
like everyone else.
It's still a spof. So maybe this could be an incentive to improve
that?
Improve it how? I use my *.synchro.net address for DNS updating only,
as well as some default settings that are used to connect to the synchro.net services. Otherwise I use my own paid for DNSs with free
ones as backups.
The irc network was down too. If there were some more links between
the different systems (fidoweb style ;)), that might not have
happend...
Mine wasn't down, but my (and everyone else's) link to Rob's IRC service is/was. We can link our IRC service to any server we want, but most of us choose to use the default and link to Rob's system because it is, well.. the Synchronet IRC network.
Would you rather me link my service to Freenode where BBS and/or Synchronet discussion is non-existant? :)
I could possibly see something in the lines of the Synchronet BBS list where everyone else's IRC servers are passed around to all connected systems so you basically have a list to choose from.. but as far as I know you can only link your IRC server to one other server at a time (which I don't think is Synchronet specific - that may be normal IRC operation).
When you connect to a new server, you disconnect from the previous
one. I don't think it's build like a client where you can connect to multiple servers at once, but I could be wrong..?
With that said, if Rob really wanted to - he could setup all the
services that are linkable at a hosting facility or something, where uptime wouldn't be affected if he himself were to move his systems
and/or internet, but that's completely up to him and then more money
is involved.
Personally, with how much conversation actually goes on on IRC most of
the time (of course, there are times where there is quite a bit going
on as well, but not nearly as often), I don't really think it's much
of an issue losing the service while Rob moves. It will be back up shortly, and netsplits and idling will commence as usual. :)
Hi Nicholas,
On 2016-12-20 21:36:40, you wrote to Chad Sharp:
My system has not been able to connect to Vert in two days, and
now CVS, IRC, QWK, and Verts FTP are all down. Does anyone know
if they will be back up sometime soon?
You must have missed the announcement that DM was moving hiscable/internet
service to the new house today. It'll be back up as soon as he gets everything up and running again at the new place. So just hang tight.
Including his DNS servers, so everybody that uses a xxx.synchro.net hostname, is unreachable. Talking about a SPOF. :-(
You must have missed the announcement that DM was moving his cable/internet service to the new house today. It'll be back up as soon as he gets everything up and running again at the new place. So just hang tight.
Interestingly, my BBS is apparently still exchanging Dove-Net messages from VERT (I keep seeing new messages posted on Dove-Net). I know his systems are down, and his BBS web site at vert.synchro.net isn't loading, so I'm wondering how my BBS is able to connect & exchange Dove-Net messages right now.
kk4qbn wrote to Accession <=-
Yup, and the last I could remember no ones life ever depended on being able to contact a bbs :-) I coulnt tell much difference that the
You must have missed the announcement that DM was moving hiscable/internet
service to the new house today. It'll be back up as soon as he gets everything up and running again at the new place. So just hang tight.
Including his DNS servers, so everybody that uses a xxx.synchro.net hostname, is unreachable. Talking about a SPOF. :-(
There's a back-up DNS (dns2.synchro.net), not hosted by me, so hostnames should still have been resolving while I was down.
Digital Man wrote to Wilfred van Velzen <=-
Re: Re: Vert?
By: Wilfred van Velzen to Nicholas Boel on Wed Dec 21 2016 08:52 am
Hi Nicholas,
On 2016-12-20 21:36:40, you wrote to Chad Sharp:
My system has not been able to connect to Vert in two days, and
now CVS, IRC, QWK, and Verts FTP are all down. Does anyone know
if they will be back up sometime soon?
You must have missed the announcement that DM was moving hiscable/internet
service to the new house today. It'll be back up as soon as he gets everything up and running again at the new place. So just hang tight.
Including his DNS servers, so everybody that uses a xxx.synchro.net hostname, is unreachable. Talking about a SPOF. :-(
There's a back-up DNS (dns2.synchro.net), not hosted by me, so
hostnames should still have been resolving while I was down.
Including his DNS servers, so everybody that uses a xxx.synchro.net
hostname, is unreachable. Talking about a SPOF. :-(
There's a back-up DNS (dns2.synchro.net), not hosted by me, so hostnames should still have been resolving while I was down.
theMine wasn't down, but my (and everyone else's) link to Rob's IRC service
is/was. We can link our IRC service to any server we want, but most of us
choose to use the default and link to Rob's system because it is, well..
the Synchronet IRC network.
We could spread our IRC network around a bit more if we wanted to, but at
end of the day if Vert is down there's going to be a big netsplit. Most servers would be using the default configuration anyway.
services,With that said, if Rob really wanted to - he could setup all the services
that are linkable at a hosting facility or something, where uptime
wouldn't be affected if he himself were to move his systems and/or
internet, but that's completely up to him and then more money is involved.
I suppose an argument could be made for doing that with some of these
but I know that he likes running his own servers at home. I'm with you;it's
not something that happens often, and it's just BBS stuff. A few days ofoutage
(amidst years of fairly reliable service) isn't a big deal.
Re: DNS, it's any sysop's choice to go with the free SPOF vs. paying for something instead. And everyone loves FREE BBS SERVICES amirite?
i suspect he is/was talking about multiple DNS and possibly also Dynamic DomainDNS...
Update servers so that if the main synchro.net server(s) are down for some reason, then those addresses can still be updated and be accurate in the
the problem, such as it is, it the netsplits when the main server that everyone
is linked to is down... each system then becomes its own little puddleunless
the operators take steps to relink to other systems and join the puddles together to make a larger pond...
thatWould you rather me link my service to Freenode where BBS and/or
Synchronet discussion is non-existant? :)
if someone were to create the channels and maintain them, it might not be
way... the sticking point being the terms of service and all the bots...many
botnets use channels on the common IRC networks...
the things about clients being connected to multiple servers and being inthe
same channels is the duplicate users and that each channel window isseparate
from the others... i don't think you can bond or combine two #BBS channels
two different IRC servers within the client... you couldn't do that backthen,
anyway...
any idea how the move is going and when everything will be back online and fully operational? i see your post came through the vertrauen gateway into fidonet...
shouldIncluding his DNS servers, so everybody that uses a xxx.synchro.net
hostname, is unreachable. Talking about a SPOF. :-(
There's a back-up DNS (dns2.synchro.net), not hosted by me, so hostnames
still have been resolving while I was down.
i suspect he is/was talking about multiple DNS and possibly also
Dynamic Domain Update servers so that if the main synchro.net
server(s) are down for some reason, then those addresses can still be
updated and be accurate in the DNS...
Point is, Rob offers a free service. The rest of us choose to use it
or not, and also choose to have backup DNSs ourselves (or not).
the problem, such as it is, it the netsplits when the main server
that everyone
It was never a problem, IMO.
is linked to is down... each system then becomes its own little
puddle unless the operators take steps to relink to other systems and
join the puddles together to make a larger pond...
Or just wait the few days - that we were warned ahead of time about -
till the service is back up and operational again.
Would you rather me link my service to Freenode where BBS and/or
Synchronet discussion is non-existant? :)
if someone were to create the channels and maintain them, it might
not be that way... the sticking point being the terms of service and
all the bots... many botnets use channels on the common IRC
networks...
Hasn't been done as of yet,
and I don't really think there would be much of a point in doing so as
all it would really do is separate and divide what we've already established over the years. We had the same issue about a decade ago
with thebbs.org and others that tried setting up their own networks
for the same exact purpose. All it does is spread everyone out more
thin than it already is. Eventually we all came back together to form
one network and stick with it.
the things about clients being connected to multiple servers and
being in the same channels is the duplicate users and that each
channel window is separate from the others... i don't think you can
bond or combine two #BBS channels on two different IRC servers within
the client... you couldn't do that back then, anyway...
Exactly. Which is why I didn't really see a point in doing anything
except waiting for the services to be brought back. We had plenty of fore-warning what was going to happen and when.. so I wasn't concerned about it at all.
any idea how the move is going and when everything will be back
online and fully operational? i see your post came through the
vertrauen gateway into fidonet...
If you didn't catch it yet, I believe he announced that everything was back in full operation today, although there seemed to be spurts in
the past few days where I got mail via Vertrauen anyways (possibly due
to the DNS rotation of whatever sort he told me about once).
--- slrn/1.0.3 (Linux)
# Origin: thePharcyde_ distribution system (723:1/1)
* Synchronet * thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
* Origin: Vertrauen - vert.synchro.net (1:103/705)
You must have missed the announcement that DM was moving hiscable/internet
service to the new house today. It'll be back up as soon as he gets everything up and running again at the new place. So just hang tight.
Including his DNS servers, so everybody that uses a xxx.synchro.net hostname, is unreachable. Talking about a SPOF. :-(
There's a back-up DNS (dns2.synchro.net), not hosted by me, so hostnames should still have been resolving while I was down.
hmmm, you might add that to the dyndns.js file (after you get the ok first)
There's a back-up DNS (dns2.synchro.net), not hosted by me, so hostnames should still have been resolving while I was down.
just looked in the dyndns.js and that address was not listed in it... just added it just in case
Hi,
On 2016-12-24 12:25:10, Digital Man wrote to Wilfred van Velzen:
about: "Re: Vert?":
Including his DNS servers, so everybody that uses a xxx.synchro.net
hostname, is unreachable. Talking about a SPOF. :-(
There's a back-up DNS (dns2.synchro.net), not hosted by me, so hostnames should still have been resolving while I was down.
I don't think they were. I tried a couple of the *.synchro.net hostnames, and none resolved...?
mark lewis wrote to Nicholas Boel <=-
yup... i used to set up and maintain channels for remoteaccess but it
got to be such a hassle dealing with the different rules on the
different networks and no one else was showing up so finally i just
quit doing it... that and the fact that i moved from winwhatever so
wasn't able to use my registered mIRC with all of the scripts and protections i had worked on for so long...
yup... i used to set up and maintain channels for remoteaccess but it
got to be such a hassle dealing with the different rules on the
different networks and no one else was showing up so finally i just
quit doing it... that and the fact that i moved from winwhatever so
wasn't able to use my registered mIRC with all of the scripts and
protections i had worked on for so long...
Actually, mIRC runs perfectly well under WINE on both Linux and Mac
(I've done it), so ditching Windows doesn't mean ditching mIRC. My
mIRC setup that I've had since the late 90s (with numerous upgrades,
of course) last ran under WINE on the Mac. I have to copy it across
to the current Windows box one of these days. :)
mark lewis wrote to Tony Langdon <=-
hell, i might try it then... but that means putting wine on the
system... then to also figure out how to import my registration keys...
i don't know... maybe...
Then there's something wrong with your DNS client configuration? DNS2.SYNCHRO.NET is clearly listed as a name server for the synchro.net domain and was up the whole time: http://www.whois.com/whois/synchro.net
there must be something wrong with everybodys. While you were gone DM, no ones *.Synchro.net address worked, most of the boards on my syncterm were unconnectable and mine itself would not resolve. Luckily I had a backup at darktech.orgMy board was reachable the entire time.
there must be something wrong with everybodys. While you were gone DM, no ones *.Synchro.net address worked, most of the boards on my syncterm were unconnectable and mine itself would not resolve. Luckily I had a backup at darktech.org
My board was reachable the entire time.
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495939:06:27 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 286,966 |