Hola Todos!

At all hours, at minute 20, the following appears in the log:

*************************************
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet'
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet'
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet'
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet'
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet'
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet'
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet'
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet'
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet'
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet' *************************************

And so on 368 times every hour for zones 1, 3 and 4.

I see it's because it can't find the domain for zones 1, 3, and 4, but I don't know how to make it find them.

Any help is welcome :)


Un saludo,
Angel Ripoll
aripoll @ zruspas.org

--- GoldED+/LNX 1.1.5-b20260304 + HPT 1.9 + Binkd 1.1 en Debian
* Origin: Synchronet - bbs.zruspas.org - Zruspa's BBS - (2:341/66)

Hi Angel,

On 2026-07-14 11:01:42, you wrote to Todos:

At all hours, at minute 20, the following appears in the log:

So it must be related to some event on your system on that time?

*************************************
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet'
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet'
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet'
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet'
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet'
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet'
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet'
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet'
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet'
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet'
*************************************

And so on 368 times every hour for zones 1, 3 and 4.

I see it's because it can't find the domain for zones 1, 3, and 4, but I don't
know how to make it find them.

Any help is welcome :)

It's a bit of trick, but the following might work. (Not tested)

Add these lines to your binkd config file:

address 1:999/999.999@fidonet 3:999/999.999@fidonet 4:999/999.999@fidonet

hide-aka 1:999/999.999@fidonet *
hide-aka 3:999/999.999@fidonet *
hide-aka 4:999/999.999@fidonet *


Bye, Wilfred.

--- FMail-lnx64 2.3.4.1-B20260520
* Origin: FMail development HQ (2:280/464)

On 2026 Jul 14 11:01:42, you wrote to Todos:

I see it's because it can't find the domain for zones 1, 3, and 4, but I don't know how to make it find them.

grab this file from my site,

https://sestar.synchro.net/temp/binkd-networks.conf

put it somewhere, and point your binkd to it... i include it in my binkd.conf just below my addresses list like this...

address 1:3634/12@fidonet 1:3634/0@fidonet 1:123/0@fidonet 1:18/0@fidonet #######################################
# include all known FTN networks list #
#######################################
include /sbbs/ftn/nodelist/binkd-networks.conf

it is a plain ascii test file... the way it is currently set up is for 5D FTN operations but most will use it in 4D FTN operations... the comments section at the top of the file should explain the difference and what to change... you'll need to edit it anyway to make the outbound paths fit your system... yes, on my system, all of those outbound directories exist even though i've never connected with any of them...

the list is pretty accurate and has been built over years of binkd connections with systems flying othernet addresses... yes, some/many of these old FTNs may not exist any more... it doesn't hurt anything to keep them listed and it is the only remaining list i know of for so many of the FTN othernets that existed...

now with all that said, it should also be noted that if a remote system has forgotten to add the domain to their addresses, you'll see a similar message as you are seeing now... that's a problem on their end, not yours but this case looks like you need this or a similar domains list file...

)\/(ark

"The soul of a small kitten in the body of a mighty dragon. Look on my majesty, ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!"
... I understand the answers, the questions throw me.
---
* Origin: (1:3634/12.73)

Hi mark,

On 2026-07-14 08:44:14, you wrote to Angel Ripoll:

I see it's because it can't find the domain for zones 1, 3, and 4,
but I don't know how to make it find them.

grab this file from my site,

https://sestar.synchro.net/temp/binkd-networks.conf

put it somewhere, and point your binkd to it... i include it in my binkd.conf
just below my addresses list like this...

address 1:3634/12@fidonet 1:3634/0@fidonet 1:123/0@fidonet 1:18/0@fidonet #######################################
# include all known FTN networks list # #######################################
include /sbbs/ftn/nodelist/binkd-networks.conf

I don't think this will help prevent the warnings that Angel is seeing in his log. But who knows, let him try it... ;-)

the list is pretty accurate and has been built over years of binkd connections with systems flying othernet addresses... yes, some/many
of these old FTNs may not exist any more... it doesn't hurt anything
to keep them listed and it is the only remaining list i know of for so many of the FTN othernets that existed...

There is a public spreadsheet on google docs with a list of FTN networks:

https://docs.google.com/spreadsheets/d/17pmf7cS9ocU99Rm6qlJD_OncqmbDI5Qj8Yw99A5bgVc/edit#gid=0


Bye, Wilfred.

--- FMail-lnx64 2.3.4.1-B20260520
* Origin: FMail development HQ (2:280/464)

On 2026 Jul 14 15:13:32, you wrote to me:

#######################################
# include all known FTN networks list #
#######################################
include /sbbs/ftn/nodelist/binkd-networks.conf

I don't think this will help prevent the warnings that Angel is seeing in his log. But who knows, let him try it... ;-)

true... i did also mention the problem may be the remote(s) not presenting their FTN domain(s) in their address list when the connection is made... that's a problem on the remote end and Angel doesn't show us the portion above these lines which tells the remote being connected to...

the list is pretty accurate and has been built over years of binkd
connections with systems flying othernet addresses... yes, some/many
of these old FTNs may not exist any more... it doesn't hurt anything
to keep them listed and it is the only remaining list i know of for so
many of the FTN othernets that existed...

There is a public spreadsheet on google docs with a list of FTN networks:

https://docs.google.com/spreadsheets/d/17pmf7cS9ocU99Rm6qlJD_OncqmbDI5Qj8Yw
99A5bgVc/edit#gid=0

i remember there being a sheet but i haven't looked it over in a long while... i trust my list a little more, though, because i do update it when i see a new FTN domain pop up in my binkd logs... with a very similar error message, too :wink:

)\/(ark

"The soul of a small kitten in the body of a mighty dragon. Look on my majesty, ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!"
... Psychoceramics: The study of crackpots.
---
* Origin: (1:3634/12.73)

Hi mark,

On 2026-07-14 10:31:32, you wrote to me:

I don't think this will help prevent the warnings that Angel is
seeing in his log. But who knows, let him try it... ;-)

