limit zones per domain?

[mark lewis]

recently we've been given the feature of specifying what DNS domain to perform
fnz conversion and lookups on... it has been needed ;)

my question now is how can we define what zones are in a certain FTN domain? i
mean, we have to tell what our zone is for any given FTN domain but we never
tell what the "spread" of zones for that FTN domain is...

ie: fidonet zones 1-5
foobar zones 315,318
wizard zones 42,314,500-502

)\/(ark

[Pavel Gulchouck]

Hi mark!

16 Oct 12, mark lewis ==> all:

ml> recently we've been given the feature of specifying what DNS domain to
ml> perform fnz conversion and lookups on... it
ml> has been needed ;)

ml> my question now is how can we define what zones are in a certain FTN
ml> domain? i mean, we have to tell what our zone
ml> is for any given FTN domain but we never tell what the "spread" of zones
ml> for that FTN domain is...

ml> ie: fidonet zones 1-5
ml> foobar zones 315,318
ml> wizard zones 42,314,500-502

binkd operates with 5D addresses.
Domain is required part of an FTN address in binkp protocol.
In theory you can have links with different nodes 315:1/***@foobar and
315:1/***@wizard.
Domain may be omitted only in some particular cases, only in config file and
only if we have aka (5D specified) in this zone.
Binkd should never have to detect, what implicit domain has a node in zone 315.

Lucky carrier,
Pavel
aka ***@gul.kiev.ua

[mark lewis]

ml> my question now is how can we define what zones are in a certain
ml> FTN domain? i mean, we have to tell what our zone is for any given
ml> FTN domain but we never tell what the "spread" of zones for that
ml> FTN domain is...

ml> ie: fidonet zones 1-5
ml> foobar zones 315,318
ml> wizard zones 42,314,500-502

PG> binkd operates with 5D addresses.
PG> Domain is required part of an FTN address in binkp protocol. In
PG> theory you can have links with different nodes 315:1/***@foobar and
PG> 315:1/***@wizard.
PG> Domain may be omitted only in some particular cases, only in config
PG> file and only if we have aka (5D specified) in this zone.
PG> Binkd should never have to detect, what implicit domain has a node
PG> in zone 315.

i understand... however, i'm looking more at the DNS lookups that are done on
the AKA addresses of the remote during a connection... i do not have addresses
in any othernets so some questions...

why is binkd making DNS lookups of remote AKAs in domains not configed?
why is binkd making those lookups in the binkp.net domain?

here are all of the othernet AKAs presented by one of my links... i do not have
an address in any of these othernets...

10:10/***@league10.org
10:3000/***@league10.org
10:3000/***@league10.org
33:860/***@advnet
33:860/***@advnet
110:212/***@linuxnet
110:212/***@linuxnet
111:4950/***@stn
111:4950/***@stn
111:4950/***@stn
618:100/***@micronet
618:100/***@micronet
618:100/***@micronet
618:10/***@micronet
92:762/***@zenet
92:762/***@zenet
92:762/***@zenet
510:269/***@justanet
510:269/***@justanet
510:5112/***@justanet
115:1502/***@pascalnet


yet, ALL of the above are having DNS lookups performed to binkp.net... how do i
know? i see them in my DNS log ;)

)\/(ark