24 hours ago my synchronet bbs v 3.19b stopped connecting to FSXnet. I have made no changes or updates to SBBS. I have rebooted my PC and still get this message. I am running windows 10 64b. This has all been working great up until 24 hours ago when SBBS stopped making a polling connection with FSXnet.
Here is my Poll Log:

10/27 09:58:52a BINKPOLL Running timed event: BINKPOLL
10/27 09:58:52a BINKPOLL BinkIT/2.41 invoked with options: -p
10/27 09:58:52a BINKPOLL Attempting poll for node 21:1/100@fsxnet
10/27 09:58:52a BINKPOLL JSBinkP/4 callout to 21:1/100@fsxnet started
10/27 09:58:52a BINKPOLL Connecting to 21:1/100@fsxnet at f100.n1.z21.fsxnet.nz:24554
10/27 09:58:56a BINKPOLL Connection to f100.n1.z21.fsxnet.nz:24554 failed (Error: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server. ).
10/27 09:58:56a BINKPOLL Timed event: BINKPOLL returned 0

Any advice would be greatly appreciated. I enjoy FSXnet. Have a great weekend all.

Rixter
ricksbbs.synchro.net:23
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (21:1/183)

24 hours ago my synchronet bbs v 3.19b stopped connecting to FSXnet. I have made no changes or updates to SBBS. I have rebooted my PC and still get this message. I am running windows 10 64b. This has all been working great up until 24 hours ago when SBBS stopped making a polling
connection with FSXnet. Here is my Poll Log:

10/27 09:58:52a BINKPOLL Running timed event: BINKPOLL
10/27 09:58:52a BINKPOLL BinkIT/2.41 invoked with options: -p
10/27 09:58:52a BINKPOLL Attempting poll for node 21:1/100@fsxnet
10/27 09:58:52a BINKPOLL JSBinkP/4 callout to 21:1/100@fsxnet started
10/27 09:58:52a BINKPOLL Connecting to 21:1/100@fsxnet at f100.n1.z21.fsxnet.nz:24554
10/27 09:58:56a BINKPOLL Connection to f100.n1.z21.fsxnet.nz:24554 failed (Error: This is usually a temporary error during hostname resolution and means that the local server did not receive a response
from an authoritative server. ).
10/27 09:58:56a BINKPOLL Timed event: BINKPOLL returned 0

The hostname you should be connecting to is agency.bbs.nz - if that is what you have configured, are you able to ping it?

It should reply with the IP address of 103.193.138.76

--- Mystic BBS v1.12 A48 (Windows/32)
* Origin: bbs.CabanaBar.net:11123 (21:1/246)

The hostname you should be connecting to is agency.bbs.nz - if that is what you have configured, are you able to ping it?

It should reply with the IP address of 103.193.138.76

--- Mystic BBS v1.12 A48 (Windows/32)
* Origin: bbs.CabanaBar.net:11123 (21:1/246)

Thank you for replying. I could not ping it but now I can and it is working again. I had to do nothing but wait a few days. Have a good weekend.

telnet://ricksbbs.synchro.net:23
http://ricksbbs.synchro.net:8080
Madison,NC

Hello Rixter!

On 27 Oct 2024, Rixter said the following...

24 hours ago my synchronet bbs v 3.19b stopped connecting to FSXnet. I have made no changes or updates to SBBS. I have rebooted my PC and still get this message. I am running windows 10 64b. This has all been working

I noticed something similar -- that my binkd, at least during incoming sessions (e.g. when Avon's machine connects to my binkd), appeared to get the connections cut off:

binkd.1:? 26 Oct 03:16:35 [2561622] recv: connection closed by foreign host

After some network sniffing it appears that my binkd tries to resolve all remote AKAs (which are quite many!) into IPs using the fsxnet.nz translation feature, and those DNS requests fail (timeout) for some reason. I'm guessing Avon's system then got tired of waiting for my binkd, and hence closed the connection.

A temporary workaround here was to disable the DNS lookups by changing:
domain fsxnet /mnt/bbs/echomail/out/fsxnet 21 fsxnet.nz
...to:
domain fsxnet /mnt/bbs/echomail/out/fsxnet 21 othernet.nodnslookup
...in binkd.cfg so that it tries to use a non-existent lookup service (instead of the fsxnet.nz lookup service), and hence fails immediately, and skips the translation. (The lookups aren't that important as all new nodes should end up in the nodelist after a week or so.)

In your case -- try changing f100.n1.z21.fsxnet.nz:24554 to net1.fsxnet.nz:24554 if possible. I believe those two should be interchangeable.

Best regards
Zip

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)