Keep having this idea pop in my head.. maybe a solution in search of a problem.. DNS servers often have text strings with all
sorts of stuff.. spf for ips allowed to send mail on behalf of a domain, domain ownership verfification.. yadda yadda
Could perhaps throw one in there like BBS=2323 or something so syncterm can find nonstandard ports on it's own.
Keep having this idea pop in my head.. maybe a solution in search of a problem.. DNS servers often have text strings with all
sorts of stuff.. spf for ips allowed to send mail on behalf of a domain, domain ownership verfification.. yadda yadda
Could perhaps throw one in there like BBS=2323 or something so syncterm can find nonstandard ports on it's own.
So "SRV" records a really for this: https://en.wikipedia.org/wiki/SRV_record
But your idea is good - could Syncterm read them? Best to find deuce in IRC or post a feature request on sourceforge
Keep having this idea pop in my head.. maybe a solution in search of
a problem.. DNS servers often have text strings with all sorts of
stuff.. spf for ips allowed to send mail on behalf of a domain, domain ownership verfification.. yadda yadda
Could perhaps throw one in there like BBS=2323 or something so
syncterm can find nonstandard ports on it's own.
Re: syncterm bbs port discovery
By: fusion to Digital Man on Thu Jul 07 2022 05:55 am
Keep having this idea pop in my head.. maybe a solution in search
of a problem.. DNS servers often have text strings with all sorts
of stuff.. spf for ips allowed to send mail on behalf of a domain,
domain ownership verfification.. yadda yadda
Could perhaps throw one in there like BBS=2323 or something so
syncterm can find nonstandard ports on it's own.
So "SRV" records a really for this:
https://en.wikipedia.org/wiki/SRV_record
On 7/6/22 22:55, fusion wrote:
Keep having this idea pop in my head.. maybe a solution in search of
a problem.. DNS servers often have text strings with all sorts of
stuff.. spf for ips allowed to send mail on behalf of a domain, domain ownership verfification.. yadda yadda
Could perhaps throw one in there like BBS=2323 or something so
syncterm can find nonstandard ports on it's own.
You could create an SRV record...
_telnet._tcp.foo.com 86400 IN SRV 10 5 2323 host.foo.com
https://www.cloudflare.com/learning/dns/dns-records/dns-srv-record/
However, it's on the client to actually support this... Might be interesting if web browsers supported this as well, to work around port blocking restrictions without having to specify a given port.
Also, an interesting thing to possibly add to a dyndns service/host for
BBS usage.
DM?
Nelgin wrote to All <=-
Keep in mind an SRV record hostname must point to a servers A or AAAA address and not a CNAME. Otherwise, seems reasonable.
Keep in mind an SRV record hostname must point to a servers A or
AAAA address and not a CNAME. Otherwise, seems reasonable.
My experience setting up DNS is long in the past, Bind 4.9 in 1993?
I don't recall if there was any downside to setting multiple A records pointing to one IP, versus one A record with multiple CNAME records
pointing to it?
No downside, aside from having to change multiple DNS entries when the originating IP changes?
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,033 |
Nodes: | 15 (0 / 15) |
Uptime: | 124:21:02 |
Calls: | 529 |
Calls today: | 23 |
Files: | 95,154 |
D/L today: |
4,436 files (587M bytes) |
Messages: | 298,889 |
Posted today: | 12 |