Hello everybody!

I was wondering if somebody could help me with what it looks like a routing problem with hpt.
When I create compose a netmail and would like to send it direct hpt creates a new outbound directory for the destination zone
but that directory is not where binkd look for.

In hpt config I've got:

LogLevels 123456789

name s2r
sysop JAS
location CABA

address 4:900/733

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
[...]

How is this usually managed?


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)

Hey Javier!

On Fri, 19 Sep 2025 15:51:26 -0300, you wrote:

I was wondering if somebody could help me with what it looks like a
routing problem with hpt. When I create compose a netmail and would like
to send it direct hpt creates a new outbound directory for the
destination zone but that directory is not where binkd look for.

In hpt config I've got:

LogLevels 123456789

name s2r
sysop JAS
location CABA

address 4:900/733

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
[...]

How is this usually managed?

What are your route definitions for the node you're trying to send direct to? Assuming this/these are correct...

If you're trying to send direct netmail, your HPT route config should probably have a line like this (this is what I do):

route direct <link> <what to route>

So, if you want to send direct to 1:2/3, and you only want to send mail addressed to them, directly to them (ie, not route anything else):

route direct 1:2/3 1:2/3.*

Otherwise, if you want to route 1:2/* to 1:2/3:

route direct 1:2/3 1:2/*

First address is the one you want to send the mail to, and the second address is what you want to send to the first address (wildcards are accepted). You need to define something like this for every separate link you have, unless you route 1:* 2:* 3:* 4:* to one link. Also, put any direct links /above/ the 'catch-all' (1:* 2:* 3:* 4:*). For example:

route direct 1:154/10 1:154/10.*
route direct 1:229/426 1:* 2:* 3:* 4:*

Anything you netmail to 1:154/10.* would go directly to 1:154/10. Anything you netmail anywhere else, would route through 1:229/426 and let that system route it however they have setup to get it where it needs to go.

If the above is all correct and understood, and it still doesn't work.. then binkd is the next to check:

Did you setup a node definition for the node you want to send direct to? If not, are you using binkp.net? If neither, binkd won't know where to send it.

Hope that helps.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Hello Nick!

19 Sep 25 19:20, you wrote to me:

This is my route config:

#EN# Don't route mail to zone adresses
route no-pack *:0/*

# Mails an Points auf "hold" setzen
route hold noroute 4:900/733.*

## ruteo para points va a nodos
route crash boss *:*/*.*

# Mails an 1:*, 2:*, 3:*, 4:* und 5:* sofort an
route crash 4:902/26 1:* 2:* 3:* 4:* 5:*
route crash 21:3/100 21:*

#EN# Don't route 0:, 32767:, etc.
route no-pack *

I don't have a node definition for the bossnode of the point I'd like to contact however the node is listed in the nodelist.

Hey Javier!

On Fri, 19 Sep 2025 15:51:26 -0300, you wrote:

I was wondering if somebody could help me with what it looks like a
routing problem with hpt. When I create compose a netmail and would
like to send it direct hpt creates a new outbound directory for the
destination zone but that directory is not where binkd look for.

In hpt config I've got:

LogLevels 123456789

name s2r
sysop JAS
location CABA

address 4:900/733

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
[...]

How is this usually managed?

What are your route definitions for the node you're trying to send
direct to? Assuming this/these are correct...

If you're trying to send direct netmail, your HPT route config should probably have a line like this (this is what I do):

route direct <link> <what to route>

So, if you want to send direct to 1:2/3, and you only want to send
mail addressed to them, directly to them (ie, not route anything
else):

route direct 1:2/3 1:2/3.*

