Re: dotted hostname is bad IMO

2011-02-02 Thread Kevin Darcy
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, p...@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  11.22.33.44
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@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users






___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: dotted hostname is bad IMO

2011-02-01 Thread Barry Margolin
In article mailman.1600.1296530179.555.bind-us...@lists.isc.org,
 p...@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  11.22.33.44 
 
 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.

I don't think it's something you need to worry about.  DNS servers 
organize their cache data structures to make steps 1-4 easy to perform 
all at once.

Time to pull out your copy of Knuth Sorting and Searching.

-- 
Barry Margolin, bar...@alum.mit.edu
Arlington, MA
*** PLEASE don't copy me on replies, I'll read them in the group ***
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: dotted hostname is bad IMO

2011-02-01 Thread Joseph S D Yao
On Tue, Feb 01, 2011 at 11:11:47AM +0800, p...@mail.nsbeta.info wrote:
...
 So I dont think dotted hostname is good pratical.
...


You need to read the whole posting.  Another poster pointed out that the
dot  _ I S _  the DNS delimiter.


--
/*\
**
** Joe Yao  j...@tux.org - Joseph S. D. Yao
**
\*/
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users