Subj : proposed new nodelist
To   : Johannes Lundberg
From : Malcolm Miles
Date : Wed Oct 09 2002 04:35 pm

On Jul 20, 2002 Johannes Lundberg wrote to Peter Knapper:

JL> I thought a bit of this. Using sub-domains for
JL> services/transport-protocols work quite well? IE, to find out if
JL> host 2:206/149 has binkp-access, you simply resolve
JL> 'binkp.f149.n206.z2.fidonet.net'. And to list the services
JL> available, you do a zone transfer on f149.n206.z2.fidonet.net. Port 
JL> specification could be solved with a record looking like
JL> 'p4001.binkp.f149...'. The old BinkD @fidonet.net way would still
JL> work, as the f149-record would point to the right IP already. And
JL> new software developers would be instructed in using the new format.

JL> (This could also be done using a IN HINFO-record in the DNS, to
JL> avoid zone transfers)

Better to use the SRV record as this directly returns a host and a port eg:

>dig srv _binkp._tcp.f260.n633.z3.fidonet.org

; <<>> DiG 8.3 <<>> srv _binkp._tcp.f260.n633.z3.fidonet.org
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, 
ADDITIONAL: 1
;; QUERY SECTION:
;;      _binkp._tcp.f260.n633.z3.fidonet.org, type = SRV, class = IN

;; ANSWER SECTION:
_binkp._tcp.f260.n633.z3.fidonet.org.  1D IN SRV  0 0 24554 fido.tardis.net.

shows that to make a binkp connection to 3:633/260 connect to fido.tardis.net 
on port 24554.

Best wishes,
Malcolm

--- timEd/386 1.10.y2k+
 * Origin: Tardis BBS +61 3 9819 7093 (3:633/260)

.