On Tue, Sep 23, 2003 at 10:13:32PM -0600, Mark McDonald wrote:
> I've registered my domain.
> Now I'd like to serve it.
You've received a lot of suggestions to get hosting from your ISP,
dyndns.org, etc. They're all valid--one of the things that you really
have to commit to if you run your own DNS server is 24x7 uptime.
However, none of the posts I've seen have really answered your underlying
question--how does the world know about you, once your DNS name is
registered? And a subtext--what happens if your IP address changes?
(Sometimes due to administrative requirements, most often these days
because people are using dynamic IP addresses.)
In the first case, the answer is that you have to find at least one site
already running DNS to agree to be a "secondary" for you; usually, it's
a good idea to have two or more. Then, you submit your IP address, and
that of your secondary/ies, to your registrar; that is, whoever accepted
your application for your domain. They'll store the IP addresses of
your primary and secondary nameservers, so whenever anyone asks for your
domain they can be directed to those machines for detailed information.
Where do you find secondaries? Well, there's always the old way--find
a friend who's already running a DNS server. These days, most people
have to pay someone--your ISP will almost always be willing to host a
secondary or even primary. Note that you can't pick a server out of
the thin air; they have to modify their DNS server configuration files
to allow DNS updates from you or your primary.
Finally "almost" static address is a problematic statement. If it's not
really static, then you're going to lose DNS service whenever it changes.
If changing is really a rare thing--f'rinstance, many ISPs use DHCP
just as an address pool manager, and never really change your address
after it's assigned--you can manually correct it whenever it happens.
IF you can tolerate a couple of days of disruption while you (a) find
out you're dead, and (b) update your primary DNS records and push updates
to your secondaries, then wait while it propagates throughout the 'Net;
OTOH, others will zap your address assignment every time your cable/dsl
modem reboots. In that case, you have to be able to handle dynamic DNS;
and I will join the chorus in suggesting you get in touch with someone like
dyndns.org.
Hope this helped give you some of the underlying info on how you'd set up
DNS...
--
Dave Ihnat
[EMAIL PROTECTED]
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list
