On 2017 Sep 21 10:33:02, you wrote to Michiel van der Vlist:

 MV>> I have these lines in binkd.cfg

 MV>> defnode *
 MV>> #root-domain binkd.net

 TK> Two minor issues...

 TK> 1. The second line is commented out, so it does not help.
 TK> 2. It should be binkp.net, not binkd.net.

and it should ideally be defined as the very last field on the domain line...
especially for systems in more than one domain... those other domains should
also have their own DNS zone for the fnz converted FTN addresses...


for others following along...

eg: for 3D/4D
domain fidonet  /bink/outbound 1 binkp.net
domain amiganet /bink/outbound 1 amiganet.invalid

actual directory structure:
/bink/outbound      <- main zone outbound (Z1 in this example)
/bink/outbound.002  <- Z2 outbound
/bink/outbound.003  <- Z3 outbound
/bink/outbound.004  <- Z4 outbound
/bink/outbound.027  <- Z39 outbound


eg: for 5D
domain fidonet  /bink/outbound/fidonet   1 binkp.net
domain amiganet /bink/outbound/amiganet 39 amiganet.invalid

actual directory structure:
/bink/outbound/fidonet      <- main zone outbound (Z1 in this example)
/bink/outbound/fidonet.002  <- Z2 outbound
/bink/outbound/fidonet.003  <- Z3 outbound
/bink/outbound/fidonet.004  <- Z4 outbound
/bink/outbound/amiganet     <- Z39 outbound


there are not very many mail tossers that are BSO 5D aware...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... Aliens make terrible house pets.
---