[16979] in North American Network Operators' Group
Re: renumbering and roaming
daemon@ATHENA.MIT.EDU (Karl Denninger)
Mon May 18 15:10:14 1998
Date: Mon, 18 May 1998 13:59:28 -0500
From: Karl Denninger <karl@mcs.net>
To: "Michael S. Fischer" <otterley@iPass.COM>
Cc: nanog@merit.edu
In-Reply-To: <199805181838.LAA01696@dynamine.iPass.COM>; from Michael S. Fischer on Mon, May 18, 1998 at 11:38:04AM -0700
On Mon, May 18, 1998 at 11:38:04AM -0700, Michael S. Fischer wrote:
> In message <Pine.GSO.3.93.980518105250.8122N-100000@staff.uk.psi.com>, Paul Man
> sfield writes:
>
> >On Sun, 17 May 1998, Michael Dillon turned on his computer and typed:
> >> On Sun, 17 May 1998, Michael K. Smith:
> >>
> >> IMHO every dialup customer from every ISP in the world should use
> >> 192.168.254.1 for their DNS address and this number should be hard coded
> >> as the default in all client software. Then this problem would go away.
> >
> >if all ISPs agreed to use these addresses... say
> > - TWO resolvers, e.g. 192.168.254,1 and 192.168.253.1
> > - two mail relays, e.g. 192.168.254.5 and 192.168.253.5
> > - two news servers, e.g. ---254.9 and 253.9
> > - two ntp time servers
> > - etc etc
> >
> >[the addresses chosen for /30 netmasks, I think that in my Monday morning
> >brain-state I got it right?]
> >
> >And so on for "standard" services, then we could achieve global roaming SO
> >easily.
> >
> >The number of times we've had customers roam elsewhere and then try
> >and use ou r mail relays when for spam reasons relaying is denied...
>
> After several discussions, we came up with this solution that we think
> works well to support standard services for roaming users:
>
> Support a .local. root domain in your DNS servers. Examples of DNS
> hostnames would be mail.local., ntp.local., news.local., etc. When a
> roamer dials up he generally uses the DNS servers assigned by the NAS;
> these addresses would be authoritative on a provider-by-provider
> basis. If all networks supported this schema all users could simply
> have these addresses coded into their client software and would
> connect to the proper machines as they differ on various networks.
>
> iPass is currently building an Internet-Draft specifying the details
> of this approach. What do you think?
>
> --Michael
That doesn't work; too many of those things must be hard-coded numbers
(specifically, the DNS servers).
.LOCAL along with defined addresses, declared as "non-routable" (ie: local
only) *DOES* do the trick.
--
--
Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin
http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV
| NEW! Corporate ISDN Prices dropped by up to 50%!
Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS
Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost
