Hey all. So the concensus seems to be Vert is up and running and has no issues. I'm onboard with that, because I AM, after all, recieving my DoveNet feed.

The issue is, I'm still experiencing dyndns.js failure. One suggestion was to check to see if my account was still active by using my QWK account to ftp into Vert. I did. It worked, so the account seems to still be valid. The other suggestion was to run the dyndns.js routine from the command line. I did, saw no indications of error or failure.

Here's the output of the dyndns.js routine:
root@thelostchord:/sbbs/exec# ./jsexec dyndns.js <password> -mx mail.synchro.net

JSexec v3.17b-Linux (rev 1.201) - Execute Synchronet JavaScript Module
Compiled Feb 26 2020 20:44:08 with GCC 9.2.1

Loading configuration files from /sbbs/ctrl
JavaScript-C 1.8.5 2011-03-31
JavaScript: Creating runtime: 8388608 bytes
JavaScript: Initializing context (stack: 16384 bytes)

Reading script from /sbbs/exec/dyndns.js
/sbbs/exec/dyndns.js compiled in 0.00 seconds
Synchronet Dynamic DNS Client 1.15
id?
TLCBBS
pw?
<password>
ip?

ttl?

mx?
mail.synchro.net
ip6?

txt?

loc?

wc?

ok

/sbbs/exec/dyndns.js executed in 4.70 seconds

JavaScript: Destroying context
JavaScript: Destroying runtime
root@thelostchord:/sbbs/exec#
root@thelostchord:/sbbs/exec#

Question. What's the next troubleshooting step? My IP address when I ping the board is NOT the same as the public IP on my router. Is there any way of seeing what IP address dyndns.js is sending to the dns server? I don't know at this point if the problem is on my router or the ISP or at Vert. Locally everything is working. If I telnet in to the public IP address listed on my router the BBS responds normally. This is a puzzle and somewhat more confounding when I can only see one end of the transaction.

Any info or insight would be greatly appreciated.

Thanks much...
-==*>Weatherman<*==-

---
þ Synchronet þ The Lost Chord BBS - Cheyenne, WY

Hey all. So the concensus seems to be Vert is up and running and has no issues. I'm onboard with that, because I AM, after all, recieving my DoveNet feed.

The issue is, I'm still experiencing dyndns.js failure. One suggestion was to check to see if my account was still active by using my QWK account to ftp into Vert. I did. It worked, so the account seems to still be valid. The other suggestion was to run the dyndns.js routine from the command line. I did, saw no indications of error or failure.

Here's the output of the dyndns.js routine:
root@thelostchord:/sbbs/exec# ./jsexec dyndns.js <password> -mx mail.synchro.net

JSexec v3.17b-Linux (rev 1.201) - Execute Synchronet JavaScript Module Compiled Feb 26 2020 20:44:08 with GCC 9.2.1

Loading configuration files from /sbbs/ctrl
JavaScript-C 1.8.5 2011-03-31
JavaScript: Creating runtime: 8388608 bytes
JavaScript: Initializing context (stack: 16384 bytes)

Reading script from /sbbs/exec/dyndns.js
/sbbs/exec/dyndns.js compiled in 0.00 seconds
Synchronet Dynamic DNS Client 1.15
id?
TLCBBS
pw?
<password>
ip?

ttl?

mx?
mail.synchro.net
ip6?

txt?

loc?

wc?

ok

/sbbs/exec/dyndns.js executed in 4.70 seconds

JavaScript: Destroying context
JavaScript: Destroying runtime
root@thelostchord:/sbbs/exec#
root@thelostchord:/sbbs/exec#

Question. What's the next troubleshooting step? My IP address when I ping the board is NOT the same as the public IP on my router. Is there any way of seeing what IP address dyndns.js is sending to the dns server? I don't know at this point if the problem is on my router or the ISP or at Vert. Locally everything is working. If I telnet in to the public IP address listed on my router the BBS responds normally. This is a puzzle and somewhat more confounding when I can only see one end of the transaction.

Any info or insight would be greatly appreciated.