Otherwise, if you want to route 1:2/* to 1:2/3:

route direct 1:2/3 1:2/*

First address is the one you want to send the mail to, and the second address is what you want to send to the first address (wildcards are accepted). You need to define something like this for every separate
link you have, unless you route 1:* 2:* 3:* 4:* to one link. Also, put
any direct links /above/ the 'catch-all' (1:* 2:* 3:* 4:*). For
example:

route direct 1:154/10 1:154/10.*
route direct 1:229/426 1:* 2:* 3:* 4:*

Anything you netmail to 1:154/10.* would go directly to 1:154/10.
Anything you netmail anywhere else, would route through 1:229/426 and
let that system route it however they have setup to get it where it
needs to go.

If the above is all correct and understood, and it still doesn't
work.. then binkd is the next to check:

Did you setup a node definition for the node you want to send direct
to? If not, are you using binkp.net? If neither, binkd won't know
where to send it.

Hope that helps.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin)
(1:154/10)

Javier


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

Hey Javier!

On Fri, 19 Sep 2025 22:22:22 -0300, you wrote:

# Mails an 1:*, 2:*, 3:*, 4:* und 5:* sofort an
route crash 4:902/26 1:* 2:* 3:* 4:* 5:*
route crash 21:3/100 21:*

For what it's worth, Fidonet doesn't have a zone 5 any more, so no need for '5:*' there. However, this has nothing to do with your issue.

I don't have a node definition for the bossnode of the point I'd like to contact however the node is listed in the nodelist.

Seems as though hpt is doing it's job so far. Post your binkd.conf next (without passwords). I predict you may be trying to use some sort of 5D addressing when you may not need to.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Hey Javier!

On Sat, 20 Sep 2025 16:52:08 -0300, you wrote:

Here yo have my binkd.conf. Doesn't HPT support 5D addressing?

It looks like you don't have any means of contacting anyone in zone 2.

- No 'node' definitions.
- Not using binkp.net
- No binkd compatible nodelist included

You're going to have to pick one of the three, or binkd won't know where to connect.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

* Originally in fidosoft.husky
* Crossposted in binkd

Hi Javier.

20 Sep 25 16:52, you wrote to Nick Boel:

# The first variant specifies a domain as a default domain for 3D/4D addresses.
#
domain fidonet /var/spool/ftn/outb 4 fidonet

=======

You should use binkp.net here or just remove it. Now your binkd tries to resolve the domain .fidonet, which may not exist.

'Tommi

---
* Origin: nntps://news.fidonet.fi (2:221/1)

Hello Tommi!

22 Sep 25, Tommi Koivula wrote to Javier Sturman:

# The first variant specifies a domain as a default domain for
3D/4D addresses. # domain fidonet /var/spool/ftn/outb 4 fidonet

=======

You should use binkp.net here or just remove it. Now your binkd tries
to resolve the domain .fidonet, which may not exist.

Hm, sure? This config is working for me since my binkd installation. As far as i remember the domain is a fidonet "domain" and not an internet domain.

Those domain definition may be part of the 5D ftn style address.
I found an old btxe doc with:

Password 2:2476/7@fidonet passed valid, defines password "passed"
only for a node "2:2476/7" with
the CORRECT domain ("fidonet"). A
node 2:2476/7@anynet would get a
password failure.

This is an extension of password protection, 'cause with passwords only in
compiled nodelists binkley can normally not distinguish between a password
for "2:2476/7@anynet" and "2:2476/7@fidonet".



The main purpose of fidonet domains is to run different networks on the same zone number with overlapping net/node entries.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Javier!

20 Sep 25, Javier Sturman wrote to Nick Boel:

# domain <name> <main-outbound> <default-zone> [<root-domain>]

# The first variant specifies a domain as a default domain for 3D/4D addresses.

domain fidonet /var/spool/ftn/outb 4 fidonet
domain fsxnet /var/spool/ftn/outb 4 fsxnet

The path for both domains is the same. Mail for net/node@fidonet goes to outb and mail for net/node@fsxnet goes to outb. Please check your outb for files, do they have a clear differency for domains within the file names?

As far as i remember the domains were made compatible for DOS and FAT 8.3 outbound file name conventions. The filename contains hex net/node adresses that's why the zone is defined in the config.

Scanning mail to that outb would result in one target node only. The *.?lo flowfile is for 40/441 and the directory for zone 4. Because both domains dive into the same outbound outb whoever 4:40/441 connects first will get the mail on hold.

# Aliases to support known DNS domain zones
# (some people mix up the terms "FTN domain" and "DNS internet
domain")

That's the key element. Do not mix up.

address 4:900/733@fidonet 21:3/100.2@fsxnet

Above you set the fsxnet zone outbound to zone 4. If 21 is correct then it should be 21. In that case no domain is needed. As long you have seperate zones there is no need for domains.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Kai!

24 Sep 25 01:59, you wrote to me:

domain fidonet /var/spool/ftn/outb 4 fidonet
domain fsxnet /var/spool/ftn/outb 4 fsxnet

The path for both domains is the same. Mail for net/node@fidonet goes
to outb and mail for net/node@fsxnet goes to outb. Please check your
outb for files, do they have a clear differency for domains within the file names?

The only way I see the files for fsxnet (21:*) is that the outbound directory has 21 in it.

fido:/var/spool/ftn$ ls -al
total 31
drwxrwx--- 14 fido fido 14 Sep 26 14:59 .
drwxr-xr-x 10 root wheel 10 May 18 19:50 ..
drwxrwx--- 2 fido fido 34 Sep 19 15:44 dupebase
drwxrwx--- 5 fido fido 5 Sep 15 12:50 filebase
drwxrwx--- 2 fido fido 2 May 18 19:50 fileboxes
drwxrwx--- 2 fido fido 2 May 18 19:10 flags
drwxrwx--- 3 fido fido 5 Sep 26 15:25 inb
drwxrwx--- 2 fido fido 2 Sep 26 15:25 inbound-temp
drwxrwx--- 5 fido fido 5 Jun 8 22:08 msgbase
drwxrwx--- 3 fido fido 3 Sep 26 15:25 outb
drwxr-xr-x 3 fido fido 3 Sep 26 07:35 outb.002
drwxrwx--- 3 fido fido 5 Sep 26 16:36 outb.015
drwxrwx--- 4 fido fido 4 Sep 16 11:47 tmp
drwxrwx--- 2 fido fido 2 May 18 19:50 transit
fido:/var/spool/ftn$ ls -ald outb.015/*
-rw-r--r-- 1 fido fido 0 Sep 26 15:00 outb.015/00030064.dlo
drwxrwx--- 2 fido fido 2 Sep 19 18:36 outb.015/00030064.sep
-rw-r--r-- 1 fido fido 23 Sep 26 16:36 outb.015/00030064.try fido:/var/spool/ftn$ cat outb.015/00030064.try
Cannot getaddrinfofid

It seems that binkd doesn't seem to resolv 21:3/100 however if I do a ns lookup it resolves.

fido:/var/spool/ftn$ drill f100.n3.z21.fsxnet.nz
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 13460
;; flags: qr rd ra ; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; f100.n3.z21.fsxnet.nz. IN A

;; ANSWER SECTION:
f100.n3.z21.fsxnet.nz. 21597 IN CNAME clrghouz.bbs.dege.au. clrghouz.bbs.dege.au. 3597 IN CNAME ip4.bbs.dege.au. ip4.bbs.dege.au. 3597 IN A 139.99.135.199

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 5011 msec
;; SERVER: 10.10.20.150
;; WHEN: Fri Sep 26 16:40:22 2025
;; MSG SIZE rcvd: 107

As far as i remember the domains were made compatible for DOS and FAT
8.3 outbound file name conventions. The filename contains hex net/node adresses that's why the zone is defined in the config.

Scanning mail to that outb would result in one target node only. The
*.?lo flowfile is for 40/441 and the directory for zone 4. Because
both domains dive into the same outbound outb whoever 4:40/441
connects first will get the mail on hold.

# Aliases to support known DNS domain zones
# (some people mix up the terms "FTN domain" and "DNS internet
domain")

That's the key element. Do not mix up.

address 4:900/733@fidonet 21:3/100.2@fsxnet

Above you set the fsxnet zone outbound to zone 4. If 21 is correct
then it should be 21. In that case no domain is needed. As long you
have seperate zones there is no need for domains.

I will try removing both 4s from the config and keep trying.

Also I don't understand why does the tosser packer create a directory for the point although it should have been for the bossnode of that point.

fido:/var/spool/ftn$ ls -ald outb.002/*
drwxr-xr-x 3 fido fido 6 Sep 26 16:41 outb.002/00dd0001.pnt fido:/var/spool/ftn$ ls -ald outb.002/*/*
-rw------- 1 fido fido 767 Sep 26 00:28 outb.002/00dd0001.pnt/0000003a.dut -rw-r--r-- 1 fido fido 10 Sep 26 16:41 outb.002/00dd0001.pnt/0000003a.hld drwxr-xr-x 2 fido fido 2 Sep 26 00:28 outb.002/00dd0001.pnt/0000003a.sep -rw-r--r-- 1 fido fido 23 Sep 26 16:41 outb.002/00dd0001.pnt/0000003a.try fido:/var/spool/ftn$ cat outb.002/00dd0001.pnt/0000003a.try

