dotted hostname is bad IMO

Kevin Darcy kcd at
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?

                         - Kevin

On 1/31/2011 10:11 PM, pyh at wrote:
> given the domain name of "", and given an A RR in its zone is:
> s1.s2.s3  IN  A
> OK when a dns cache query for the first time, it will 
> follow the logic:
> #1, has NS RR in cache? (no)
> #2, has NS RR in cache? (no)
> #3, has NS RR in cache? (no)
> #4, has NS RR in cache? (yes most time, since is a 
> famous domain).
> #5, Goto's NS fetch the result.
> The process is complicated.
> But if the hostname is "", what will the dns cache do 
> by the first query? it will just do:
> #1, 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

More information about the bind-users mailing list