What about for redundancy being able to list multiple host/ip addresses
for an ION entry?

Chris

 wrote in message news:1041272570.716.0{at}tkdsoftware.com...
> >> In my first attempt at XML nodelist I had most of these as a child
http://harborwebs.com:8080/Net379/v0.0.5.NET379.XML
>
>  >> points should be a child to node, I believe. Points should have
similar
>  >> if not the same attributes /children as a node.
>
>  >> With best regards, Dale Ross.  E-mail:
>  >> Dale.Ross{at}p1.f1.n379.z1.fidonet.org
>
>  WS>      Hmm...  how about ION connection type?  That is, which piece of
>  WS> information  to pay attention to....  Is the ION a Static IP -- i.e.
>  WS> the QUAD number never changes and can be listed by number?  Or, is
the
>  WS> ION a Dynamic IP -- i.e. the DNS name never changes, but rather
points
>  WS> to an ever changing dynamic QUAD number pool.  (For example, my
router
>  WS> just went down and none of my new name servers know of HarborWebs.  I
>  WS> had to Telnet in via Quad Number or I wouldn't get in at all!)
>
> We are also considering storing IP information at a DNS server. Perhaps
the
> default will be fidonet.net and the actual domain resolves down to the
node
> number in the format of
>
> p.f.n.z.fidonet.net
>
> p=point
> f=node
> n=net
> z=zone
>
> So I would not be harborwebs.com, I would be f1.n379.z1.fidonet.net
because
> my node number is 1:379/1. Either I would handle the dns at
> f.n.z.fidonet.net OR a CNAME record would be at that location pointing to
> harborwebs.com
>
> We can certainly add an attribute of
>
> ipAddress='nnn.nnn.nnn.nnnn'
>
> Please do share your thoughts on this.
>
> With best regards, Dale Ross.  E-mail: Dale.Ross{at}p1.f1.n379.z1.fidonet.org
>
> --- Fidolook Lite FTN stub
> PATH: 379/1



--- Mail-ennium/32 v1.01.301.9/#01-0001