dotted hostname is bad IMO
kcd at chrysler.com
Wed Feb 2 14:37:17 UTC 2011
So, let me see if I have this correctly: you think that DNS architects
and/or planners should constrain their choices with respect to namespace
layout and/or delegation hierarchy, because of some minor performance
considerations, based on your _speculations_ (without any hard evidence)
about how certain cache-fetching algorithms are coded?
On 1/31/2011 10:11 PM, pyh at mail.nsbeta.info wrote:
> given the domain name of "126.com", and given an A RR in its zone is:
> s1.s2.s3 IN A 220.127.116.11
> OK when a dns cache query for s1.s2.s3.126.com the first time, it will
> follow the logic:
> #1, s1.s2.s3.126.com has NS RR in cache? (no)
> #2, s2.s3.126.com has NS RR in cache? (no)
> #3, s3.126.com has NS RR in cache? (no)
> #4, 126.com has NS RR in cache? (yes most time, since 126.com is a
> famous domain).
> #5, Goto 126.com's NS fetch the result.
> The process is complicated.
> But if the hostname is "s1-s2-s3.126.com", what will the dns cache do
> by the first query? it will just do:
> #1, 126.com has NS RR in cache? (yes)
> #2, go there fetching the reqult.
> It's much simple and fast.
> So I dont think dotted hostname is good pratical.
> bind-users mailing list
> bind-users at lists.isc.org
More information about the bind-users