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
