OT: DNS Zone policy and hidden masters (was: Re: OT?: Emailing from within filepro)

[Jay R. Ashworth]

On Sat, May 29, 2004 at 02:00:07PM -0400, Fairlight wrote:
> I won't get into putting a primary nameserver on DSL.  Well, yes I will,
> since DSL has absolutely zero guarantee of service under FCC regulations.
> Doesn't matter what your contract with the telco says--under regs, they
> don't have to fix it, you don't have any recourse if they don't.  This
> means that if you want one on your side of the demarcation point, it
> should be the secondary, not the primary, as that way at least the primary
> would always be active and you'd have less delay.  As it happens, this
> wouldn't normally cause much of a problem, as the system is designed to
> have secondaries for a reason.

Actually, the sugested solution to this problem is to tell the world
your ISP's NS is your primary (list it first), but tell that server
it's a slave -- to your "real" "hidden" master server behind the DSL
line.  If your zone expire time is long enough, and both servers do
NOTIFY, this gets you the best of both worlds.

And remember, the reason for the short TTL is merely to avoid *clients*
from caching an address you know is about to change; that's independent
of the zone and expiration issues.

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra at baylink.com
Member of the Technical Staff     Baylink                             RFC 2100
The Suncoast Freenet         The Things I Think
Tampa Bay, Florida        http://baylink.pitas.com             +1 727 647 1274

        "They had engineers in my day, too."  -- Perry Vance Nelson