You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose that we first check for a SRV record of service adtp (AirDispatch Tracker Protocol) before resolving the tracker address. That way, one url like airdispat.ch can point to a 'messier' tracker url like tracker.airdispat.ch.
The text was updated successfully, but these errors were encountered:
I'd require specification of tracker.airdispat.ch vs infering based of the record of service. Yes, it would probably clean things up, but being explicit has its merits.
Three addressing types
used by computers
yours (username@tracker - queries tracker for username, download address, ???, profit)
Text record on DNS tracking server - querying tracker server first time is like sshing into another server. Assume DNS is secure, DNS gives correct AD address
jhleath
added a commit
to airdispatch/airdispatch-go
that referenced
this issue
Jul 5, 2013
I propose that we first check for a SRV record of service
adtp
(AirDispatch Tracker Protocol) before resolving the tracker address. That way, one url likeairdispat.ch
can point to a 'messier' tracker url liketracker.airdispat.ch
.The text was updated successfully, but these errors were encountered: