My local cable company, Bend Cable, gives out static IP with RoadRunner
service.
I also know several folks on @Home in Fremont, CA, that have static
IP addresses.
Our dedicated accounts get static, as I am sure is the case with most ISPs.
Non-dedicated can get static only for a fee. The rate structure starts at
$8 for a /32 and goes up to about 25% above the ARIN fee for address space.
The customer must also assert why they need it.
I just wish I could swip the /30's, /31's, and /32's we give out, to ARIN.
We're putting in more NAT and proxy boxes for businesses and are doing more
networks smaller than /29 these days. Yet ARIN still encourages us to use
a /29 when a /32 would do. I'll probably swip the /29 containing them as
just a commentary saying something like "contains /32 assignments" when I
get my network database going.
What this means is that ARIN is restricting the DNS management. If you have
less than a /29 then you are not allowed to manage your own domain-space
without a handler. That handler is the ISP. To be honest, most of our /29's
are too clueless to handle DNS, in fact most of them are Microsoft-only
LANs whom I don't trust DNS to anyway. I have yet to see a BIND port to any
version of Windows, with resolver library, that worked. Gotta have a Unix
box in the LAN somewhere in order to do that ( and a bunch else besides).
Most of our /29's cann't even spell Unix.
I take that back, I was just informed that we have some Apple-talk and
Novell LANs as well.
Why? Assuming you assign those blocks out of a larger block (i.e. you
give out /30's out of a /25), when it comes time to apply for more space,
you just tell ARIN blah/25 is split up into /30's for dedicated customers
using NAT. You probably won't get any argument beyond them possibly
asking for a list of who the customers are.
---dont't waste your cpu, crack rc5...www.distributed.net team enzo---
Jon Lewis <jlewis@fdt.net> | Spammers will be winnuked or
Network Administrator | nestea'd...whatever it takes
Florida Digital Turnpike | to get the job done.
______http://inorganic5.fdt.net/~jlewis/pgp for PGP public key________
Just the /29 users? DNS is irrelevant. ARIN only watches over IPv4
address space utilization. OK...they also handle in-addr.arpa delegations
for the space they look after, but the fact that they don't want swips of
/29 or longer prefixes has nothing to do with who can manage DNS.
---dont't waste your cpu, crack rc5...www.distributed.net team enzo---
Jon Lewis <jlewis@fdt.net> | Spammers will be winnuked or
Network Administrator | nestea'd...whatever it takes
Florida Digital Turnpike | to get the job done.
______http://inorganic5.fdt.net/~jlewis/pgp for PGP public key________
If you are not handling your own in-addr.arpa then you are not fully
managing your own DNS name space. In *many* cases, if the reverse does not
match the forward reference then access will be denied.
[ On Sun, November 8, 1998 at 23:23:01 (-0500), Jon Lewis wrote: ]
Subject: Re: ARIN?
> What this means is that ARIN is restricting the DNS management. If you have
> less than a /29 then you are not allowed to manage your own domain-space
> without a handler. That handler is the ISP. To be honest, most of our /29's
> are too clueless to handle DNS, in fact most of them are Microsoft-only
Just the /29 users? DNS is irrelevant. ARIN only watches over IPv4
address space utilization. OK...they also handle in-addr.arpa delegations
for the space they look after, but the fact that they don't want swips of
/29 or longer prefixes has nothing to do with who can manage DNS.
It seems ARIN won't publish IN-ADDR.ARPA delegations smaller than /16
these days yet there are many legacy blocks within their control which
are no longer managed by the ISPs they are delgated to. Some ISPs are
forced to manage IN-ADDR.ARPA space (i.e. they must offer secondary DNS
services) for /24s they have no other dealings with. Although in theory
one might imagine this would balance out, in practice it does not. In
practice it even breaks down when some such ISPs refuse to secondary /24
IN-ADDR.ARPA zones for networks they no longer route.
If all the backbone operators were to run separate IN-ADDR.ARPA servers
(i.e. separate from the current set of DNS root servers) then there
would be no valid technical objection to directly delegating every
assigned /24 or larger network from those servers.
There should also be no objection for listing all assigned /30 networks.
I'm not talking about dial-up users -- but fully routed dedicated
customers using only a /30 or more. I *WANT* to see these networks in
whois lookups! These listings should be *required*.
RWhois would be great if it worked in practice, but as yet it doesn't.
Too many claimed rwhois servers don't even exist.
One thing I would dearly love to see is support in client rwhois
implementations for referrals. Today, if I query the root rwhois
server at rwhois.net, I don't end up with a clear answer as to who
the network block has been delegated. I have to manually try and
find the rwhois server [if any] for the smallest block returned, and
see if there are further delegations being made.
At Vitts, we're attempting to document in our rwhois server, every
network assignment we make. This includes the /30's. We have a handful
of 1 IP customers that are connected to the Internet using a router
running NAT or firewall software. It makes it easier for us to have
a standards based way of identifying the owner for every IP address
we manage.