1. [1] P. Mockapetris, “Domain names-concepts and facilities,” RFC 1034 (INTERNET STANDARD), Nov. 1987. Updated by RFCs 1101, 1183, 1348, 1876, 1982, 2065, 2181, 2308, 2535, 4033, 4034, 4035, 4343, 4035, 4592, 5936, 8020. 10.17487/rfc1034
2. [2] P. Mockapetris, “Domain names-implementation and specification,” RFC 1035 (INTERNET STANDARD), Nov. 1987. Updated by RFCs 1101, 1183, 1348, 1876, 1982, 1995, 1996, 2065, 2136, 2181, 2137, 2308, 2535, 2673, 2845, 3425, 3658, 4033, 4034, 4035, 4343, 5936, 5966, 6604, 7766. 10.17487/rfc1035
3. [3] K. Schomp, M. Allman, and M. Rabinovich, “DNS resolvers considered harmful,” Proc. 13th ACM Workshop on Hot Topics in Networks, HotNets-XIII, pp.16:1-16:7, ACM, New York, NY, USA, 2014. 10.1145/2670518.2673881
4. [4] J. Jung, E. Sit, H. Balakrishnan, and R. Morris, “DNS performance and the effectiveness of caching,” IEEE/ACM Trans. Netw., vol.10, no.5, pp.589-603, 2002. 10.1109/tnet.2002.803905
5. [5] J. Jung, A.W. Berger, and H. Balakrishnan, “Modeling TTL-based Internet caches,” IEEE INFOCOM 2003. Twenty-second Annual Joint Conference of the IEEE Computer and Communications Societies (IEEE Cat. no.03CH37428), vol.1, pp.417-426, March 2003. 10.1109/infcom.2003.1208693