Dec 09 11:49 2018, Carol Shenkenberger wrote to Markus Reschke:
MR>> Wouldn't we get two FTS docs contradicting each other then???
CS> Not if we align them. Take what is in existing use, see what the CS> differences are, then what tools already use them and see what works.
The FTSC documented one: - if there's an address in the IBN flag use that one and only that one - if the IBN flag doesn't include an address take all the addresses from all INA flags
The undocumented standard: - take all addresses in IBN and INA flags
Q: How ports are handled by the undocumented standard? If we have INA:my-bbs.ddns.org and IBN:my-bbs.dyndns.com:8080 for example, does the port number also apply the the address in the INA flag?
CS> This isn't a really common thing to see (a site with 2 lookup CS> addresses). I'd say most of us with 2 have a reason for it. Mine is CS> backup connectivity for the most part. I've had one or the other go CS> off for a bit and with the game league (Battlenet) that can get nasty CS> fast.
Over here most of the distribution nodes have several FQDNs for resilience. If one dyn-DNS service fails the node is still reachable via its second FQDN.
