Hello All,
I am trying to add "defnode *" to my binkd.conf so I can send netmail directly to nodes I don't have a node line in my binkd.conf. When I do that binkd uses the wrong domain and fails for nodes I do have listed,
as below..
This only happens when I add "defnode *" to my binkd.conf, if I leave it commented out all is working as expected.
What have I done wrong?
This only happens when I add "defnode *" to my binkd.conf, if I
leave it commented out all is working as expected.
What have I done wrong?
I don't think you have done ANYTHING wrong... the node needs to update
at binkp.net
This only happens when I add "defnode *" to my binkd.conf, if I
leave it commented out all is working as expected.
What have I done wrong?
I don't think you have done ANYTHING wrong... the node needs to update
at binkp.net
I've got something wrong here that only shows itself when I add "defnode *" to my binkd.conf. Instead of polling 1:2320/100@fidonet (for example) it tries to poll 1:2320/100@agoranet and that fails because that node doesn't have such an aka. It does the same for the other zones I have here also.
binkp.net does work here as expected.
Hello Alan!
18 Aug 16 14:40, you wrote to Allen Prunty:
This only happens when I add "defnode *" to my binkd.conf, if I
leave it commented out all is working as expected.
What have I done wrong?
I don't think you have done ANYTHING wrong... the node needs to
update at binkp.net
I've got something wrong here that only shows itself when I add
"defnode *" to my binkd.conf. Instead of polling 1:2320/100@fidonet
(for example) it tries to poll 1:2320/100@agoranet and that fails
because that node doesn't have such an aka. It does the same for the
other zones I have here also.
binkp.net does work here as expected.
You will have to reajust your expectations.
The following line should be in your config file.
-------------------------------
#
# Overrides root domain for DNS lookups, see `node' below.
#
root-domain binkp.net
-----------------
That forces de domain for defnode and "*" notations for hostnames.
The "*" notation forces binkd to use the following hostname
fn.nx.zy.binkd.net
Where x=nodenumber, y=netnumber, z=zonenumber
Kees
--- GoldED+/LNX 1.1.5
* Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
I've got something wrong here that only shows itself when I add
"defnode *" to my binkd.conf. Instead of polling
1:2320/100@fidonet (for example) it tries to poll
1:2320/100@agoranet and that fails because that node doesn't have
such an aka. It does the same for the other zones I have here
also.
binkp.net does work here as expected.
You will have to reajust your expectations.
The following line should be in your config file.
-------------------------------
#
# Overrides root domain for DNS lookups, see `node' below.
#
root-domain binkp.net
-----------------
Thursday August 18 2016 06:39, you wrote to me:
This only happens when I add "defnode *" to my binkd.conf, if I
leave it commented out all is working as expected.
What have I done wrong?
I don't think you have done ANYTHING wrong... the node needs to update
at binkp.net
I've got something wrong here that only shows itself when I add
"defnode *" to my binkd.conf. Instead of polling 1:2320/100@fidonet
(for example) it tries to poll 1:2320/100@agoranet and that fails
because that node doesn't have such an aka. It does the same for the
other zones I have here also.
binkp.net does work here as expected.
binkp.net does work here as expected.
You will have to reajust your expectations.
The following line should be in your config file.
-------------------------------
#
# Overrides root domain for DNS lookups, see `node' below.
#
root-domain binkp.net
-----------------
That forces de domain for defnode and "*" notations for hostnames.
The "*" notation forces binkd to use the following hostname
fn.nx.zy.binkd.net
Where x=nodenumber, y=netnumber, z=zonenumber
That's whacked as I don't use agoranet.
I put 5D entries in all of my node entries like so...
node 21:1/100.0@fsxnet -6 ipv6.agency.bbs.geek.nz:24556;* NUNYA i c:\\pxw\ \fsxnet\\out
In this case it's no question it's fxnet
Was told everything works better when the node is completely speced
out.
In your case it shouild start with...
node 1:2320/100.0@fidonet ....
This way BinkD knows my domain is fidonet and it doesn't have to guess
Allen
... The greatest enemy of creatitivy is staying inside your comfort
zone
--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: LiveWire -=* Louisville, KY USA *=- LiveWireBBS.Com (1:2320/100)
I think the only nodes listed there are zone 1-4 though.
I've got something wrong here that only shows itself when I add
"defnode *" to my binkd.conf. Instead of polling 1:2320/100@fidonet
(for example) it tries to poll 1:2320/100@agoranet and that fails
because that node doesn't have such an aka. It does the same for the
other zones I have here also.
binkp.net does work here as expected.
You will have to reajust your expectations.
The following line should be in your config file.
-------------------------------
#
# Overrides root domain for DNS lookups, see `node' below.
#
root-domain binkp.net
-----------------
mark lewis wrote to Kees van Eeten <=-
this is *best* done with the new format... especially for those in multiple FTN networks... the new format is
domain fidonet /ftn/outbound/fidonet 1 binkp.net
domain foobarz /ftn/outbound/foobarz 1234 foobarz.net
domain barfood /ftn/outbound/barfood 321 barfood.org
I am trying to add "defnode *" to my binkd.conf so I can send netmail directly to nodes I don't have a node line in my binkd.conf. When I do that binkd uses the wrong domain and fails for nodes I do have listed,
as below..
Anyways ... my solution looks like this:
#defnode *
include /usr/local/etc/binkd.inc
I have a script that converts the fidonet daily nodelist to a binkd include file.
I have a script that converts the fidonet daily nodelist to aYou have been quiet too long starting to wonder if you are ok.
binkd include file.
Would you consider sharing the script?
this is *best* done with the new format... especially for those in
multiple FTN networks... the new format is
domain fidonet /ftn/outbound/fidonet 1 binkp.net
domain foobarz /ftn/outbound/foobarz 1234 foobarz.net
domain barfood /ftn/outbound/barfood 321 barfood.org
What version of binkd do you need to be able to use this format?
It's certainly much better, as I had issues with using the root-domain configuration, with my othernets. I'd have kept using binkp.net, if I could restrict its use to Fidonet addresses. It plays havoc with othernets, so the above per domain format makes more sense.
Hi Allen!
Was away for 2 weeks, and the fido node crashed (?) after 2 days ...
Came back thought it was a dead storage, rebooted, and it works again.
Would you consider sharing the script?
I only use that script, it was not written by me.
# nl2binkd v1.07
# (c) 2012-2016 by Markus Reschke
# Fidonet 2:240/1661 / madires@theca-tabellaria.de
Works very well, and evades the issues with defnode * and othernets, while still being able to crash every fido node with binkp.
Was away for 2 weeks, and the fido node crashed (?) after 2 days... -> Came back thought it was a dead storage, rebooted, and it works again.
It must have been exhausted... it needed rest.
You will be proud of me I have bink-d working now, and it is
connectable via ipv6 at ipv6.livewirebbs.com
Hi Allen!
20 Aug 2016 06:11, from Allen Prunty -> Richard Menedetter:
Some comments:
The hosts differs from the one in the nodelist.
You can add A and AAAA records, and the IPv6 capable nodes will automatically connect via IPv6 and the rest with IPv4.
Also it seems you do not have the password that I have sent you in the config - I get an unsecured connection.
mark lewis wrote to Tony Langdon <=-
What version of binkd do you need to be able to use this format?
TBH, i'm not sure... i pointed out the problem with using root-domain
and being in multiple FTN othernets and binkp.net doing only fidonet addresses some time back... one of the developers told me about this format but it has been several years ago... i don't recall their name
but i think it was stas degteff as he helped me with other aspects of a full 5D configuration and what the outbound directory tree would look like... this alternative method of listing DNS lookup domains is not specific to 5D, though... on my main machine, i have locked several messages in my message base to keep them from being purged... those discussions were back in 2012 but apparently i failed to lock the ones concerning this format of the domain lines and i don't see anything in
the FAQ about it :(
it absolutely does make more sense... the real trick is to get
othernets to set up their own DNS lookup domain zones...
those discussions were back in 2012 but apparently i failed to lock
the ones concerning this format of the domain lines and i don't see
anything in the FAQ about it :(
Yes, I never knew about this format until you mentioned it here. Keen
to know more. It's not in any of my examples.
it absolutely does make more sense... the real trick is to get
othernets to set up their own DNS lookup domain zones...
What's involved in setting the lookup service up?
I can register and administer domains (have done for years, though in
this case, it would be a subdomain of an existing domain), and I
recently started an othernet, so I would be interested in what I'd
need to do to setup the service for my net.
Anyways ... my solution looks like this:
#defnode *
include /usr/local/etc/binkd.inc
mark lewis wrote to Tony Langdon <=-
What's involved in setting the lookup service up?
basically it is two parts...
1. have a script to convert the nodelist into a/some DNS zone files
for whatever DNS host server software is being used.
2. set up a DNS host server to use the zone files created in step 1
and allow public access to that DNS server so anyone in the
world can look up fzzz.nyyy.zxxx.your.domain.
i think i've covered most all of it... does it make sense to you??
1. have a script to convert the nodelist into a/some DNS zone files
for whatever DNS host server software is being used.
2. set up a DNS host server to use the zone files created in step 1
and allow public access to that DNS server so anyone in the
world can look up fzzz.nyyy.zxxx.your.domain.
Paul Hayton wrote to mark lewis <=-
Thanks Mark for the info..
This is something I have little experience in, but I too am interested
in setting something like this up. Tony, do you want to work together
on this?
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,023 |
| Nodes: | 17 (1 / 16) |
| Uptime: | 12:40:39 |
| Calls: | 502,255 |
| Calls today: | 9 |
| Files: | 103,940 |
| D/L today: |
11,197 files (3,150M bytes) |
| Messages: | 299,736 |