Thanks much...
-==*>Weatherman<*==-

Pinging tlcbbs.synchro.net [66.201.137.183] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 66.201.137.183:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

did you ensure that you have the appropriate ports forwarded on your router and open/listening on your host system?

try checking here: http://vert.synchro.net/scanmyports.ssjs
and here: https://www.grc.com/x/ne.dll?bh0bkyd2 (Gibson Research Sheilds Up)

Hope this helps some ..

~Mortifis

---
þ Synchronet þ posted via alleycat etrucker-runemaster web ui

Mortifis wrote to Weatherman <=-

Hey all. So the concensus seems to be Vert is up and running and has no issues. I'm onboard with that, because I AM, after all, recieving my DoveNet feed.

The issue is, I'm still experiencing dyndns.js failure. One suggestion was to check to see if my account was still active by using my QWK account to ftp into Vert. I did. It worked, so the account seems to still be valid. The other suggestion was to run the dyndns.js routine from the command line. I did, saw no indications of error or failure.

Here's the output of the dyndns.js routine:
root@thelostchord:/sbbs/exec# ./jsexec dyndns.js <password> -mx mail.synchro.net

JSexec v3.17b-Linux (rev 1.201) - Execute Synchronet JavaScript Module Compiled Feb 26 2020 20:44:08 with GCC 9.2.1

Loading configuration files from /sbbs/ctrl
JavaScript-C 1.8.5 2011-03-31
JavaScript: Creating runtime: 8388608 bytes
JavaScript: Initializing context (stack: 16384 bytes)

Reading script from /sbbs/exec/dyndns.js
/sbbs/exec/dyndns.js compiled in 0.00 seconds
Synchronet Dynamic DNS Client 1.15
id?
TLCBBS
pw?
<password>
ip?

ttl?

mx?
mail.synchro.net
ip6?

txt?

loc?

wc?

ok

/sbbs/exec/dyndns.js executed in 4.70 seconds

JavaScript: Destroying context
JavaScript: Destroying runtime
root@thelostchord:/sbbs/exec#
root@thelostchord:/sbbs/exec#

Question. What's the next troubleshooting step? My IP address when I ping the board is NOT the same as the public IP on my router. Is there any way of seeing what IP address dyndns.js is sending to the dns server? I don't know at this point if the problem is on my router or the ISP or at Vert. Locally everything is working. If I telnet in to the public IP address listed on my router the BBS responds normally. This is a puzzle and somewhat more confounding when I can only see one end of the transaction.

Any info or insight would be greatly appreciated.

Thanks much...
-==*>Weatherman<*==-

Pinging tlcbbs.synchro.net [66.201.137.183] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 66.201.137.183:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

did you ensure that you have the appropriate ports forwarded on your router and open/listening on your host system?

try checking here: http://vert.synchro.net/scanmyports.ssjs
and here: https://www.grc.com/x/ne.dll?bh0bkyd2 (Gibson Research
Sheilds Up)

Hope this helps some ..

Mortifis,

Thanks for the reply. Yeah, all the required/suggested ports are open and
being forwarded to the BBS server. Verified that with the scanmyports link you sent. The BBS is certainly listening on those ports as it works perfectly well when I http or telnet in using the LAN private IP address as well as when I manually use my public IP address from the WAN side of the router. I could send you the IP address and you'd be able to ping/connect with no issue. The only problem I'm having is getting the domain name to resolve to the correct IP address. For some reason it's just not registering. This is a very strange as it HAD been working for several months prior to this. The domain name is resolving to 66.201.137.183, yet the actual public IP address is
72.55.211.127. Very strange. I saw in the documentation for dyndns.js that there's a way of manually inputting an IP address. I'll try that as a work-around and see if that gives me any result.

Thanks for the reply!
-==*>Weatherman<*==-

... The number you have dialed...Nine-one-one...has been changed.
--- MultiMail/Linux v0.49
þ Synchronet þ The Lost Chord BBS - Cheyenne, WY

Re: Re: Troubleshoot dyndns.j
By: Weatherman to Mortifis on Wed Jul 29 2020 11:18 pm

