Hello everybody!

I've tried adding a secondary network, FSXNET, but when I write a netmail message, for example to Areafix I see in the logs that binkd tries to connect to my uplink but using @fidonet so I doesn't resolve the hostname. I tried in different ways as the FAQ mentions in 22 & 23 but I get the same results. I use hpt as tosser.

-+-
+ 16 Sep 08:01:55 [68337] call to 21:x/y00@fidonet
+ 16 Sep 08:01:55 [68337] getaddrinfo failed: Name does not resolve (8)

+ 16 Sep 08:02:56 [68519] call to 21:x/y00@fidonet
+ 16 Sep 08:02:56 [68519] getaddrinfo failed: Name does not resolve (8)

+ 16 Sep 08:03:56 [68707] call to 21:x/y00@fidonet
+ 16 Sep 08:03:56 [68707] getaddrinfo failed: Name does not resolve (8)
+ 16 Sep 08:03:56 [68707] holding 21:x/y00@fidonet (2025/09/16 08:13:56)
-+-

---binkd.conf---
[...]
#
domain fidonet /var/spool/ftn/outb 4 binkp.net
domain fsxnet /var/spool/ftn/outb 21 fsxnet.nz
address 4:900/733@fidonet
address 21:x/y00.z@fsxnet
[...]
-+-

---/var/spool/ftn---
fido:/var/spool/ftn$ ls -al out*
outb:
total 9
drwxrwx--- 2 fido fido 2 Sep 16 01:48 .
drwxrwx--- 13 fido fido 13 Sep 16 07:54 ..

outb.015:
total 15
drwxr-xr-x 3 fido fido 6 Sep 16 08:03 .
drwxrwx--- 13 fido fido 13 Sep 16 07:54 ..
-rw------- 1 fido fido 322 Sep 16 07:54 000300x4.cut
-rw-r--r-- 1 fido fido 10 Sep 16 08:03 000300x4.hld
drwxr-xr-x 2 fido fido 2 Sep 16 07:54 000300x4.sep
-rw-r--r-- 1 fido fido 23 Sep 16 08:03 000300x4.try

---hpt/fidoconfig---
[...]
address 4:900/733@fidonet
address 21:x/y00.z@fsxnet

inbound /var/spool/ftn/inb/unsecure
protinbound /var/spool/ftn/inb
outbound /var/spool/ftn/outb

tempinbound /var/spool/ftn/tmp/inb
tempoutbound /var/spool/ftn/tmp/outb

nodelistDir /var/spool/ftn/filebase/nodelist
[...]
-+-


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)

Re: How to add an additional network?
By: JAS to All on Tue Sep 16 2025 08:00 am

Howdy,

domain fidonet /var/spool/ftn/outb 4 binkp.net
domain fsxnet /var/spool/ftn/outb 21 fsxnet.nz
address 4:900/733@fidonet
address 21:x/y00.z@fsxnet

Maybe try without the domain name at the end of the "domain" statements.

Also, the "zone" ID (4,21) on the "domain" lines are not the zone's of the othernets, but it indicate what "zone" is your *primary* domain.

This needs to be consistent with your mail tosser.

If your mail tosser is putting fsxnet mail in /var/spool/ftn/outb.015, then you need to change binkd's configuration to have "4" for the fsxnet domain, not 21. (Assuming hpt is treating your "fidonet" AKA as your *primary* AKA - and thus it is packaging your fidonet mail to "/var/spool/ftn/outb")

...deon

...ëîåï
--- SBBSecho 3.27-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)

Hello deon!

16 Sep 25 22:45, you wrote to me:

HPT leaves the files in outb directory.
---hpt/config--- (fidoconfig)
[...]
inbound /var/spool/ftn/inb/unsecure
protinbound /var/spool/ftn/inb
outbound /var/spool/ftn/outb
[...]

I changed binkd.conf to both domains have 4 in the end.
[...]
domain fidonet /var/spool/ftn/outb 4
domain fsxnet /var/spool/ftn/outb 4
[...]

First it tries with the appropiate address and then switches to the other network and of course it would not resolve the hostname.