And in binkd.log
-+-
26 Sep 16:32:17 [72994] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:32:17 [74073] rc(72994)=0
26 Sep 16:33:17 [73201] call to 2:221/1.58@fidonet
26 Sep 16:33:17 [74073] 2:221/1.58@fsxnet busy, skipping
26 Sep 16:33:17 [73202] call to 21:3/100@fidonet
26 Sep 16:33:17 [74073] 21:3/100@fsxnet busy, skipping
26 Sep 16:33:17 [73201] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:33:17 [73202] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:33:17 [74073] rc(73202)=0
26 Sep 16:33:17 [74073] rc(73201)=0
26 Sep 16:34:17 [73399] call to 2:221/1.58@fidonet
26 Sep 16:34:17 [74073] 2:221/1.58@fsxnet busy, skipping
26 Sep 16:34:17 [74073] 21:3/100@fsxnet busy, skipping
26 Sep 16:34:17 [73400] call to 21:3/100@fidonet
26 Sep 16:34:17 [73399] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:34:17 [73400] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:34:17 [74073] rc(73399)=0
26 Sep 16:34:17 [74073] rc(73400)=0
26 Sep 16:35:17 [73605] call to 2:221/1.58@fidonet
26 Sep 16:35:17 [74073] 2:221/1.58@fsxnet busy, skipping
26 Sep 16:35:17 [74073] 21:3/100@fsxnet busy, skipping
26 Sep 16:35:17 [73606] call to 21:3/100@fidonet
26 Sep 16:35:17 [73605] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:35:17 [73606] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:35:17 [74073] rc(73605)=0
26 Sep 16:35:17 [74073] rc(73606)=0
26 Sep 16:36:17 [73813] call to 2:221/1.58@fidonet
26 Sep 16:36:17 [74073] 2:221/1.58@fsxnet busy, skipping
26 Sep 16:36:17 [74073] 21:3/100@fsxnet busy, skipping
26 Sep 16:36:17 [73814] call to 21:3/100@fidonet
26 Sep 16:36:17 [73813] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:36:17 [73814] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:36:17 [74073] rc(73814)=0
26 Sep 16:36:17 [74073] rc(73813)=0
26 Sep 16:37:17 [74014] call to 2:221/1.58@fidonet
26 Sep 16:37:17 [74073] 2:221/1.58@fsxnet busy, skipping
26 Sep 16:37:17 [74015] call to 21:3/100@fidonet
26 Sep 16:37:17 [74073] 21:3/100@fsxnet busy, skipping
26 Sep 16:37:17 [74014] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:37:17 [74015] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:37:17 [74073] rc(74015)=0
26 Sep 16:37:17 [74073] rc(74014)=0
-+-

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Javier


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

