16 Sep 14:35:24 [45224] created /var/spool/ftn/outb.015/000300z4.csy
16 Sep 14:35:24 [45224] call to 21:x/y00@fidonet
16 Sep 14:35:24 [45223] 21:x/y00@fsxnet busy, skipping
16 Sep 14:35:24 [45224] getaddrinfo failed: Name does not resolve (8)

Is there a reason you are obscuring the net/node number, or is it really showing up in the logs as 21:x/y00@fsxnet?

If it is really showing up with the x and the y in it, then I am pretty
sure that is your issue. Those should be numbers.

If you are obscuring them, I would suggest that maybe you use the node's
actual address instead of relying on the zone lookup. It could be down or
not otherwise functioning properly. There is also something
odd going on there with the second line showing '@fidonet' while the third correctly says '@fsxnet' but I am not sure what might be causing that.


* SLMR 2.1a * Do ministers do more than lay people?
--- SBBSecho 3.28-Linux
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)

Hello Mike!

17 Sep 25 09:36, you wrote to me:

At first I was changin those numbers for privacy. I finally solved the issue by commenting out the last line I had in binkf.conf that allowed to connect to unlisted destinations.

# Default node flags. Binkd will call an unlisted node if "defnode" is defined. #
#defnode -nd *

16 Sep 14:35:24 [45224] created /var/spool/ftn/outb.015/000300z4.csy
16 Sep 14:35:24 [45224] call to 21:x/y00@fidonet
16 Sep 14:35:24 [45223] 21:x/y00@fsxnet busy, skipping
16 Sep 14:35:24 [45224] getaddrinfo failed: Name does not resolve
(8)

Is there a reason you are obscuring the net/node number, or is it
really showing up in the logs as 21:x/y00@fsxnet?

If it is really showing up with the x and the y in it, then I am
pretty sure that is your issue. Those should be numbers.

If you are obscuring them, I would suggest that maybe you use the
node's actual address instead of relying on the zone lookup. It could
be down or not otherwise functioning properly. There is also
something odd going on there with the second line showing '@fidonet'
while the third correctly says '@fsxnet' but I am not sure what might
be causing that.

* SLMR 2.1a * Do ministers do more than lay people?
--- SBBSecho 3.28-Linux
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)

JAS


--- GoldED+/BSD 1.1.5-b20170303-b20170303 + HPT 1.9.0 + Binkd 1.1a-115
* Origin: FIDONODO DE JAS | ¯\_(O,O)_/¯ (4:900/733)

Hello Wilfred and JM!

18 Sep 25 18:31, you wrote to Joacim Melin:

LOL you are right, its something I just got used to do.

Hi Joacim,

On 2025-09-18 17:01:32, you wrote to JAS:

At first I was changin those numbers for privacy. I finally
solved the issue by commenting out the last line I had in
binkf.conf that allowed to connect to unlisted destinations.

16 Sep 14:35:24 [45224] call to 21:x/y00@fidonet

If you are obscuring them, I would suggest that maybe you use
the node's actual address instead of relying on the zone
lookup. It could be down or not otherwise functioning
properly. There is also something odd going on there with the
second line showing '@fidonet' while the third correctly says
'@fsxnet' but I am not sure what might be causing that.

You realize there is a nodelist and you will be in it? :)

He's obscuring who he is linking to in fsx net. I can't imagine that
is sensitive information, but it's up to him (and his link) to decide about that... ;-)

Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

JAS


--- GoldED+/BSD 1.1.5-b20170303-b20170303 + HPT 1.9.0 + Binkd 1.1a-115
* Origin: FIDONODO DE JAS | ¯\_(O,O)_/¯ (4:900/733)

Hi Joacim,

On 2025-09-18 17:01:32, you wrote to JAS:

At first I was changin those numbers for privacy. I finally solved the
issue by commenting out the last line I had in binkf.conf that allowed
to connect to unlisted destinations.

16 Sep 14:35:24 [45224] call to 21:x/y00@fidonet

If you are obscuring them, I would suggest that maybe you use the
node's actual address instead of relying on the zone lookup. It
could be down or not otherwise functioning properly. There is also
something odd going on there with the second line showing '@fidonet'
while the third correctly says '@fsxnet' but I am not sure what
might be causing that.

You realize there is a nodelist and you will be in it? :)

He's obscuring who he is linking to in fsx net. I can't imagine that is sensitive information, but it's up to him (and his link) to decide about that... ;-)


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

At first I was changin those numbers for privacy. I finally solved the issue b
commenting out the last line I had in binkf.conf that allowed to connect to unlisted destinations.

# Default node flags. Binkd will call an unlisted node if "defnode" is defined
#
#defnode -nd *

Good catch! Glad you fixed it.

Mike


* SLMR 2.1a * You are now entering a School Free Drug Zone.
--- SBBSecho 3.28-Linux
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)

Hello Mike!

17 Sep 25 09:36, you wrote to me:

At first I was changin those numbers for privacy. I finally solved the issue by commenting out the last line I had in binkf.conf that allowed
to connect to unlisted destinations.

# Default node flags. Binkd will call an unlisted node if "defnode" is defined.
#
#defnode -nd *

16 Sep 14:35:24 [45224] created /var/spool/ftn/outb.015/000300z4.csy
16 Sep 14:35:24 [45224] call to 21:x/y00@fidonet
16 Sep 14:35:24 [45223] 21:x/y00@fsxnet busy, skipping
16 Sep 14:35:24 [45224] getaddrinfo failed: Name does not resolve
(8)

Is there a reason you are obscuring the net/node number, or is it
really showing up in the logs as 21:x/y00@fsxnet?

If it is really showing up with the x and the y in it, then I am
pretty sure that is your issue. Those should be numbers.

If you are obscuring them, I would suggest that maybe you use the
node's actual address instead of relying on the zone lookup. It could
be down or not otherwise functioning properly. There is also
something odd going on there with the second line showing '@fidonet'
while the third correctly says '@fsxnet' but I am not sure what might
be causing that.

You realize there is a nodelist and you will be in it? :)


--- NiKom v2.6.0
* Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:221/242.0)