The DNS is only to find the reference between the callsign and the IP address. Entries would only be added once stations are authorised, so any delay would not affect the live routing.
IP Routing would take care of station moves, not DNS. Every repeater would look-up the callsign-to-IP address, and then simply IP route to destination. I completely agree that DNS is inappropriate for instantaneous moves. 73 David - G4ULF --- In [email protected], "Woodrick, Ed" <ewoodr...@...> wrote: > > > Don't believe that DNS updates are instantaneous. In common configuration, IP > address changes can easily take 6 hours. > > And if you pull the TTLs down to something short, you start to bang the heck > out of the centralized name servers. Whoops, let me say the one centralized > name server, because zone replication timeframes will also add a lot of delay. > > Ed WA4YIH > > From: [email protected] [mailto:[email protected]] On > Behalf Of Stewart Bryant > Sent: Monday, July 27, 2009 4:31 PM > To: [email protected] > Subject: Re: [DSTAR_DIGITAL] Re: First home-made dstar G2 gateway went live > today. > > > > dlake02 wrote: > > I completely agree with you David. This is an IP networking > problem easily solved by a mixture of DNS and IP routing. > We do not even need to worry about IP mobility, at the mobility > rates we are talking here regular convergence would work. > > I would partition the network into a mixture of IGP and BGP > just like the Internet. That allows you full scaling and > the ability to apply policy between the ASs. > > Callsign migration time would be limited by the b/w of the > links used, but I would be disappointed if it were > over a second within an IGP. > > I originally thought that this would need routing protocol > enhancements, but on thinking about it, from a > network perspective it would work right out of the box. > > Stewart/G3YSX >
