>> We are also considering storing IP information at a DNS server. Perhaps
 G> the
 >> default will be fidonet.net and the actual domain resolves down to the
 G> node
 >> number in the format of
 >>
 >> p.f.n.z.fidonet.net

 G> That would be the way to go, DNS is very efficient with large zones.

Let me explain what we are talking about doing and see what you think. We
have several methods via IP that a system can contact another system. On
popular method is using a protocol called BinkP. This protocol normally runs
on port 24554. But like any TCP protocol it can run on other ports. A node
may also have other IP capabilities (telnet, ftp, etc.) I will use my node
as an example. I support the following protocols and they are defined by
flags in our nodelist:

IBN = BinkP
IFT = FTP
ITN = TELNET
IFC = IFCIO

In my situation my /1 node number supports IBN on the standard port of
24554. I support FTP with two directory listing styles, DOS on port 21 and
Unix on 1021. Telnet is on port 60177. This is not telnet access to my BBS,
this a mailer to mailer connection via Telnet and IFCIO is on the standard
port of 60179. There are other IP capability flags but I am not utilizing
them at the moment.

We are thinking about using SRV (service location) records in DNS to store
the IP capability of a node. An application can query the DNS server to
gather the IP capabilities of a particular node. This may be needed if
protocols are run on different domains OR sub-domains. Our current nodelist
format is very limited in the information that we an add. IP capabilities
for fidonet nodes has really stretched our nodelist to the bounds of
breaking.

What do you think about an application request all this information from a
DNS server?

With best regards, Dale Ross.  E-mail: Dale.Ross{at}p1.f1.n379.z1.fidonet.org

--- Fidolook Lite FTN stub