---binkd.log---
16 Sep 14:35:24 [45223] clientmgr started
16 Sep 14:35:24 [45222] created /var/run/binkd/binkd.pid
16 Sep 14:35:24 [45222] servmgr started
16 Sep 14:35:24 [45222] servmgr listen on *:24554
16 Sep 14:35:24 [45223] started client #1, id=45224
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)
16 Sep 14:35:24 [45224] unlinked `/var/spool/ftn/outb.015/000300z4.csy'
16 Sep 14:35:24 [45224] exitfunc()
16 Sep 14:35:24 [45224] bsy_remove_all: done
16 Sep 14:35:24 [45223] rc(45224)=0
16 Sep 14:36:24 [45223] started client #1, id=45413
16 Sep 14:36:24 [45223] 21:x/y00@fsxnet busy, skipping
16 Sep 14:36:24 [45413] created /var/spool/ftn/outb.015/000300z4.csy
16 Sep 14:36:24 [45413] call to 21:x/y00@fidonet
16 Sep 14:36:24 [45413] getaddrinfo failed: Name does not resolve (8)
16 Sep 14:36:24 [45413] unlinked `/var/spool/ftn/outb.015/000300z4.csy'
16 Sep 14:36:24 [45413] exitfunc()
16 Sep 14:36:24 [45413] bsy_remove_all: done
16 Sep 14:36:24 [45223] rc(45413)=0
16 Sep 14:37:24 [45223] started client #1, id=45601
16 Sep 14:37:24 [45223] 21:x/y00@fsxnet busy, skipping
16 Sep 14:37:24 [45601] created /var/spool/ftn/outb.015/000300z4.csy
16 Sep 14:37:24 [45601] call to 21:x/y00@fidonet
16 Sep 14:37:24 [45601] getaddrinfo failed: Name does not resolve (8)
16 Sep 14:37:24 [45601] unlinked `/var/spool/ftn/outb.015/000300z4.csy'
16 Sep 14:37:24 [45601] exitfunc()
16 Sep 14:37:24 [45601] bsy_remove_all: done
16 Sep 14:37:24 [45223] rc(45601)=0
16 Sep 14:38:24 [45223] started client #1, id=45789
16 Sep 14:38:24 [45223] 21:x/y00@fsxnet busy, skipping
16 Sep 14:38:24 [45789] created /var/spool/ftn/outb.015/000300z4.csy
16 Sep 14:38:24 [45789] call to 21:x/y00@fidonet
16 Sep 14:38:24 [45789] getaddrinfo failed: Name does not resolve (8)
16 Sep 14:38:24 [45789] holding 21:x/y00@fidonet (2025/09/16 14:48:24)
16 Sep 14:38:24 [45789] unlinked `/var/spool/ftn/outb.015/000300z4.csy'
16 Sep 14:38:24 [45789] exitfunc()
16 Sep 14:38:24 [45789] bsy_remove_all: done
16 Sep 14:38:24 [45223] rc(45789)=0---

Maybe try without the domain name at the end of the "domain"
statements.

Also, the "zone" ID (4,21) on the "domain" lines are not the zone's of
the othernets, but it indicate what "zone" is your *primary* domain.

This needs to be consistent with your mail tosser.

If your mail tosser is putting fsxnet mail in /var/spool/ftn/outb.015, then you need to change binkd's configuration to have "4" for the
fsxnet domain, not 21. (Assuming hpt is treating your "fidonet" AKA as your *primary* AKA - and thus it is packaging your fidonet mail to "/var/spool/ftn/outb")

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)

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 deon!

16 Sep 25 13:57, I wrote to you:

Finally I was able to fix the error.
I had uncommented the last line in binkd.conf which allowed connections to unlisted nodes, so I commented it out and now it works.

Thanks for you help.

Hello deon!

16 Sep 25 22:45, you wrote to me:

Sep 14:38:24 [45789] call to 21:x/y00@fidonet 16 Sep 14:38:24 [45789] getaddrinfo failed: Name does not resolve (8) 16 Sep 14:38:24 [45789] holding 21:x/y00@fidonet (2025/09/16 14:48:24) 16 Sep 14:38:24 [45789] unlinked `/var/spool/ftn/outb.015/000300z4.csy' 16 Sep 14:38:24
[45789] exitfunc() 16 Sep 14:38:24 [45789] bsy_remove_all: done 16 Sep 14:38:24 [45223] rc(45789)=0---

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 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)

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)

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)

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)

what's FSXNET?

J
--- CNet/5
* Origin: RetroLair.AmigaRetro.Net:6800 (1:342/30)