• hpt + binkd direct messages to different zone

    From Kai Richter@2:240/77 to Nick Boel on Saturday, September 27, 2025 18:03:40
    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)
  • From Kai Richter@2:240/77 to Tommi Koivula on Saturday, September 27, 2025 18:59:44
    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)
  • From Javier Sturman@4:900/733 to Kai Richter on Tuesday, September 30, 2025 09:19:54

    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)
  • From Kai Richter@2:240/77 to Javier Sturman on Thursday, October 02, 2025 14:09:00
    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)