From: perry at piermont.com (Perry E. Metzger)
Subject: [COFF] [TUHS] RetroNet… Virtual is cheap.
Date: Thu, 6 Sep 2018 15:42:40 -0400 [thread overview]
Message-ID: <20180906154240.6fdbdc68@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <2dcff0e3-139e-5a5f-b5b6-0f01debe4ff8@spamtrap.tnetconsulting.net>
On Thu, 6 Sep 2018 10:24:09 -0600 Grant Taylor via COFF
<coff at minnie.tuhs.org> wrote:
> On 09/06/2018 09:41 AM, Perry E. Metzger wrote:
> > Why not just dynamic update whenever the lease is renewed? If
> > nothing changes, no one will see any change. (I've run like that
> > for 15 years I think...)
>
> That does work from a client point of view.
>
> From a DNS administrators point of view, it's likely to cause
> unnecessary updates to the zone and subsequent transfers to slave
> servers. All of which is unnecessary.
I guess I've always viewed my time as being worth more. The data
being transferred is a few k, smaller than the size of one icon on my
desktop, I doubt the communications overhead is noticed in the
hailstorm of video going over the networks in question. Your Milage
May Differ.
Perry
--
Perry E. Metzger perry at piermont.com
next prev parent reply other threads:[~2018-09-06 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f3f250f4-cffd-794c-450a-d1c3829c890e@spamtrap.tnetconsulting.net>
[not found] ` <1535565898.3905695.1490376112.4B7D3E18@webmail.messagingengine.com>
[not found] ` <6e7783fb-ff06-2e21-002f-76bef263b63c@spamtrap.tnetconsulting.net>
[not found] ` <1d8c0539-8b43-9954-d8a7-db4dcc22b27d@texoma.net>
[not found] ` <e0aa9929-d1fc-43fb-8eae-1c2bad859244.maildroid@localhost>
[not found] ` <ff99cbb7-1069-9a08-2e41-d1781fe91125@texoma.net>
2018-08-31 17:33 ` gtaylor
2018-09-01 22:20 ` peter
2018-09-02 2:00 ` gtaylor
2018-09-06 15:41 ` perry
2018-09-06 16:24 ` gtaylor
2018-09-06 19:42 ` perry [this message]
2018-09-06 21:13 ` gtaylor
2018-09-10 6:35 ` dave
2018-09-13 21:39 ` perry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180906154240.6fdbdc68@jabberwock.cb.piermont.com \
--to=coff@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).