Discussion:
root-domain
(too old to reply)
mark lewis
2012-10-11 13:12:20 UTC
Permalink
how can we specify more than one root-domain for f.n.z DNS lookups to go to for
domains that are not fidonet?

currently we use binkp.net for all lookups... even those that are FTN
othernets... shouldn't these othernets have their own fnz DNS service which
should be being used?

i'm thinking of maybe a modification to the root-domain line's format such that
the FTN domain it covers is listed and then the domain's DNS lookup server...
maybe something like this...

root-domain fidonet binkp.net // f.n.z.fidonet is on binkp.net
root-domain pascalnet pascal.net // f.n.z.pascalnet is on pascal.net
root-domain mynet mynet.com // f.n.z.mynet is on mynet.com

or ???

NOTE: the above are examples...

)\/(ark
Pavel Gulchouck
2012-10-12 04:19:20 UTC
Permalink
Hi mark!

11 Oct 12, mark lewis ==> all:

ml> how can we specify more than one root-domain for f.n.z DNS lookups to go
ml> to for domains that are not fidonet?

ml> currently we use binkp.net for all lookups... even those that are FTN
ml> othernets... shouldn't these othernets have
ml> their own fnz DNS service which should be being used?

ml> i'm thinking of maybe a modification to the root-domain line's format such
ml> that the FTN domain it covers is listed
ml> and then the domain's DNS lookup server... maybe something like this...

ml> root-domain fidonet binkp.net // f.n.z.fidonet is on binkp.net
ml> root-domain pascalnet pascal.net // f.n.z.pascalnet is on pascal.net
ml> root-domain mynet mynet.com // f.n.z.mynet is on mynet.com

ml> or ???

This feature was introduced in binkd 1.0.

# Your FTN domains:
# domain <name> <main-outbound> <default-zone> [<root-domain>]

Lucky carrier,
Pavel
aka ***@gul.kiev.ua
mark lewis
2012-10-14 07:45:54 UTC
Permalink
ml> root-domain fidonet binkp.net // f.n.z.fidonet is on binkp.net
ml> root-domain pascalnet pascal.net // f.n.z.pascalnet is on pascal.net
ml> root-domain mynet mynet.com // f.n.z.mynet is on mynet.com

ml> or ???

PG> This feature was introduced in binkd 1.0.

PG> # Your FTN domains:
PG> # domain <name> <main-outbound> <default-zone> [<root-domain>]

Cool!! i hadn't seen the notes on it... thanks, pavel! :)

)\/(ark
mark lewis
2012-11-15 08:06:06 UTC
Permalink
PG> This feature was introduced in binkd 1.0.

PG> # Your FTN domains:
PG> # domain <name> <main-outbound> <default-zone> [<root-domain>]

i thanked you before for this and i have implemented it in my configs... this
message is to point out that i do not find this information in the FAQ...
there's one or two places that it might go but i'll let someone else decide if
they are proper or if a new FAQ entry would be better...

)\/(ark

Benny Pedersen
2012-10-17 08:00:28 UTC
Permalink
Hello mark!

11 Oct 2012 17:12, mark lewis wrote to all:

ml> or ???

its not really needed, but if it is then it format should be changed to

root-domain <origin-zone-number> <destination-root-domain>

default would then be

root-domain 2 binkp.net

then root-domain can be multiline now

another way is to commit othher zone nodelist into the binkd dns so it will be
one single dns zone that holds ALL known nodelists, that was my plan with
nodelist.info domain but i dropped it since i have no time to make all the
underlaying work on this task


Regards Benny

... there can only be one way of life, and it works :)
mark lewis
2012-10-17 12:11:52 UTC
Permalink
ml> or ???

BP> its not really needed, but if it is then it format should be
BP> changed to

BP> root-domain <origin-zone-number> <destination-root-domain>

BP> default would then be

BP> root-domain 2 binkp.net

BP> then root-domain can be multiline now

you still have the same problem of not knowing that zone 7 is not a fidonet
zone...

BP> another way is to commit othher zone nodelist into the binkd dns so
BP> it will be one single dns zone that holds ALL known nodelists,

i asked if binkp.net was supposed to be this because of how binkd is doing all
DNS lookups... the answer was that it is not intended to be such...

BP> that was my plan with nodelist.info domain but i dropped it since
BP> i have no time to make all the underlaying work on this task

i don't blame you... but how were you going to get nodelist for /all/
othernets? especially when there is no listing of all othernets and their
zones...

)\/(ark
Benny Pedersen
2012-10-20 15:48:52 UTC
Permalink
Hello mark!

17 Oct 2012 16:11, mark lewis wrote to Benny Pedersen:

ml> you still have the same problem of not knowing that zone 7 is not a
ml> fidonet zone...

aha, but undefined zone numbers can be resolved to localhost or local

root-domain 7 localdomain

if my suggestion is used in my previous mail, then this zone could just use
cname as binkp expect results

ml> i asked if binkp.net was supposed to be this because of how binkd is
ml> doing all DNS lookups... the answer was that it is not intended to be
ml> such...

sadly imho yes, its just more sad that there exists othernets/othernetworks
that dont join fidonet in zone 1-5

ml> i don't blame you... but how were you going to get nodelist for /all/
ml> othernets? especially when there is no listing of all othernets and
ml> their zones...

my plan was to create some web where unknown new nodes could create there own
node listning, and then ask there where to get a uplink to connect to based on
known "left" nodes in fidonet, it might nearly be wasted now :(


Regards Benny

... there can only be one way of life, and it works :)
Loading...