Re: simple domain

[Jonathan Q <jq@example.com>]

Stephen J. Turnball (turnbull@example.com) wrote:

Stephen>     cs> Huh?  That's an internic thing ...
Stephen> 
Stephen> Ah ... yes.
Stephen> 
Stephen> Still, he does need to register his nameserver upstream, right?  And

Well, you need your ISP's cooperation.  Usually, they won't be very
interested in giving that cooperation if your DNS server doesn't have
a 7 x 24 Internet connection.  If you don't have 7 x 24, but you do
have a fixed IP address, they couldn't absolutely stop you from
registering your machine with Internic as the authoritative NS for your
domain, but there is a very great deal they can do to make that work
poorly.  Or they can put in an access list and make it not work at all.
Even if they don't quite go that far, they won't delegate the reverse DNS
to you and they won't act as secondary DNS for you, so when you're offline
you disappear.  Unless you've got a buddy who runs a DNS server somewhere
else who will act as secondary for you.

And then you hope your ISP doesn't filter incoming DNS requests to their
dialup pools.

As you mention, for those on dialup connections with dynamically
assigned IP addresses, dyndns is the only answer.  Even then, 
anything that depends on matching forward and reverse DNS
will break, since dyndns naturally can't give reverse lookup
for your IP address.

As someone else mentioned, virtual hosting is very cheap.  I doubt
it's worth the hassle of going through dyndns, even if your ISP
does allow running a server on a dialup connection.

Jonathan