Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 08 Aug 2000 01:29:19 -0600
From:      Chris Fedde <chris@fedde.littleton.co.us>
To:        Bigwillie <mvanberk@optonline.net>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: DNS/BIND 
Message-ID:  <200008080729.e787TJ000165@fedde.littleton.co.us>
In-Reply-To: <4.2.0.58.20000808014707.00a2abd0@mail-hub.optonline.net> 

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 08 Aug 2000 01:52:56 -0400  Bigwillie wrote:
 +------------------
 | Thanks for the link, seems very informative.  Bottom line is that I cant do 
 | what I want to do, because of the lack of Broadband ISPs in my area (NJ 
 | sucks in more ways than one, Bellatlantic/Verizon crap).  Its not easy, to 
 | be bitten by the BSD (Unix) bug, and not being able to do anything about it.
...
 | I just have to wait here bleeding till I can get access to some IP 
 | addresses on a fat pipe.......
 | Sorry for the rant.
 +------------------

I don't think that I would throw in the towel just yet...

You can still run your own domain even if you don't have a static
IP address.  Here are some things to think about.

DNS is really a low bandwidth kind of thing.  Especially if you are
doing it for only a few dozen hosts on a home network.

You can set up a caching-only name server for your home network
without having a static ip address.  This server can be configured
to bootstrap from the root servers or can be setup to forward
through an ISP server.  Your inside clients are then configured to
talk to this server rather than the ISP's.

You can run a zone for your home network that is not glued to the
internet at all. In fact this is exactly what you want for the
private address space.  It's just a matter of thinking through the
issues then setting up the correct zone files and config entries.

Most ISP's will manage a domain for you. They generally don't even
charge much to do it.  But it's a gas to do it yourself.

Beyond bragging rights there are a few other reasons to bring up a public
domain on your home server.  One of them is that you want to serve
web pages off it.  Another is so that you can handle your own
inbound mail.

If you watch the IP address that is assigned to your host you will probably
notice that it dosn't change very often.  It's an interesting exersize to
write a test script that lets you track address changes.   In some cases
the address dosn't change at all.

Your regestered name servers don't have to be in your domain.
You just need to find a couple folks who are regestered them selves
and are gullable enough to host the zones for you.  There are lots of
options for administering zone files these range from simple ftp or ssh
uploads through dynamic DNS with many options along the way.

Hope that this note helps
chris

--
    Chris Fedde
    303 773 9134


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200008080729.e787TJ000165>