|
|
 |  |
Re: Panther, shared internet, and QDNSFrom: Len Conrad Date: Monday, December 29, 2003
Time: 2:06:31 pm
>No, not true at all.
Yes, it's very definitely true as "best practice" in general. dynamic
updates and NOTIFY work better or even at all following this best practice.
>Think of the case of a hidden master server.
Stealth masters are not general usage, and one assumes that anybody setting
up a stealth master, would know what he's doing when diverging from best
practice.
And even with a stealth master, one of the public NS slaves can be the can
be the "primary slave" (and therefore in the mname field) slaved to the
stealth master, and to which the other NSs are slaved, further reducing the
traffic with and obscuring the stealth master.
>Len, can you provide an example scenario that matches what Bill has done?
no, but I've seen problems described in the bind-users list, so check those
archives.
I'm really conservative in my DNS setups, and when I fix other peoples'
DNS, so I don't have these subtle problems in my experience.
>- A given server is mentioned twice, by different names, in the delegation
>records.
To encourage redundancy in DNS, registrars used to prevent registering more
than hostname for the same IP. That's still good practice, for the same
reasons.
It's obviously not fatal to register at the parent NS two hosts for the
same IP. But I don't consider registering, eg, "vanity" hostnames as best
practice.
>One of these names is not used in the authority records.
>
>- Another server is listed in the authority records
authority records (the onse that delegate authority), imo, ARE the
delegation records. Do you mean the zone NS records?
>but not the delegation records.
DNS is confusing and mysterious enough for most people that being tricky or
whatever is really not a good idea.
Len
|

Return to Digital Point Solutions' Home Page |