Re: Hosting Your Own Web Sites

Bryan, Jim, others

It seems to me then that Domain Name Re-Delegation is more management than
science.

And I guess if the decision was taken to generate options in outsourced
hosting [perhaps alongside of options of self hosting that Hadley has on the
list] and you wanted to make sure you had the speed to change built into it
then I see three components to outsourced hosting now:

1. Registration - Getting www.thisplace.com at 203.48.239.25 on that central
record.
2. Propagation - Getting www.thisplace.com at 203.48.239.25 scattered around
the traps.
3. Hosting - The actual serving of the pages and so on.

Seems like the action in Dynamic DNS is worth keeping an eye on in this
area. Maybe we'll see sites that will get your domain requested from a whole
heap of computers around the world instantly to get all those local records
along the way forced to be updated. A bit like sites that submit to heaps of
search engines - at least a similar business model.

Sounds like the perfect contract for hosting would include a TTL clause on
exit or internal changes.

Very interesting.

----- Original Message -----
From: "Bryan Britt" <beltane(at)beltane.com>
To: <hwg-business(at)mail.hwg.org>
Sent: Tuesday, December 11, 2001 4:53 AM
Subject: Re: Hosting Your Own Web Sites


> DNS Propagation is a function of two differnet systems, Registry and
> Nameservers. While what Jim said is certainly true regarding registries,
> there are ways around it.
>
> The .com/.net/.org world, i.e. The gtld-servers.net root servers, are
> updated only twice a day and operate as 11 independant primaries
> nameservers.  The new data is downloaded into them, and the process
> reloaded twice a day in each server, within minutes of each other.  The
> reason they aren't rotate-reloaded is because of the lag that would
> cause in propagating changes.
>
> However, in the .biz and the upcoming "newly redeveloped .us", and very
> possibly other new TLDs, updates will eventually be loaded into the
> NeuLevel gtld.biz nameservers every 15 minutes.
>
> This is the world of dynamic DNS.
>
> The rest of the propagation problem are the local configurations in your
> hosting nameservers.  Time-To-Live settings typically are set at 1 day
> or so, meaning that they don't recheck for updates until 24 hours is
> up.  This configuration is done on a domain-by-domain basis.
>
> I keep all of the domains that we host set on 3 hour TTLs, so any
> changes made propagate within hours though out the net.  Only on
> severely misconfigured networks would it take over 6 hours to make any
> changes.
>
> And here is a hint on changing IPs if you aren't changing the registered
> DNS nameservers.  Set your TTL to 5 minutes at least a day or two before
> the move.  Then when you are ready to fire up the new nameserver, make
> the change.  All traffic will be routed to the new IP within minutes.
> Then return the TTL to a normal value.
>
> With Dynamic DNS, TTLs are typically set very low to catch the changes.
>
>
>
> Bryan Britt
> Beltane Web Services
> WorldDOM.net Domain Registrations
>
>
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ICQ: 53037451
> Bryan L. Britt                                        501-327-8558
> Beltane Web Services, Conway, AR            http://www.beltane.com
> ~~~~~~~~~~Support Private Communications on the Internet~~~~~~~~~~
>
>
>
> On Mon, 10 Dec 2001 11:21:54 -0500 (EST)
> jim barchuk <jb(at)jbarchuk.com> wrote:
>
> > Hi John!
> >
> > > I want to be able to say "Fred will do it for $50. Your doing it for
$100.
> > > My client dosn't like me overspending his money. I need to flick to
Fred".
> > >
> > > Then I want to go online, type in the details of the redelegation.
Then wait
> > > a couple of minutes and see www.mycliensthopesanddreams.com take a
user to
> > > the new IP Address.
> > >
> > > Days does seem a long time.
> >
> > It is a technical fact that it can't happen that quickly. The delegation
> > can, but not propagation of that delegation throughout the net.
> >
> > I have experience only with netsol. They sometimes propagate 'on
> > schedule', 5am and 5pm, but sometimes totally wacky differences and
> > sometimes more than twice a day. It is possible to hit the server with
an
> > update just before a certain time but no telling if they'll hold to
their
> > schedule. Then, it takes time for -other- servers to 'ask' their uplinks
> > for update information. That can take hours (minimum) for major ISPs,
days
> > for many, or even -weeks- to reach the farthest points of the net. This
is
> > not the 'science' that the idea of the name 'computer science' may have
> > led you to believe.  :)
> >
> > Have a :) day!
> >
> > jb
> >
> > --
> > jim barchuk
> > jb(at)jbarchuk.com
>
>
>

HTML: hwg-business mailing list archives, maintained by Webmasters @ IWA