Subj : binkd nodelist compiler
To   : Gary DeMontigny
From : Richard Menedetter
Date : Sat Jan 16 2016 10:24 am

Hi Gary!

15 Jan 2016 18:12, from Gary DeMontigny -> Richard Menedetter:

RM>> and in binkd.cfg
RM>> root-domain binkp.net
RM>> defnode *

GD> I am not familar with the binkp.net. I assume it acts as a dns server
GD> for binkd nodes. I don't see the root-domain or defnode * defined in
GD> my binkd docs. Sounds like an interesting alternative to the binkd.txt
GD> nodelist file. How does it work and I assume that I would have to
GD> register? Thanks.

Yes ... it is a DNS Server, that feeds from 3 sources:
1) IP nodes from the nodelist (propably the weekly one ... not sure)
2) manual entries on their web interface
3) DynDNS entries

for 2) you need to register and they send you a password via Fido Netmail.

for 3) you need to poll a russian node, and they update your address with the
IP that you polled with.

If you have the 2 statements in your config, than it will look up any node that
is not hardcoded in your config.
If the service is down, than it will natually not work.
But that should be very, very rare.

GD> Gary

CU, Ricsi

Here is the machine translated FAQ:
Answers to frequently asked questions about the area binkp.net

brief information
binkp.net - domain, which is designed to indicate the IP-addresses fidoshnyh
sites that support the protocol binkp. Anyone can go to sysop http://binkp.net,
enter your address fidoshny, and he will be sent a code word netmail. Using
this codeword, i.e. netmail acknowledging receipt of the address, you can
create, ie, enter a password, and enter an Internet address or its node. Later
you can change them through the same Web interface. You can also specify that
the IP is dynamic, while at the polling business address 2: 463 / 68.168 with a
password from the site IP calling party will be registered in binkp.net as the
node address (if that IP is really responsible for the mailer binkp).

Domain binkp.net conveniently used as a root-domain for binkd (for this role
fits any DDN).
There subdomains:
ddn.binkp.net - Information from the nodelist (and only);
node.binkp.net - node addresses, expressly provided by http://binkp.net;
dyn.binkp.net - dynamic IP.
In the main zone binkp.net team contained information from these three sources.

Q: Can I specify the address of the domain in the nodelist binkp.net? After the
domain binkp.net data is taken from the nodelist, will not it unzip.zip?
A: Of course, if someone has registered for your node address from binkp.net,
without specifying it in the zone binkp.net, this node will not be available.
The same situation is with any other domain. Before you specify in your
nodelist an Internet address, make sure that the address exists and is
available, regardless of the domain. binkp.net in this respect nothing is
original.

Q: Is binkp.net - a single point of failure (SPOF) for fidonet?
A: Firstly, binkp.net in the nodelist is used less often than, for example,
dyndns.org, but no one says that dyndns.org - a single point of failure.
Secondly, binkp.net - nothing more than a service that is convenient for many
sysops. Yes, it is currently unique (any fidoshnika may prescribe where the
address of the host running the service, plus Dynamic IP, tailored specifically
for the needs of fidoshnoy), but those who fear that binkp.net because this is
a SPOF, no one bothers raise your like. Domain binkp.net not a SPOF by design.
You can draw an analogy. Let's say I made a good knot (a convenient, reliable,
with autoenrollment links via web, all sorts of statistics, with mahjong and
geishas), sysops and pushed me in daunlinki. Is it appropriate to say "it is
necessary to disable this node and close because it is a single point of
failure"? Third, if me or my unit something happens (eg, I suddenly decide to
leave Fido), domain binkp.net stop working immediately, and even after the
termination of his work information about the contents of the zone will not be
lost (in the Unlike fidonet.net), as Fresh copies available at other
fidoshnikov. Himself domain binkp.net currently has four independent
authoritative nameservers (two in Russia and two in Ukraine).

Q: binkp.net - this is not the DDN, whether it can be used as a root-domain in
binkd?
A: Yes, binkp.net - this is not the DDN, it is more convenient than the DDN. In
addition to information from the nodelist It contains information explicitly
provided by sysops and information on dynamic IP, which makes its use more
preferable. In other words, if a node has an address in the nodelist (and,
respectively, DDN), and that it is in binkp.net, but the converse is not true
in general - may exist nodes informtsiya which is present in and absent from
binkp.net nodelist although this situation is not normal.

Q: Why do I need a special domain for binkp? The bad point addresses directly
in the nodelist, flags INA or IBN?
A: Nobody makes use binkp.net. This is more convenient to register in INA own
domain or IP-address directly, they do so. But many use binkp.net - means it is
convenient to them, and strange at the same time want to prevent its use as a
unnecessary. If you do not need - he wither away, unnecessary ban meaningless.
But it can be useful for several reasons:
- Quickly update more information than in the nodelist;
- No need to interact with people of (NC) to update, everything is automatic;
- Sites with dynamic IP is enough to register the IP is dynamic, and set up a
regular polling address 2: 463 / 68.168 [213.133.161.36], after which the IP
zone binkp.net will be updated automatically;
- Your own domain is not at all, and obviously propisvyat IP-address in the
nodelist is not always good (in particular, because this IP-address can change
over time, even if it is "static").

Q: Is there enough binkp.net sekyurno? After one sysop can make an arbitrary
zone information, which can be on the main perehvait mail.
A: Similarly, "nesekyuren" and any one of DDN, and generally any domain.
Moreover - nodelist Securit even less because (almost) any sysop can send in
fake web fileecho nodelist, and the nodelist will be adopted and applied by
other nodes (access parameters for customized nodlistovoy fileecho few people).
Or send in fileecho and send Ward regional segment (subject to availability of
password link with him). So to claim that nodelist sekyurnee than binkp.net,
strange.

Q: How much binkp.net reliably? If due to a malfunction or malicious intent
zone binkp.net Clean, old information will not be including and secondary. And
if sboyn.t nodelist, you can use the previous version.
A: Crashes during assembly nodelist (loss of regions, etc.) occur regularly,
Rollbacking - handmade, which makes a few. DNS on this regard suschestvnno
reliable. In addition, the previous version of the nodelist is not at all
always new nodelist overrides the previous one. If the sysop for safety made
..the preservation of the previous nodelist - nothing it does not hurt the same
way to make saving a previous version of the information binkp.net (available
on http://binkp.net/binkp-db).

--- GoldED+/LNX
* Origin: fido.ricsi.priv.at (2:310/31)

You are viewing proxied material from cvs.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.