true... i did also mention the problem may be the remote(s) not presenting their FTN domain(s) in their address list when the connection is made... that's a problem on the remote end and Angel doesn't show us the portion above
these lines which tells the remote being connected to...

I don't know if it's related to a connection being made.

There is a public spreadsheet on google docs with a list of FTN
networks:

https://docs.google.com/spreadsheets/d/17pmf7cS9ocU99Rm6qlJD_OncqmbDI5Qj8
Yw 99A5bgVc/edit#gid=0

i remember there being a sheet but i haven't looked it over in a long while...
i trust my list a little more, though, because i do update it when i see a new
FTN domain pop up in my binkd logs... with a very similar error message, too
:wink:

This spreadsheet is also updated by me and others. But probably not as consistently...


Bye, Wilfred.

--- FMail-lnx64 2.3.4.1-B20260520
* Origin: FMail development HQ (2:280/464)

14 Jul 26 11:01, Angel Ripoll wrote to Todos:

*************************************
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet' ? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet' ? Jul 12 01:20:01 [1561198] Cannot find domain for
zone 1, assuming 'fidonet' ? Jul 12 01:20:01 [1561198] Cannot find
domain for zone 1, assuming 'fidonet' ? Jul 12 01:20:01 [1561198]
Cannot find domain for zone 1, assuming 'fidonet' ? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet' ? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet' ?
Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet' ? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet' ? Jul 12 01:20:01 [1561198] Cannot find domain for
zone 1, assuming 'fidonet'
*************************************

And so on 368 times every hour for zones 1, 3 and 4.

I see it's because it can't find the domain for zones 1, 3, and 4, but
I don't know how to make it find them.

Any help is welcome :)

I think it's enough if you set up some (dummy) entries with domain in your binkd nodes file.

Node 1:999/999@fidonet *
Node 3:999/999@fidonet *
Node 4:999/999@fidonet *

Or maybe you could use "nolog" to hide those lines. ;)

'Tommi

---
* Origin: * RBB * Lake Ylo * Finland * (2:221/360)

Hi Tommi,

On 2026-07-14 19:10:49, you wrote to Angel Ripoll:

And so on 368 times every hour for zones 1, 3 and 4.

I see it's because it can't find the domain for zones 1, 3, and 4,
but I don't know how to make it find them. Any help is welcome :)

I think it's enough if you set up some (dummy) entries with domain in your binkd nodes file.

Node 1:999/999@fidonet *
Node 3:999/999@fidonet *
Node 4:999/999@fidonet *

I don't think this will work. If I look at the source only Domains and Aka's are checked for the domain name of a zone number.

Or maybe you could use "nolog" to hide those lines. ;)

That should work...

But I think it's better to prevent the warnings. ;-)


Bye, Wilfred.

--- FMail-lnx64 2.3.4.1-B20260520
* Origin: FMail development HQ (2:280/464)

On 14 Jul 2026, Wilfred van Velzen said the following...

It's a bit of trick, but the following might work. (Not tested)

Add these lines to your binkd config file:

address 1:999/999.999@fidonet 3:999/999.999@fidonet 4:999/999.999@fidonet

hide-aka 1:999/999.999@fidonet *
hide-aka 3:999/999.999@fidonet *
hide-aka 4:999/999.999@fidonet *

Seems to work here, thanks!

Before:

