Hi Torsten!

29 Jan 2016 00:09, from Torsten Bamberg -> Richard Menedetter:

 RM>>> My config looks like this:
 RM>>> root-domain not configured.
 RM>>> fido domain has root-domain binkp.net
 RM>>> othernet has no root-domain
 TB> It has to have a othernet domain, mostly this othernet domain is
 TB> virtually.

I think we are talking "around" each other.
With "root-domain" I mean the DNS Domain that is used to automatically look up
a node if it is not defined in the config.

What I want is that "fidonet" uses the binkp.net domain.
domain fidonet /home/fido/outbound 2 binkp.net
domain othernet /home/fido/outbound 2 <- missing last argument root-domain

When I then insert a
defnode *

I would assume that it tries to look up unconfigured nodes (not in binkd.cfg)
for fidonet in the fxx.nxx.zxx.binkd.net domain.
Strangely it also does it for @othernet
I have no clue what DNS domain it is using, as I have configured none!

What I am looking for is a
defnode *
only for fidonet, and not for any other domain.
How to configure that in binkd?

 RM>>>   -h 2:310/31.1@othernet <-- should not be here
 RM>>>   -d 2:12/34@othernet <-- should not be here
 RM>>> Is that a config error on my side?
 TB> Yes. you have to define the nodestatements with domain and disable
 TB> defnode.

But the whole purpose of my mail was NOT to comment out defnode *.
If I do it is working, but I do not have defnode behaviour for fidonet FTN
domain.

That is a very useful feature, and I want to use it for fidonet.

The question (bug??) is that it seems to make lookups also for othernet FTN
domains that do not even have a DNS root-domain configured.
I should tcpdump what DNS requests binkd sends.
Will do that later, when I am at home (currently at work)

CU, Ricsi

--- GoldED+/LNX