Hey Kai!

On Wed, 24 Sep 2025 01:59:32 , you wrote:

# domain <name> <main-outbound> <default-zone> [<root-domain>]

# The first variant specifies a domain as a default domain for
3D/4D addresses.

domain fidonet /var/spool/ftn/outb 4 fidonet
domain fsxnet /var/spool/ftn/outb 4 fsxnet

The path for both domains is the same. Mail for net/node@fidonet goes to outb and mail for net/node@fsxnet goes to outb. Please check your outb
for files, do they have a clear differency for domains within the file names?

This is how 4D addressing works. binkd will automatically create the "outb" folder for zone 4, and then the fsxnet folder will be outb.015

As far as i remember the domains were made compatible for DOS and FAT
8.3 outbound file name conventions. The filename contains hex net/node adresses that's why the zone is defined in the config.

Only when using 5D addressing.

Scanning mail to that outb would result in one target node only. The
*.?lo flowfile is for 40/441 and the directory for zone 4. Because both domains dive into the same outbound outb whoever 4:40/441 connects first will get the mail on hold.

# Aliases to support known DNS domain zones
# (some people mix up the terms "FTN domain" and "DNS internet
domain")

That's the key element. Do not mix up.

Just as well, and in his case, he mixed up the "root-domain" with "domain". The last option should not be 'fidonet' or 'fsxnet'. In Fidonet's case, it should be binkp.net. If fsxnet has a root-domain that can be looked up, that should be there instead.

address 4:900/733@fidonet 21:3/100.2@fsxnet