My DynDNS is also down. I also noticed that the sbbs list hasn't been updated since Saturday (the 25th) so I just assumed something is up with Vertrauen at the moment...

http://www.synchro.net/sbbslist.html

---
þ Synchronet þ t0kerZ hUt

Mortifis wrote to Weatherman <=-

Pinging tlcbbs.synchro.net [66.201.137.183] with 32 bytes of data: Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 66.201.137.183:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

did you ensure that you have the appropriate ports forwarded on your router and open/listening on your host system?

try checking here: http://vert.synchro.net/scanmyports.ssjs
and here: https://www.grc.com/x/ne.dll?bh0bkyd2 (Gibson Research Sheilds Up)

Hope this helps some ..

Mortifis,

Thanks for the reply. Yeah, all the required/suggested ports are open and
being forwarded to the BBS server. Verified that with the scanmyports link you sent. The BBS is certainly listening on those ports as it works perfectly well when I http or telnet in using the LAN private IP address as well as when I manually use my public IP address from the WAN side of the router. I could send you the IP address and you'd be able to ping/connect with no issue. The only problem I'm having is getting the domain name to resolve to the correct IP address. For some reason it's just not registering. This is a very strange as it HAD been working for several months prior to this. The domain name is resolving to 66.201.137.183, yet the actual public IP address is
72.55.211.127. Very strange. I saw in the documentation for dyndns.js that there's a way of manually inputting an IP address. I'll try that as a work-around and see if that gives me any result.

Thanks for the reply!
-==*>Weatherman<*==-

ya, I am not sure what the issue you're experiencing is. when I ping tlcbbs.synchro.net it still shows as 66.201.137.183 ... and when I ping, telnet or http 72.55.211.127 there is no response. did you try the grc link I sent?

~mortifis

---
þ Synchronet þ posted via alleycat etrucker-runemaster web ui

Crushed wrote to Weatherman <=-

My DynDNS is also down. I also noticed that the sbbs list hasn't been updated since Saturday (the 25th) so I just assumed something is up
with Vertrauen at the moment...

http://www.synchro.net/sbbslist.html

Well, good to know that I'm not alone, but concerned that there may be a bigger problem afoot. Good to know that there's a good chance the problem isn't on my end or with my ISP... Guess I'm just an emotional wreck about this. ;)

Thanks for adding to the information pool regarding this. All the knowledge does help narrow down the problem...

Regards,
-==*>Weatherman<*==-

... Got my tie caught in the fax... Suddenly I was in L.A.
--- MultiMail/Linux v0.49
þ Synchronet þ The Lost Chord BBS - Cheyenne, WY

Mortifis wrote to Weatherman <=-

@VIA: VERT/EPHRAM
@MSGID: <5F24485E.507.dove-ops@ephram.synchro.net>
@REPLY: <5F2258C9.330.dove-ops@tlcbbs.synchro.net>
@TZ: c0f0

Mortifis wrote to Weatherman <=-

Pinging tlcbbs.synchro.net [66.201.137.183] with 32 bytes of data: Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 66.201.137.183:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

did you ensure that you have the appropriate ports forwarded on your router and open/listening on your host system?

try checking here: http://vert.synchro.net/scanmyports.ssjs
and here: https://www.grc.com/x/ne.dll?bh0bkyd2 (Gibson Research Sheilds Up)

Hope this helps some ..

Mortifis,

Thanks for the reply. Yeah, all the required/suggested ports are open and
being forwarded to the BBS server. Verified that with the scanmyports link you sent. The BBS is certainly listening on those ports as it works perfectly well when I http or telnet in using the LAN private IP address as well as when I manually use my public IP address from the WAN side of the router. I could send you the IP address and you'd be able to ping/connect with no issue. The only problem I'm having is getting the domain name to resolve to the correct IP address. For some reason it's just not registering. This is a very strange as it HAD been working for several months prior to this. The domain name is resolving to 66.201.137.183, yet the actual public IP address is
72.55.211.127. Very strange. I saw in the documentation for dyndns.js that there's a way of manually inputting an IP address. I'll try that as a work-around and see if that gives me any result.

