Ticket #1293 (new defect) — at Initial Version

Opened 11 years ago

Last modified 10 years ago

username.dialup persistent DNS service

Reported by: adehnert Owned by:
Priority: normal Milestone: The Distant Future
Component: linerva Keywords: transition
Cc: Fixed in version:
Upstream bug:

Description

One option for fixing #1176 would be for the load balancing infrastructure to automatically preferentially send you to your preferred dialup. (Another the wrapper script approach from comment:3:ticket:1176, seems more annoying for users.)

AIUI, given the way ssh and the dialups work right now, we could easily do this by having a DNS server that handled username.ist-dialup.sipb.org or so and maintained a persistent mapping of username -> dialup. Ideally, we could convince IS&T to take and maintain this, but SIPB running such a service would be a useful second choice. In any case, Jon suggests that prototyping such a service is a good first step.

Note: See TracTickets for help on using tickets.