Mark Andrews <mailto:[email protected]>
4 March 2015 08:04
In message<[email protected]>, Ray Hunter writes:
Ted Lemon<mailto:[email protected]>
4 March 2015 03:21
On Mar 3, 2015, at 4:55 PM, Ray Hunter<[email protected]> wrote:
One hour TTL could mean 24 times the DNS traffic compared to that historic
norm. It also could mean (re)signing DNSSEC zones more than 24 times per day
as hosts move around the homenet.......
Caching is really only interesting for query clusters and frequently access
ed domains. I don't think there is any reason to expect that there will be
performance issues for homenet names, which I would expect would be infrequen
tly accessed by relatively few resolvers.
If I'm following draft-ietf-homenet-front-end-naming-delegation, then
the hidden master is also located within the Homenet.
Doesn't that mean that the (hidden master) DNS server itself also has to
be renumbered?
And the new content synched with the slave servers (outside of homenet)
in a timely manner, before the old prefixes are expired?
Are the values suggested in section 4.2 for SOA appropriate then?
I understood a zone transfer was only triggered when the SOA contents
changed, and that was only checked once the slave refresh timer had expired.
Zone transfers on SOA timer expiry very rarely happen these days. NOTIFY
messages are the usual trigger.
Thanks. That rids me of one misconception then.
How does Homenet either update glue records for the domain on the
Internet TLD servers (if the master isn't hidden), or update the
configuration of the slave servers to point to the new address of the
hidden master (if the master is hidden), within an hour or less?
Is that something that can also be automated and e.g. be triggered by an
existing NOTIFY message?
Or would this mechanism need a new extension?
I'd rather not assume that the ISP was also the DNS provider.
Otherwise the slaves will lose connectivity to the hidden master (if the
master is hidden) . Or your glue records will be outdated and the name
resolution won't bootstrap at all (if the master isn't hidden).
You either have more name resolution traffic (every day), or you have more
temporary addresses and old prefixes hanging around for longer (during a ren
umbering event, which is presumably not every day).
Temporary addresses don't belong in the DNS. Stale information doesn't be
long in the DNS. This seems like a no-brainer to me.
--
Regards,
RayH
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
--
Regards,
RayH
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