Above you set the fsxnet zone outbound to zone 4. If 21 is correct then
it should be 21. In that case no domain is needed. As long you have
seperate zones there is no need for domains.

Only when using 5D addressing, which he is not. Please don't confuse him more than he already is. :/

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Hey Javier!

On Fri, 26 Sep 2025 16:36:02 -0300, you wrote:

The only way I see the files for fsxnet (21:*) is that the outbound directory has 21 in it.

If you are already going to change your configuration without trying my previous suggestion(s), don't bother trying those suggestions, as they probably won't work since you've changed your config... again.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Hello Nick!

26 Sep 25 20:08, you wrote to me:

I deleted all outbound directories and then modified my binkd.conf based on this config file I was directed in another network.
Now it works. (https://nrbbs.net/binkd-linux.txt)

Hey Javier!

On Fri, 26 Sep 2025 16:36:02 -0300, you wrote:

The only way I see the files for fsxnet (21:*) is that the outbound
directory has 21 in it.

If you are already going to change your configuration without trying
my previous suggestion(s), don't bother trying those suggestions, as
they probably won't work since you've changed your config... again.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin)
(1:154/10)

Javier


--- 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 Kai.

24 Sep 25 01:42:32, you wrote to me:

# The first variant specifies a domain as a default domain for
3D/4D addresses. # domain fidonet /var/spool/ftn/outb 4 fidonet

=======

You should use binkp.net here or just remove it. Now your binkd
tries to resolve the domain .fidonet, which may not exist.

Hm, sure?

Yes.

'Tommi

---
* Origin: Point One (2:221/1.1)

Hello Nick!

26 Sep 25, Nick Boel wrote to Kai Richter:

# domain <name> <main-outbound> <default-zone> [<root-domain>]

# Aliases to support known DNS domain zones
# (some people mix up the terms "FTN domain" and "DNS internet
domain")

That's the key element. Do not mix up.

Just as well, and in his case, he mixed up the "root-domain" with "domain". The last option should not be 'fidonet' or 'fsxnet'. In Fidonet's case, it should be binkp.net. If fsxnet has a root-domain
that can be looked up, that should be there instead.

Then root-domain does stand for "DNS internet domain"?

Above you set the fsxnet zone outbound to zone 4. If 21 is correct
then it should be 21. In that case no domain is needed. As long you
have seperate zones there is no need for domains.

Only when using 5D addressing, which he is not. Please don't confuse
him more than he already is. :/

I do apologize. I think there are three issues within the config. I would choose different outbounds for the domains, then each domain could have it's own zone breakdown subdirs.

The DNS lookups was already explained by Tommi but i did not understand fully because there was no root-domain reference mentioned.

The third one is point to bossnode routing. I think that could be fixed later.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Tommi!

27 Sep 25, Tommi Koivula wrote to Kai Richter:

# The first variant specifies a domain as a default domain for
3D/4D addresses. # domain fidonet /var/spool/ftn/outb 4 fidonet

=======

+++++++

You should use binkp.net here or just remove it. Now your binkd
tries to resolve the domain .fidonet, which may not exist.

Hm, sure?

Yes.

Sorry, the position of the originating underscore (+++) and domain fidonet pointed me to the first fidonet keyword. Now it does make sense.

Maybe we could turn to fully edited config lines to avoid confusion. ;-)

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Kai!

27 Sep 25 18:03, you wrote to Nick Boel:

Above you set the fsxnet zone outbound to zone 4. If 21 is correct
then it should be 21. In that case no domain is needed. As long
you have seperate zones there is no need for domains.

Only when using 5D addressing, which he is not. Please don't
confuse him more than he already is. :/

I do apologize. I think there are three issues within the config. I
would choose different outbounds for the domains, then each domain
could have it's own zone breakdown subdirs.

At first tried to do that but HPT doesn't allow to specify an outbound directory for each link. I has support for 5D addressing but not everywhere.

The DNS lookups was already explained by Tommi but i did not
understand fully because there was no root-domain reference mentioned.

The third one is point to bossnode routing. I think that could be
fixed later.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

s2r


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

30 Sep 25, Javier Sturman wrote to Kai Richter:

At first tried to do that but HPT doesn't allow to specify an outbound directory for each link.

What about "Filebox"? I used it for my points "hold" directory. Each point had it's own.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)