Thanks for the reply!
-==*>Weatherman<*==-

ya, I am not sure what the issue you're experiencing is. when I ping tlcbbs.synchro.net it still shows as 66.201.137.183 ... and when I
ping, telnet or http 72.55.211.127 there is no response. did you try
the grc link I sent?

~mortifis

Good chance that you pinged/telnet/http to address 72.55.211.127 after my IP address changed. On top of the issue with the dyndns service, my uplink to my ISP has been unstable and has resulted in my having a new IP address every couple of days, daily, sometimes multiple times a day - which underscores how much I rely on the dyndns service. Point to point wireless broaband is such fun, particularly when you live in an area prone to rather interesting thunderstorm activity. For example, today I'm on my THIRD IP address of the day, 66.201.130.23.

I accessed both the GRC and the "scanmyports" URLs. Both essentially said the same thing, that is that the required ports are open on the firewall and being redirected to the BBS server. Someone else has said they too are experiencing issues, and that the bbs list hasn't been updated in quite some time. Perhaps the two are related...

Regards,
-==*>Weatherman<*==-

... MultiMail, the new multi-platform, multi-format offline reader!
--- MultiMail/Linux v0.49
þ Synchronet þ The Lost Chord BBS - Cheyenne, WY

Re: Re: Troubleshoot dyndns.j
By: Weatherman to Mortifis on Fri Jul 31 2020 23:44:00

and that the bbs list hasn't been updated in quite some time. Perhaps
the two are related...

i kinda doubt it but it may be possible... especially if scheduled tasks aren't being performed... but the bbs list was updated today, Aug 1st...

"List of Synchronet BBSes (151 systems) exported from Vertrauen on Sat Aug 01 2020 01:08:11 GMT-0700 (Pacific Daylight Time)"