$ binkd -p -P 2:221/6 /usr/local/etc/binkd.conf
15:11 [86152] BEGIN, binkd/1.1a-115/Linux -p -P 2:221/6 /usr/local/etc/binkd.conf
? 15:11 [86152] Cannot find domain for zone 2, assuming 'fidonet'
15:11 [86152] creating a poll for 2:221/6@fidonet (`d' flavour)
15:11 [86152] clientmgr started
$ -d 2:221/6@fidonet
+ 15:11 [86153] call to 2:221/6@fidonet
15:11 [86153] trying news.fidonet.fi [51.38.115.207]...
15:11 [86153] connected
+ 15:11 [86153] outgoing session with news.fidonet.fi:24554 [51.38.115.207] [...]

After:

$ binkd -p -P 2:221/6 /usr/local/etc/binkd.conf
15:15 [86220] BEGIN, binkd/1.1a-115/Linux -p -P 2:221/6 /usr/local/etc/binkd.conf
15:15 [86220] creating a poll for 2:221/6@fidonet (`d' flavour)
15:15 [86220] clientmgr started
$ -d 2:221/6@fidonet
+ 15:15 [86221] call to 2:221/6@fidonet
15:15 [86221] trying news.fidonet.fi [51.38.115.207]...
15:15 [86221] connected
+ 15:15 [86221] outgoing session with news.fidonet.fi:24554 [51.38.115.207]
- 15:15 [86221] hiding aka 2:999/999.999@fidonet
- 15:15 [86221] hiding aka 3:999/999.999@fidonet
- 15:15 [86221] hiding aka 4:999/999.999@fidonet
[...]


Jay

... If you suck at playing the trumpet, thats why

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Northern Realms (1:229/664)

Hi Jay,

On 2026-07-14 15:20:42, you wrote to me:

It's a bit of trick, but the following might work. (Not tested)

Add these lines to your binkd config file:

address 1:999/999.999@fidonet 3:999/999.999@fidonet 4:999/999.999@fidonet

hide-aka 1:999/999.999@fidonet *
hide-aka 3:999/999.999@fidonet *
hide-aka 4:999/999.999@fidonet *

Seems to work here, thanks!

Before:

$ binkd -p -P 2:221/6 /usr/local/etc/binkd.conf
15:11 [86152] BEGIN, binkd/1.1a-115/Linux -p -P 2:221/6 /usr/local/etc/binkd.conf ? 15:11 [86152] Cannot find domain for zone 2, assuming 'fidonet' 15:11 [86152] creating a poll for 2:221/6@fidonet (`d' flavour) 15:11 [86152] clientmgr started $ -d 2:221/6@fidonet + 15:11 [86153]
call to 2:221/6@fidonet 15:11 [86153] trying news.fidonet.fi [51.38.115.207]... 15:11 [86153] connected + 15:11 [86153] outgoing session
with news.fidonet.fi:24554 [51.38.115.207] [...]

After:

$ binkd -p -P 2:221/6 /usr/local/etc/binkd.conf
15:15 [86220] BEGIN, binkd/1.1a-115/Linux -p -P 2:221/6 /usr/local/etc/binkd.conf 15:15 [86220] creating a poll for 2:221/6@fidonet
(`d' flavour) 15:15 [86220] clientmgr started $ -d 2:221/6@fidonet + 15:15 [86221] call to 2:221/6@fidonet 15:15 [86221] trying news.fidonet.fi [51.38.115.207]... 15:15 [86221] connected + 15:15 [86221] outgoing session
with news.fidonet.fi:24554 [51.38.115.207] - 15:15 [86221] hiding aka 2:999/999.999@fidonet - 15:15 [86221] hiding aka 3:999/999.999@fidonet - 15:15
[86221] hiding aka 4:999/999.999@fidonet [...]

Cool! Thanks for testing this.

Although it introduces some other log lines... But you can hide those with nolog option. ;-)

Bye, Wilfred.

--- FMail-lnx64 2.3.4.1-B20260520
* Origin: FMail development HQ (2:280/464)

Hello Angel!

14 Jul 26 11:01, you wrote to Todos:

At all hours, at minute 20, the following appears in the log:
? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet' ? Jul 12 01:20:01 [1561198] Cannot find domain for zone 1, assuming 'fidonet'
And so on 368 times every hour for zones 1, 3 and 4.
I see it's because it can't find the domain for zones 1, 3, and 4, but
I don't know how to make it find them.

I got rid of those warnings by specifying all FTN addresses throughout the config strictly as 5D (with the domain) including my system addresses, 'node' keywords, passwords file.

Yegor

--- GoldED+/LNX 1.1.5-b20260304
* Origin: (2:382/736)

Hola Wilfred!

14 Jul 26 11:39, Wilfred van Velzen dijo a Angel Ripoll:

Any help is welcome :)

