Its on the TODO list and I don't anticipate it taking too much effort to add support for the lookup portion, but I haven't done it yet.
If its something you'll use I can get it in there pretty soon, assuming
I have access to a DNS to test with.
g00r00,
Does Mystic's BinkP server support FTS-5004: the DNS Distributed
Nodelist ?
As for DNS to test with, SciNet meets the FTS spec for distributed
DNS, scinet-ftn.org.
On 02-23-20 08:00, g00r00 wrote to Netsurge <=-
Does Mystic's BinkP server support FTS-5004: the DNS Distributed
Nodelist ?
Its on the TODO list and I don't anticipate it taking too much effort
to add support for the lookup portion, but I haven't done it yet.
If its something you'll use I can get it in there pretty soon, assuming
I have access to a DNS to test with.
On 02-22-20 20:52, Netsurge wrote to g00r00 <=-
Its on the TODO list and I don't anticipate it taking too much effort to add support for the lookup portion, but I haven't done it yet.
If its something you'll use I can get it in there pretty soon, assuming
I have access to a DNS to test with.
The main hub for SciNet isn't running Mystic's BinkD server, but I do
have a lot of downlinks who do. No rush, it was more curiosity.
As for DNS to test with, SciNet meets the FTS spec for distributed DNS, scinet-ftn.org.
Which now leads me to ask, when will we see you in SciNet, lol.
cool! that makes 4 out of 70 FTNs i know of that support DNS lookups for their nodes :)
cool! that makes 4 out of 70 FTNs i know of that support DNS
lookups for their nodes :)
which ones are they Mark?
Domain DNS Lookup Domain Zone(s)
-------- ----------------- ---------
fidonet binkp.net 1-6
fsxnet fsxnet.nz 21
scinet scinet-ftn.org 77
vkradio ftn.vkradio.com 432
-1, fsxnet.nz is still broken for non-standard ports (and the main hub is on port 24556)
what do you mean by broken? specifically, please...
-1, fsxnet.nz is still broken for non-standard ports (and the main hub
is on port 24556)
cool! that makes 4 out of 70 FTNs i know of that support DNS
lookups for their nodes :)
which ones are they Mark?
Domain DNS Lookup Domain Zone(s)
-------- ----------------- ---------
fidonet binkp.net 1-6
fsxnet fsxnet.nz 21
scinet scinet-ftn.org 77
vkradio ftn.vkradio.com 432
On 02-26-20 18:22, Oli wrote to mark lewis <=-
24 Feb 20 10:22, you wrote to Paul Hayton:
cool! that makes 4 out of 70 FTNs i know of that support DNS
lookups for their nodes :)
which ones are they Mark?
Domain DNS Lookup Domain Zone(s)
-------- ----------------- ---------
fidonet binkp.net 1-6
fsxnet fsxnet.nz 21
scinet scinet-ftn.org 77
vkradio ftn.vkradio.com 432
-1, fsxnet.nz is still broken for non-standard ports (and the main hub
is on port 24556)
Thanks Oli. Are you meaning the HUBs (there's more than one) should be on 24554? Or do you mean that the zone file should reflect that if HUBs are not on port 24554 then it should be reflected in the zone file as per FTS-5004 ?
Yep, fsxnet.nz still needs some SRV records, especially for its /1 hub,
so I would agree, it is currently broken.
On 02-26-20 13:51, mark lewis wrote to Oli <=-
-1, fsxnet.nz is still broken for non-standard ports (and the main hub is
on port 24556)
what do you mean by broken? specifically, please...
On 02-26-20 22:09, Netsurge wrote to Tony Langdon <=-
Yep, fsxnet.nz still needs some SRV records, especially for its /1 hub,
so I would agree, it is currently broken.
As it stands, if someone was using a domain alias for fsxnet.nz in
binkd or argus or any other binkp server and tried to use the dns
lookup mail would never get to Avon.
This is a serious issue as it would impede mail flow to him and
everyone else who is using a non standard port on any I** flag.
-1, fsxnet.nz is still broken for non-standard ports (and the main hubis
on port 24556)
what do you mean by broken? specifically, please...
Oli is referring to the lack of SRV records for fsxnet.nz, which makes systems
on non standard ports (for any listed protocol) unreachable when using DNS lookups. This is a particularly serious issue, because one of the main hubs
uses a non standard port.
The missing SRV records don't seem to be an issue in fsxnet, because maybe nobody uses it.
Maybe that's the case now, but the implmentations still need to adhere
to the standard.
On 02-27-20 08:25, Oli wrote to Tony Langdon <=-
Interestingly, my binkd (latest version with FTS-5004 enabeled) doesn't try to lookup SRV records at all. I don't know if it is a specific
problem on my system or if it is a bug in binkd. I wouldn't be
surprised if nobody else recognized it, because only a few nodes use binkp.net and only a few nodes are on non-standard ports.
The missing SRV records don't seem to be an issue in fsxnet, because
maybe nobody uses it.
On 02-28-20 12:22, Paul Hayton wrote to Tony Langdon <=-
On 28 Feb 2020 at 09:17a, Tony Langdon pondered and said...
The missing SRV records don't seem to be an issue in fsxnet, because maybe nobody uses it.
Maybe that's the case now, but the implmentations still need to adhere
to the standard.
Have another check please :)
_binkp._tcp.f100.n1.z21.fsxnet.nzServer: 127.0.1.1
That looks better.No A or AAAA records, looks like you're using the same script as me. :) But at least the SRV is there.
On 02-28-20 19:23, Paul Hayton wrote to Tony Langdon <=-
On 28 Feb 2020 at 03:03p, Tony Langdon pondered and said...
That looks better.No A or AAAA records, looks like you're using the same script as me. :) But at least the SRV is there.
Thanks it's a work in process. I am going to take this thread over to fsxNet now as we're not really talking about anything to do with Mystic now.
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 28 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 147:28:25 |
| Calls: | 2,001 |
| Calls today: | 2 |
| Files: | 11,112 |
| Messages: | 943,413 |