<strike>unfortunately, i don't seem to find an entry for your system...</strike>
belay that... i was confusing your system with one in the north east...


)\/(ark

---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR

Mortifis wrote to Weatherman <=-

@VIA: VERT/EPHRAM
@MSGID: <5F24485E.507.dove-ops@ephram.synchro.net>
@REPLY: <5F2258C9.330.dove-ops@tlcbbs.synchro.net>
@TZ: c0f0

Mortifis wrote to Weatherman <=-

Pinging tlcbbs.synchro.net [66.201.137.183] with 32 bytes of data: Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 66.201.137.183:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

did you ensure that you have the appropriate ports forwarded on your router and open/listening on your host system?

try checking here: http://vert.synchro.net/scanmyports.ssjs
and here: https://www.grc.com/x/ne.dll?bh0bkyd2 (Gibson Research Sheilds Up)

Hope this helps some ..

Mortifis,

Thanks for the reply. Yeah, all the required/suggested ports are open and
being forwarded to the BBS server. Verified that with the scanmyports link you sent. The BBS is certainly listening on those ports as it works perfectly well when I http or telnet in using the LAN private IP address as well as when I manually use my public IP address from the WAN side of the router. I could send you the IP address and you'd be able to ping/connect with no issue. The only problem I'm having is getting the domain name to resolve to the correct IP address. For some reason it's just not registering. This is a very strange as it HAD been working for several months prior to this. The domain name is resolving to 66.201.137.183, yet the actual public IP address is
72.55.211.127. Very strange. I saw in the documentation for dyndns.js that there's a way of manually inputting an IP address. I'll try that as a work-around and see if that gives me any result.

Thanks for the reply!

-==*>Weatherman<*==-

ya, I am not sure what the issue you're experiencing is. when I ping tlcbbs.synchro.net it still shows as 66.201.137.183 ... and when I ping, telnet or http 72.55.211.127 there is no response. did you try the grc link I sent?

~mortifis

Good chance that you pinged/telnet/http to address 72.55.211.127 after my IP address changed. On top of the issue with the dyndns service, my uplink to my ISP has been unstable and has resulted in my having a new IP address every couple of days, daily, sometimes multiple times a day - which underscores how much I rely on the dyndns service. Point to point wireless broaband is such fun, particularly when you live in an area prone to rather interesting thunderstorm activity. For example, today I'm on my THIRD IP address of the day, 66.201.130.23.

I accessed both the GRC and the "scanmyports" URLs. Both essentially said the same thing, that is that the required ports are open on the firewall and being redirected to the BBS server. Someone else has said they too are experiencing issues, and that the bbs list hasn't been updated in quite some time. Perhaps the two are related...

Regards,
-==*>Weatherman<*==-

so, Pinging tlcbbs.synchro.net [66.201.137.183] with 32 bytes of data:
Reply from 66.201.137.183: bytes=32 time=77ms TTL=52

what is your current public IP address? What ports are your telnet, ssh and http listening on?

SBBSLIST was updated this morning Sat Aug 01 2020 01:08:11 GMT-0700 (Pacific Daylight Time)

Also, what exactly does your modopts.ini [dyndns] look like?

~Mortifis

---
þ Synchronet þ posted via alleycat etrucker-runemaster web ui

Mortifis wrote to Weatherman <=-

I accessed both the GRC and the "scanmyports" URLs. Both essentially said the same thing, that is that the required ports are open on the firewall and being redirected to the BBS server. Someone else has said they too are experiencing issues, and that the bbs list hasn't been updated in quite some time. Perhaps the two are related...

Regards,
-==*>Weatherman<*==-

Digital Man did some fix'n, you should be good to go now .. I connected to tlcbbs.synchro.net ... reported as SBBS v3.17 Linux

~Mortifis

---
þ Synchronet þ posted via alleycat etrucker-runemaster web ui

Re: Troubleshoot dyndns.js service
By: Weatherman to All on Tue Jul 28 2020 09:58 am

Question. What's the next troubleshooting step? My IP address when I ping the board is NOT the same as the public IP on my router.

Thanks, that's been fixed today.

The root-cause was that the sysop of tccbbs.synchro.net specified an invalid LOC record in their dyndns configuration which propagated to the synchro.net.zone file which bind (named) then refused to load due to the invalid record. I'll work on better notification (of me) and validation of sysop-supplied data.


digital man

This Is Spinal Tap quote #7:
Nigel Tufnel: That's just nitpicking, isn't it?
Norco, CA WX: 94.7øF, 31.0% humidity, 6 mph ENE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Hey all.
Here's the output of the dyndns.js routine:
root@thelostchord:/sbbs/exec# ./jsexec dyndns.js <password> -mx mail.synchro.net

JSexec v3.17b-Linux (rev 1.201) - Execute Synchronet JavaScript Module Compiled Feb 26 2020 20:44:08 with GCC 9.2.1

Loading configuration files from /sbbs/ctrl

so now that you're dns issues are solved ... a few others you may not have noticed yet have been addressed, so, perhaps consider updating to 3.18a :)

---
þ Synchronet þ posted via alleycat etrucker-runemaster web ui

Mortifis wrote to Weatherman <=-

<<Snippage has occurred>>

so, Pinging tlcbbs.synchro.net [66.201.137.183] with 32 bytes of data: Reply from 66.201.137.183: bytes=32 time=77ms TTL=52

what is your current public IP address? What ports are your telnet,
ssh and http listening on?

SBBSLIST was updated this morning Sat Aug 01 2020 01:08:11 GMT-0700 (Pacific Daylight Time)

Also, what exactly does your modopts.ini [dyndns] look like?

~Mortifis

---

Mortifis,
My current IP address is 64.184.227.91, and this is probably the third IP
address I've had so far in the past 24 hours. My ISP truly sucks, unfortunately it's the only game in the neighborhood at this time.
My telnet port is 23, http is 80, ssh is 22. These are the ports that I'm
forwarding from my router to the BBS server. I used to have non-standard ports on the router forwarded to standard ports on the BBS, but that was in another time and on completely different equipment. This time around I tried to keep everything standard.
Regarding the modopts.ini file, I have no dyndns entry in it. The only option
I'm passing when I run that event is the -mx parameter and since it doesn't exceed the command line limits I have no need to include any options in the modopts.ini file.

Thanks for the inquiry....
Regards,
-==*>Weatherman<*==-

... DalekDOS v(overflow): (I)Obey (V)ision impaired (E)xterminate
--- MultiMail/Linux v0.49
þ Synchronet þ The Lost Chord BBS - Cheyenne, WY

Mortifis wrote to Weatherman <=-

I accessed both the GRC and the "scanmyports" URLs. Both essentially said the same thing, that is that the required ports are open on the firewall and being redirected to the BBS server. Someone else has said they too are experiencing issues, and that the bbs list hasn't been updated in quite some time. Perhaps the two are related...

Regards,
-==*>Weatherman<*==-

Digital Man did some fix'n, you should be good to go now .. I connected
to tlcbbs.synchro.net ... reported as SBBS v3.17 Linux

~Mortifis

---

Mortifis,
That's awesome! I see down the list that there's a mesage from the D-Man
himself. Looking forward to see what it is that is the magic that he worked. Life is definitely good again!

Regards,
-==*>Weatherman<*==-

... Internal Error: The system has been taken over by sheep at line 19960
--- MultiMail/Linux v0.49
þ Synchronet þ The Lost Chord BBS - Cheyenne, WY

Digital Man wrote to Weatherman <=-

@VIA: VERT
@MSGID: <5F25C5EE.16254.dove-sys@vert.synchro.net>
@REPLY: <5F204B43.326.dove-ops@tlcbbs.synchro.net>
@TZ: c1e0
Re: Troubleshoot dyndns.js service
By: Weatherman to All on Tue Jul 28 2020 09:58 am

Question. What's the next troubleshooting step? My IP address when I ping the board is NOT the same as the public IP on my router.

Thanks, that's been fixed today.

The root-cause was that the sysop of tccbbs.synchro.net specified an invalid LOC record in their dyndns configuration which propagated to
the synchro.net.zone file which bind (named) then refused to load due
to the invalid record. I'll work on better notification (of me) and validation of sysop-supplied data.

digital man

Awesome. Thanks! I probably should have contacted you directly, but I figured that I would use this as a learning experience to try to trouble shoot this kind of issue and maybe learn a bit about how the dyndns service worked. Looks like a classic fat-finger scenario from a SysOp of a board with a very similar URL to mine. Appreciate you stepping in and fixing the issue. I'm now going to navigate over to tccbbs.synchro.net and check his system out. ;)

Thanks again!
-==*>Weatherman<*==-

... He does the work of 3 Men...Moe, Larry & Curly
--- MultiMail/Linux v0.49
þ Synchronet þ The Lost Chord BBS - Cheyenne, WY

Re: Troubleshoot dyndns.js se
By: Weatherman to Digital Man on Sun Aug 02 2020 12:53 am

Question. What's the next troubleshooting step? My IP address when I ping the board is NOT the same as the public IP on my router.

Thanks, that's been fixed today.

The root-cause was that the sysop of tccbbs.synchro.net specified an invalid LOC record in their dyndns configuration which propagated to the synchro.net.zone file which bind (named) then refused to load due to the invalid record. I'll work on better notification (of me) and validation of sysop-supplied data.

Awesome. Thanks! I probably should have contacted you directly, but I figured that I would use this as a learning experience to try to trouble shoot this kind of issue and maybe learn a bit about how the dyndns service worked. Looks like a classic fat-finger scenario from a SysOp of a board with a very similar URL to mine. Appreciate you stepping in and fixing the issue. I'm now going to navigate over to tccbbs.synchro.net and check his system out. ;)

The fact that your hostnames are similar wasn't a factor however. His invalid LOC record affected all subsequent updates to the synchro.net zone file, for everyone. :-(

digital man

Synchronet "Real Fact" #71:
The largest dial-up Synchronet BBS was The Easy Street BBS with 25 nodes/lines. Norco, CA WX: 86.0øF, 43.0% humidity, 1 mph WSW wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Troubleshoot dyndns.js se
By: Digital Man to Weatherman on Sun Aug 02 2020 10:21:12

Re: Troubleshoot dyndns.js se

Question. What's the next troubleshooting step? My IP address when I ping the board is NOT the same as the public IP on
my
router.

Thanks, that's been fixed today.

The root-cause was that the sysop of tccbbs.synchro.net specified an invalid LOC record in their dyndns configuration
which
propagated to the synchro.net.zone file which bind (named) then refused to load due to the invalid record. I'll work on
better notification (of me) and validation of sysop-supplied data.

Awesome. Thanks! I probably should have contacted you directly, but I figured that I would use this as a learning
experience
to try to trouble shoot this kind of issue and maybe learn a bit about how the dyndns service worked. Looks like a classic
fat-finger scenario from a SysOp of a board with a very similar URL to mine. Appreciate you stepping in and fixing the
issue.
I'm now going to navigate over to tccbbs.synchro.net and check his system out. ;)

The fact that your hostnames are similar wasn't a factor however. His invalid LOC record affected all subsequent updates to the
synchro.net zone file, for everyone. :-(

digital man

Synchronet "Real Fact" #71:
The largest dial-up Synchronet BBS was The Easy Street BBS with 25 nodes/lines. Norco, CA WX: 86.0øF, 43.0% humidity, 1 mph WSW
wind, 0.00 inches rain/24hrs

Sorry about that I never know that I was cause that problem I have removed my LOC information dyndns section in modopts.ini. While on that subject the LOC of dyndns I check on the link that you have listed in the wiki to dnsloc.net and copied the number 39 17 28.927 N 80 16 32.203 W do I need to also copy 343m 10m 100m 10m?

Toolman (Tim Taylor)

---
þ Synchronet þ synchronet | ssh or Telnet bbs.tccbbs.com | Bridgeport, WV. | TCCBBS

Re: Troubleshoot dyndns.js se
By: Toolman to Digital Man on Sun Aug 02 2020 11:06 pm

Re: Troubleshoot dyndns.js se
By: Digital Man to Weatherman on Sun Aug 02 2020 10:21:12

Re: Troubleshoot dyndns.js se

Question. What's the next troubleshooting step? My IP address when I ping the board is NOT the same as the public IP on my router.

Thanks, that's been fixed today.

The root-cause was that the sysop of tccbbs.synchro.net specified an invalid LOC record in their dyndns configuration which propagated to the synchro.net.zone file which bind (named) then refused to load due to the invalid record. I'll work on better notification (of me) and validation of sysop-supplied data.

Awesome. Thanks! I probably should have contacted you directly, but I figured that I would use this as a learning experience
to try to trouble shoot this kind of issue and maybe learn a bit about how the dyndns service worked. Looks like a classic fat-finger scenario from a SysOp of a board with a very similar URL to mine. Appreciate you stepping in and fixing the issue.
I'm now going to navigate over to tccbbs.synchro.net and check his system out. ;)

The fact that your hostnames are similar wasn't a factor however. His invalid LOC record affected all subsequent updates to the synchro.net zone file, for everyone. :-(

digital man

Synchronet "Real Fact" #71:
The largest dial-up Synchronet BBS was The Easy Street BBS with 25 nodes/lines. Norco, CA WX: 86.0øF, 43.0% humidity, 1 mph WSW wind, 0.00 inches rain/24hrs

Sorry about that I never know that I was cause that problem I have removed my LOC information dyndns section in modopts.ini. While on that subject the LOC of dyndns I check on the link that you have listed in the wiki to dnsloc.net and copied the number 39 17 28.927 N 80 16 32.203 W do I need to also copy 343m 10m 100m 10m?

Yes. The problem was that you had "N -80" for some reason.

digital man

Synchronet "Real Fact" #19:
The first Synchronet BBS (Vertrauen) went live in July of 1991 (replacing WWIV).
Norco, CA WX: 71.1øF, 74.0% humidity, 6 mph ENE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Mortifis wrote to Weatherman <=-

Loading configuration files from /sbbs/ctrl

so now that you're dns issues are solved ... a few others you may not
have noticed yet have been addressed, so, perhaps consider updating to 3.18a :)

---

I'll certainly put it on my project list.

-==*>Weatherman<*==-


... 2 + 2 = 5 for extremely large values of 2.
--- MultiMail/Linux v0.49
þ Synchronet þ The Lost Chord BBS - Cheyenne, WY

Digital Man wrote to Weatherman <=-

The fact that your hostnames are similar wasn't a factor however. His invalid LOC record affected all subsequent updates to the synchro.net
zone file, for everyone. :-(

digital man

Synchronet "Real Fact" #71:
The largest dial-up Synchronet BBS was The Easy Street BBS with 25 nodes/lines. Norco, CA WX: 86.0øF, 43.0% humidity, 1 mph WSW wind, 0.00 inches rain/24hrs

---

Gotcha. So then just "one of those weird coincedences" then...

-==*>Weatherman<*==-


... Computer Hacker wanted. Must have own axe.
--- MultiMail/Linux v0.49
þ Synchronet þ The Lost Chord BBS - Cheyenne, WY

Re: Troubleshoot dyndns.js se
By: Weatherman to Digital Man on Mon Aug 03 2020 12:57 am

Digital Man wrote to Weatherman <=-

The fact that your hostnames are similar wasn't a factor however. His invalid LOC record affected all subsequent updates to the synchro.net zone file, for everyone. :-(

Gotcha. So then just "one of those weird coincedences" then...

I suppose so. The problem was affecting everyone, though only those who actually had an IP address change during that period probably noticed.

digital man

Synchronet/BBS Terminology Definition #60:
RIP = Remote Imaging Protocol (e.g. RIPscrip)
Norco, CA WX: 64.1øF, 88.0% humidity, 0 mph S wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Troubleshoot dyndns.js se
By: Toolman to Digital Man on Sun Aug 02 2020 23:06:22


Toolman> Sorry about that I never know that I was cause that problem I
Toolman> have removed my LOC information dyndns section in modopts.ini.

you're not the first to have submitted invalid LOC record data ;)

Toolman> While on that subject the LOC of dyndns I check on the link
Toolman> that you have listed in the wiki to dnsloc.net and copied the
Toolman> number 39 17 28.927 N 80 16 32.203 W do I need to also copy
Toolman> 343m 10m 100m 10m?

not sure but maybe this will help?

https://tools.ietf.org/html/rfc1876

https://en.wikipedia.org/wiki/LOC_record



)\/(ark

---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR

On 7/30/2020 5:24 PM, Crushed wrote:

Re: Re: Troubleshoot dyndns.j
By: Weatherman to Mortifis on Wed Jul 29 2020 11:18 pm

My DynDNS is also down. I also noticed that the sbbs list hasn't been updated
since Saturday (the 25th) so I just assumed something is up with Vertrauen at the moment...

http://www.synchro.net/sbbslist.html

Just throwing this out there, you can use dns.afraid.org to get a
secondary dyndns address... I put bbs.io on there, so you could have YOUR.bbs.io

--
Michael J. Ryan
tracker1 +o Roughneck BBS

---
þ Synchronet þ Roughneck BBS - coming back 2/2/20

On 8/5/2020 3:15 PM, Tracker1 wrote:

On 7/30/2020 5:24 PM, Crushed wrote:

Re: Re: Troubleshoot dyndns.j
By: Weatherman to Mortifis on Wed Jul 29 2020 11:18 pm

My DynDNS is also down. I also noticed that the sbbs list hasn't been
updated
since Saturday (the 25th) so I just assumed something is up with
Vertrauen at
the moment...

http://www.synchro.net/sbbslist.html

Just throwing this out there, you can use dns.afraid.org to get a
secondary dyndns address... I put bbs.io on there, so you could have YOUR.bbs.io

sorry, freedns.afraid.org

--
Michael J. Ryan
tracker1 +o Roughneck BBS

---
­ Synchronet ­ Roughneck BBS - coming back 2/2/20