It's a bit of trick, but the following might work. (Not tested)

Add these lines to your binkd config file:

address 1:999/999.999@fidonet 3:999/999.999@fidonet 4:999/999.999@fidonet

hide-aka 1:999/999.999@fidonet *
hide-aka 3:999/999.999@fidonet *
hide-aka 4:999/999.999@fidonet *

It works perfectly! :)

Thank you so much

Un saludo,
Angel Ripoll
aripoll @ zruspas.org

--- GoldED+/LNX 1.1.5-b20260304 + HPT 1.9 + Binkd 1.1 en Debian
* Origin: Synchronet - bbs.zruspas.org - Zruspa's BBS - (2:341/66)

Hola Mark!

14 Jul 26 08:44, mark lewis dijo a Angel Ripoll:

https://sestar.synchro.net/temp/binkd-networks.conf

put it somewhere, and point your binkd to it... i include it in my binkd.conf

I have tried it and it doesn't work.

Un saludo,
Angel Ripoll
aripoll @ zruspas.org

--- GoldED+/LNX 1.1.5-b20260304 + HPT 1.9 + Binkd 1.1 en Debian
* Origin: Synchronet - bbs.zruspas.org - Zruspa's BBS - (2:341/66)

Hola Tommi!

14 Jul 26 19:10, Tommi Koivula dijo a Angel Ripoll:

I think it's enough if you set up some (dummy) entries with domain in your binkd nodes file.

Node 1:999/999@fidonet *
Node 3:999/999@fidonet *
Node 4:999/999@fidonet *

I have tried it and it doesn't work.

Or maybe you could use "nolog" to hide those lines. ;)

nolog?

Un saludo,
Angel Ripoll
aripoll @ zruspas.org

--- GoldED+/LNX 1.1.5-b20260304 + HPT 1.9 + Binkd 1.1 en Debian
* Origin: Synchronet - bbs.zruspas.org - Zruspa's BBS - (2:341/66)

Hola Yegor!

15 Jul 26 01:54, Yegor Gluhov dijo a Angel Ripoll:

I got rid of those warnings by specifying all FTN addresses throughout the config strictly as 5D (with the domain) including my system addresses, 'node'
keywords, passwords file.

Tested and works :)

With what you've told me, i've already identified the problem. I use the iplist.lst file, which contains the URLs or IPs of the nodes running Binkd. In that file, the addresses are not 5D. If I remove that file, the 368 lines disappear. And if I add that file back, they reappear.

I modified the file to be 5D by adding @fidonet to all the nodes, and the lines don't appear anymore :).

Thanks :)

Un saludo,
Angel Ripoll
aripoll @ zruspas.org

--- GoldED+/LNX 1.1.5-b20260304 + HPT 1.9 + Binkd 1.1 en Debian
* Origin: Synchronet - bbs.zruspas.org - Zruspa's BBS - (2:341/66)

Hello, Angel Ripoll.
On 16/07/2026 11.02 you wrote:

Hola Tommi!
14 Jul 26 19:10, Tommi Koivula dijo a Angel Ripoll:

I think it's enough if you set up some (dummy) entries with domain in your
binkd nodes file.
Node 1:999/999@fidonet *
Node 3:999/999@fidonet *
Node 4:999/999@fidonet *

I have tried it and it doesn't work.

Yep, I was thinking something else. ;)

--- FastEcho/2 1.46.1 Revival
* Origin: nntp://rbb.fidonet.fi - Finland (2:221/360.0)

Hello, Angel Ripoll.
On 16/07/2026 12.02 you wrote:

With what you've told me, i've already identified the problem. I use the iplist.lst file, which contains the URLs or IPs of the nodes running Binkd. In that file, the addresses are not 5D. If I remove that file,
the 368 lines disappear. And if I add that file back, they reappear.
I modified the file to be 5D by adding @fidonet to all the nodes,
and the lines don't appear anymore :).

This is why I dont see those errors, I'm using a 5D nodes file created by nl2bind bash script. ;)

--- FastEcho/2 1.46.1 Revival
* Origin: nntp://rbb.fidonet.fi - Finland (2:221/360.0)

Hola Tommi!

16 Jul 26 14:00, Tommi Koivula dijo a Angel Ripoll:

This is why I dont see those errors, I'm using a 5D nodes file created by nl2bind bash script. ;)

Much easier. I just adopted it :)

Un saludo,
Angel Ripoll
aripoll @ zruspas.org

--- GoldED+/LNX 1.1.5-b20260304 + HPT 1.9 + Binkd 1.1 en Debian
* Origin: Synchronet - bbs.zruspas.org - Zruspa's BBS - (2:341/66)