Academic literature on the topic 'Multicast Domain Name System'

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Multicast Domain Name System.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Multicast Domain Name System"

1

Hanna, Fouad, Lionel Droz-Bartholet, and Jean-Christophe Lapayre. "Toward a Faster Fault Tolerant Consensus to Maintain Data Consistency in Collaborative Environments." International Journal of Cooperative Information Systems 26, no. 03 (August 14, 2017): 1750002. http://dx.doi.org/10.1142/s0218843017500022.

Full text
Abstract:
The consensus problem has become a key issue in the field of collaborative telemedicine systems because of the need to guarantee the consistency of shared data. In this paper, we focus on the performance of consensus algorithms. First, we studied, in the literature, the most well-known algorithms in the domain. Experiments on these algorithms allowed us to propose a new algorithm that enhances the performance of consensus in different situations. During 2014, we presented our very first initial thoughts to enhance the performance of the consensus algorithms, but the proposed solution gave very moderate results. The goal of this paper is to present a new enhanced consensus algorithm, named Fouad, Lionel and J.-Christophe (FLC). This new algorithm was built on the architecture of the Mostefaoui-Raynal (MR) consensus algorithm and integrates new features and some known techniques in order to enhance the performance of consensus in situations where process crashes are present in the system. The results from our experiments running on the simulation platform Neko show that the FLC algorithm gives the best performance when using a multicast network model on different scenarios: in the first scenario, where there are no process crashes nor wrong suspicion, and even in the second one, where multiple simultaneous process crashes take place in the system.
APA, Harvard, Vancouver, ISO, and other styles
2

Dettmer, R. "What's in a name [Internet Domain Name System]." IEE Review 49, no. 11 (December 1, 2003): 38–40. http://dx.doi.org/10.1049/ir:20031105.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Bonastre, Oscar M., Andreu Vea, and David Walden. "Origins of the Domain Name System." IEEE Annals of the History of Computing 41, no. 2 (April 1, 2019): 48–60. http://dx.doi.org/10.1109/mahc.2019.2913116.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Casalicchio, E., M. Caselli, and A. Coletta. "Measuring the global domain name system." IEEE Network 27, no. 1 (January 2013): 25–31. http://dx.doi.org/10.1109/mnet.2013.6423188.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Mockapetris, Paul V., and Kevin J. Dunlap. "Development of the Domain Name System." ACM SIGCOMM Computer Communication Review 25, no. 1 (January 11, 1995): 112–22. http://dx.doi.org/10.1145/205447.205459.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Mockapetris, P., and K. J. Dunlap. "Development of the domain name system." ACM SIGCOMM Computer Communication Review 18, no. 4 (August 1988): 123–33. http://dx.doi.org/10.1145/52325.52338.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Qin, Zhen, Chunjing Xiao, Qiyao Wang, Yuehui Jin, and Aleksandar Kuzmanovic. "A CDN-based Domain Name System." Computer Communications 45 (June 2014): 11–20. http://dx.doi.org/10.1016/j.comcom.2014.03.021.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Li, Bo, and Jinlin Wang. "An Identifier and Locator Decoupled Multicast Approach (ILDM) Based on ICN." Applied Sciences 11, no. 2 (January 8, 2021): 578. http://dx.doi.org/10.3390/app11020578.

Full text
Abstract:
Many bandwidth-intensive applications (such as online live, online games, etc.) are more suitable for using multicast to transmit information. Due to the advantages in scalability, Shared Tree (ST) is more suitable for large-scale deployment than Source-Based Tree (SBT). However, in ST-based multicast, all multicast sources need to send multicast data to a center node called a core, which will lead to core overload and traffic concentration. Besides, most existing multicast protocols use the shortest path between the source or the core and each receiver to construct the multicast tree, which will result in traffic overload on some links. In this paper, we propose an Identifier and Locator Decoupled Multicast approach (ILDM) based on Information-Centric Networking (ICN). ILDM uses globally unique names to identify multicast services. For each multicast service, the mapping between the multicast service name and the addresses of multicast tree nodes is stored in the Name Resolution System (NRS). To avoid core overload and traffic aggregation, we presented a dynamic core management and selection mechanism, which can dynamically select a low-load core for each multicast service. Furthermore, we designed a path state-aware multicast tree node selection mechanism to achieve traffic load balancing by using low-load links more effectively. Experimental results showed that our proposed multicast approach outperformed some other multicast methods in terms of core load, number of join requests, link load, traffic concentration, and routing state.
APA, Harvard, Vancouver, ISO, and other styles
9

Li, Bo, and Jinlin Wang. "An Identifier and Locator Decoupled Multicast Approach (ILDM) Based on ICN." Applied Sciences 11, no. 2 (January 8, 2021): 578. http://dx.doi.org/10.3390/app11020578.

Full text
Abstract:
Many bandwidth-intensive applications (such as online live, online games, etc.) are more suitable for using multicast to transmit information. Due to the advantages in scalability, Shared Tree (ST) is more suitable for large-scale deployment than Source-Based Tree (SBT). However, in ST-based multicast, all multicast sources need to send multicast data to a center node called a core, which will lead to core overload and traffic concentration. Besides, most existing multicast protocols use the shortest path between the source or the core and each receiver to construct the multicast tree, which will result in traffic overload on some links. In this paper, we propose an Identifier and Locator Decoupled Multicast approach (ILDM) based on Information-Centric Networking (ICN). ILDM uses globally unique names to identify multicast services. For each multicast service, the mapping between the multicast service name and the addresses of multicast tree nodes is stored in the Name Resolution System (NRS). To avoid core overload and traffic aggregation, we presented a dynamic core management and selection mechanism, which can dynamically select a low-load core for each multicast service. Furthermore, we designed a path state-aware multicast tree node selection mechanism to achieve traffic load balancing by using low-load links more effectively. Experimental results showed that our proposed multicast approach outperformed some other multicast methods in terms of core load, number of join requests, link load, traffic concentration, and routing state.
APA, Harvard, Vancouver, ISO, and other styles
10

Chandramouli, R., and S. Rose. "Challenges in securing the domain name system." IEEE Security & Privacy Magazine 4, no. 1 (January 2006): 84–87. http://dx.doi.org/10.1109/msp.2006.8.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Dissertations / Theses on the topic "Multicast Domain Name System"

1

Biolek, Martin. "Klientská aplikace protokolu DNS s grafickým rozhraním pro účely výuky." Master's thesis, Vysoké učení technické v Brně. Fakulta elektrotechniky a komunikačních technologií, 2021. http://www.nusl.cz/ntk/nusl-442404.

Full text
Abstract:
The goal of the Master thesis on the topic of the Client application of DNS protocol with graphical interface for teaching purposes is to create a program with the features of sending, receiving DNS, MDNS and LLMNR protocols with optional parameters. Additionally, compare the created application with available tools such as Nslookup, Dig and create examples of application for teaching.
APA, Harvard, Vancouver, ISO, and other styles
2

Fontanella, Shaun. "Indexing Geographic Information Using the Domain Name System." The Ohio State University, 2012. http://rave.ohiolink.edu/etdc/view?acc_num=osu1345531139.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Schomp, Kyle Graham. "Complexity and Security of the Domain Name System." Case Western Reserve University School of Graduate Studies / OhioLINK, 2016. http://rave.ohiolink.edu/etdc/view?acc_num=case1453329135.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Montes, Io. "Legal framework for domain names /." [S.l.] : [s.n.], 2005. http://aleph.unisg.ch/hsgscan/hm00153322.pdf.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Karstensen, Lasse. "Skjult IP-kommunikasjon basert på Domain Name System (DNS)." Thesis, Norges teknisk-naturvitenskapelige universitet, Institutt for telematikk, 2010. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-11320.

Full text
Abstract:
I denne rapporten undersøkes det om det er mulig å detektere IP-over-DNS -trafikk gjennom en navnetjener automatisk. Bakgrunn for oppgavevalget var et utsagn av Nussbaum m.fl. som sa at eneste mulighet en systemadministrator hadde for å begrense IP-over-DNS generelt var båndbreddebegrensninger av klienter. Dette er undersøkt i laboratoriet, og alle kjente måter for å gjøre IP-over-DNS er prøvd ut eksperimentelt.Rapporten gir to hovedbidrag: 1) det argumenteres for at det er mulig å detektere IP-over-DNS -trafikk automatisk og uten særlig mange falske alarmer, samt 2) gruppering av båndbreddeforbruk per mottakerdomene ser ut til å være den beste teknikken for å gjøre dette. Arbeidet er gjort eksperimentelt og iterativt, og kildekode som implementerer samtlige utprøvde teknikker er vedlagt.
APA, Harvard, Vancouver, ISO, and other styles
6

Ahmed, Sarah 1975. "A scalable Byzantine fault tolerant secure domain name system." Thesis, Massachusetts Institute of Technology, 2001. http://hdl.handle.net/1721.1/8936.

Full text
Abstract:
Thesis (M.Eng.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 2001.
Includes bibliographical references (p. 98-101).
The domain name system is the standard mechanism on the Internet to advertise and access important information about hosts. At its inception, DNS was not designed to be a secure protocol. The biggest security hole in DNS is the lack of support for data integrity authentication, source authentication, and authorization. To make DNS more robust, a security extension of the domain name system (DNSSEC) was proposed by the Internet Engineering task force (IETF) in late 1997. The basic idea of the DNS security extension is to provide data integrity and origin authentication by means of cryptographic digital signatures. However, the proposed extension suffers from some security flaws. In this thesis, we discuss the security problems of DNS and its security extension. As a solution, we present the design and implementation of a Byzantine-fault-tolerant domain name system. The system consists of 3f+1 tightly coupled name servers and guarantees safety and liveness properties assuming no more than f replicas are faulty within a small window of vulnerability. To authenticate communication between a client and a server to provide per-query data authentication, we propose to use symmetric key cryptography. To address scalability concerns, we propose a hierarchical organization of name servers with a hybrid of iterative and recursive query resolution approaches. The issue of cache inconsistency is addressed by designing a hierarchical cache with an invalidation protocol using leases. Because of the use of hierarchical state partitioning and caching to achieve scalability in DNS, we develop an efficient protocol that allows replicas in a group to request operations from another group using very few messages. We show that the scalable Byzantine-fault tolerant domain name system, while providing a much higher degree of security and reliability, performs as well or even better than an implementation of the DNS security extension.
by Sarah Ahmed.
M.Eng.
APA, Harvard, Vancouver, ISO, and other styles
7

Eckhard, Rolf Andreas. "Das Domain-Name-System : eine kritische Bestandsaufnahme aus kartellrechtlicher Sicht /." Frankfurt am Main [u.a.] : Lang, 2001. http://www.gbv.de/dms/spk/sbb/recht/toc/332838439.pdf.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Snyder, Mark E. "Critical infrastructure protection and the Domain Name Service (DNS) system." Diss., Rolla, Mo. : Missouri University of Science and Technology, 2008. http://scholarsmine.mst.edu/thesis/pdf/Snyder_09007dcc805e0f32.pdf.

Full text
Abstract:
Thesis (M.S.)--Missouri University of Science and Technology, 2008.
Vita. The entire thesis text is included in file. Title from title screen of thesis/dissertation PDF file (viewed January 15, 2009) Includes bibliographical references.
APA, Harvard, Vancouver, ISO, and other styles
9

Sit, Emil 1977. "A study of caching in the Internet Domain Name System." Thesis, Massachusetts Institute of Technology, 2000. http://hdl.handle.net/1721.1/86513.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Filippi, Geoffrey George. "A High-Availability Architecture for the Dynamic Domain Name System." Thesis, Virginia Tech, 2008. http://hdl.handle.net/10919/32869.

Full text
Abstract:
A High-Availability Architecture for the Dynamic Domain Name System

DNS, DDNS, BGP, anycast, DHCP, replication, LDAP, multi-master, high-availability, reliability

The Domain Name System (DNS) provides a mapping between host names and Internet Protocol (IP) addresses. Hosts that are configured using the Dynamic Host Configuration Protocol (DHCP) can have their assigned IP addresses updated in a Dynamic DNS (DDNS). DNS and DDNS are critical components of the Internet. Most applications use host names rather than IP addresses, allowing the underlying operating system (OS) to translate these host names to IP addresses on behalf of the application. When the DDNS service is unavailable, applications that use DNS cannot contact the hosts served by that DDNS server. Unfortunately, the current DDNS implementation cannot continue to operate under failure of a master DNS server. Although a slave DNS server can continue to translate names to addresses, new IP addresses or changes to existing IP addresses cannot be added. Therefore, those new hosts cannot be reached by the DDNS.

A new architecture is presented that eliminates this single point of failure. In this design, instead of storing resource records in a flat text file, all name servers connect to a Lightweight Directory Access Protocol (LDAP) directory to store and retrieve resource records. These directory servers replicate all resource records across each other using a multi-master replication mechanism. The DHCP servers can add records to any of the functioning DNS servers in event of an outage. In this scheme, all DNS servers use the anycast Border Gateway Protocol (BGP). This allows any of the DNS servers to answer queries sent to a single IP address. The DNS clients always use the same IP address to send queries. The routing system removes routes to non-functional name servers and delivers the request to the closest (according to network metrics) available DNS server.

This thesis also describes a concrete implementation of this system that was created to demonstrate the viability of this solution. A reference implementation was built in a laboratory to represent an Internet Service Provider (ISP) with three identical regions. This implementation was built using Quagga as the BGP routing software running on a set of core routers and on each of the DNS servers. The Berkeley Internet Name Daemon (BIND) was used as an implementation of the DNS. The BIND Simplified Database Backend (SDB) interface was used to allow the DNS server to store and retrieve resource records in an LDAP directory. The Fedora Directory Server was used as a multi-master LDAP directory. DHCP service was provided by the Internet Systems Consortium's (ISC) DHCP server. The objectives for the design were high-availability, scalability and consistency. These properties were analyzed using the metrics of downtime during failover, replication overhead, and latency of replication. The downtime during failover was less than one second. The precision of this metric was limited by the synchronization provided by the Network Time Protocol (NTP) implementation used in the laboratory. The network traffic overhead for a three-way replication was shown to be only 3.5 times non-replicated network traffic. The latency of replication was also shown to be less than one second. The results show the viability of this approach and indicate that this solution should be usable over a wide area network, serving a large number of clients.
Master of Science

APA, Harvard, Vancouver, ISO, and other styles

Books on the topic "Multicast Domain Name System"

1

Herrmann, Dominik. Beobachtungsmöglichkeiten im Domain Name System. Wiesbaden: Springer Fachmedien Wiesbaden, 2016. http://dx.doi.org/10.1007/978-3-658-13263-7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Cheung, YiuChung. Multi-lingual domain name system. Oxford: Oxford Brookes University, 2001.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Liu, Cricket. Understanding the Domain Name System (DNS). Sebastopol, CA: O'Reilly & Associates, Inc., 1998.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

The domain name registration system: Liberalisation, consumer protection, and growth. Abingdon, Oxon [UK]: Routledge, 2012.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Das Domain-Name-System: Eine kritische Bestandsaufnahme aus kartellrechtlicher Sicht. Frankfurt am Main: Peter Lang, 2001.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Ng, Jenny. The domain name registration system: Liberalisation, consumer protection, and growth. Abingdon, Oxon [UK]: Routledge, 2012.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

Research, United States Congress House Committee on Science Subcommittee on Basic. The domain name system, parts I-II: Joint hearings before the Committee on Science, Subcommittee on Basic Research and Subcommittee on Technology, U.S. House of Representatives, One Hundred Fifth Congress, second session, March 31 and October 7, 1998. Washington: U.S. G.P.O., 1999.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Domain name system privatization, is ICANN out of control?: Hearing before the Subcommittee on Oversight and Investigations of the Committee on Commerce, House of Representatives, One Hundred Sixth Congress, first session, July 22, 1999. Washington: U.S. G.P.O., 1999.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Liska, Allan. DNS Security: Hacking and Defending the Domain Name System. Elsevier Science & Technology Books, 2016.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Ng, Jenny. Domain Name Registration System: Liberalisation, Consumer Protection and Growth. Taylor & Francis Group, 2014.

Find full text
APA, Harvard, Vancouver, ISO, and other styles

Book chapters on the topic "Multicast Domain Name System"

1

Weik, Martin H. "Domain Name System." In Computer Science and Communications Dictionary, 453. Boston, MA: Springer US, 2000. http://dx.doi.org/10.1007/1-4020-0613-6_5504.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Goerzen, John. "Domain Name System." In Foundations of Python Network Programming, 65–85. Berkeley, CA: Apress, 2004. http://dx.doi.org/10.1007/978-1-4302-0752-8_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Fox, Richard, and Wei Hao. "Domain Name System." In Internet Infrastructure, 161–218. Boca Raton : Taylor & Francis, a CRC title, part of the Taylor & Francis imprint, a member of the Taylor & Francis Group, the academic division of T&F Informa, plc, [2017]: CRC Press, 2017. http://dx.doi.org/10.1201/9781315175577-5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Bök, Patrick-Benjamin, Andreas Noack, Marcel Müller, and Daniel Behnke. "Domain Name System (DNS)." In Computernetze und Internet of Things, 203–9. Wiesbaden: Springer Fachmedien Wiesbaden, 2020. http://dx.doi.org/10.1007/978-3-658-29409-0_10.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Jayakar, Krishna. "Internet Domain Name System." In Handbook of Computer Networks, 305–19. Hoboken, NJ, USA: John Wiley & Sons, Inc., 2011. http://dx.doi.org/10.1002/9781118256114.ch22.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Simpkins, Stacy. "Domain Name System (DNS)." In Building a SharePoint 2016 Home Lab, 117–31. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-2170-9_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Goswami, Subrata. "The Domain Name System." In Internet Protocols, 119–37. Boston, MA: Springer US, 2003. http://dx.doi.org/10.1007/978-1-4615-0385-9_6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Ruff, Andreas. "Das Domain-Name-System." In DomainLaw, 7–17. Berlin, Heidelberg: Springer Berlin Heidelberg, 2002. http://dx.doi.org/10.1007/978-3-642-56116-0_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Badach, Anatol, and Erwin Hoffmann. "Domain Name System (DNS)." In Technik der IP-Netze, 231–302. München: Carl Hanser Verlag GmbH & Co. KG, 2019. http://dx.doi.org/10.3139/9783446455115.005.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Badach, Anatol, and Erwin Hoffmann. "Domain Name System (DNS)." In Technik der IP-Netze, 175–238. München: Carl Hanser Verlag GmbH & Co. KG, 2015. http://dx.doi.org/10.3139/9783446439863.004.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Multicast Domain Name System"

1

Deccio, Casey, Chao-Chih Chen, Prasant Mohapatra, Jeff Sedayao, and Krishna Kant. "Quality of name resolution in the Domain Name System." In 2009 17th IEEE International Conference on Network Protocols (ICNP). IEEE, 2009. http://dx.doi.org/10.1109/icnp.2009.5339693.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Mockapetris, Paul, and Kevin Dunlap. "Implementation of the Domain Name System." In the 2nd workshop. New York, New York, USA: ACM Press, 1986. http://dx.doi.org/10.1145/503956.503991.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Mockapetris, P., and K. J. Dunlap. "Development of the domain name system." In Symposium proceedings. New York, New York, USA: ACM Press, 1988. http://dx.doi.org/10.1145/52324.52338.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Zou, Futai, Siyu Zhang, Bei Pei, Li Pan, Linsen Li, and Jianhua Li. "Survey on Domain Name System Security." In 2016 IEEE First International Conference on Data Science in Cyberspace (DSC). IEEE, 2016. http://dx.doi.org/10.1109/dsc.2016.96.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Fan, Xun, John Heidemann, and Ramesh Govindan. "Evaluating anycast in the domain name system." In IEEE INFOCOM 2013 - IEEE Conference on Computer Communications. IEEE, 2013. http://dx.doi.org/10.1109/infcom.2013.6566965.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Deccio, Casey, Jeff Sedayao, Krishna Kant, and Prasant Mohapatra. "Measuring Availability in the Domain Name System." In IEEE INFOCOM 2010 - IEEE Conference on Computer Communications. IEEE, 2010. http://dx.doi.org/10.1109/infcom.2010.5462270.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Rose, Scott, Ramaswamy Chandramouli, and Anastase Nakassis. "Information Leakage through the Domain Name System." In Technology Conference for Homeland Security (CATCH). IEEE, 2009. http://dx.doi.org/10.1109/catch.2009.10.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Jung, Younchan, and Matnel Peradilla. "Domain Name to IP Address Resolution System with Multiple Name Servers Adaptable to MANETs." In 2012 IEEE 11th International Conference on Trust, Security and Privacy in Computing and Communications (TrustCom). IEEE, 2012. http://dx.doi.org/10.1109/trustcom.2012.132.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Wei Zhou and Liu Chen. "A secure domain name system based on intrusion tolerance." In 2008 International Conference on Machine Learning and Cybernetics (ICMLC). IEEE, 2008. http://dx.doi.org/10.1109/icmlc.2008.4621016.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Khan, Sarmad Ullah, Rafiullah Khan, and Arif Ali. "Implementation of Content Centric Networks through Domain Name System." In 2015 International Conference on Emerging Technologies (ICET). IEEE, 2015. http://dx.doi.org/10.1109/icet.2015.7389212.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Multicast Domain Name System"

1

Josefsson, S. Domain Name System Media Types. RFC Editor, April 2005. http://dx.doi.org/10.17487/rfc4027.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Eastlake, D., and M. Andrews. Domain Name System (DNS) Cookies. RFC Editor, May 2016. http://dx.doi.org/10.17487/rfc7873.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Eastlake, D., and C. Kaufman. Domain Name System Security Extensions. RFC Editor, January 1997. http://dx.doi.org/10.17487/rfc2065.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Eastlake, D. Domain Name System Security Extensions. RFC Editor, March 1999. http://dx.doi.org/10.17487/rfc2535.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Eastlake, D. Domain Name System (DNS) IANA Considerations. RFC Editor, March 2011. http://dx.doi.org/10.17487/rfc6195.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Josefsson, S. Domain Name System Uniform Resource Identifiers. RFC Editor, May 2006. http://dx.doi.org/10.17487/rfc4501.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Eastlake, D., E. Brunner-Williams, and B. Manning. Domain Name System (DNS) IANA Considerations. RFC Editor, September 2000. http://dx.doi.org/10.17487/rfc2929.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Eastlake, D. Detached Domain Name System (DNS) Information. RFC Editor, March 1999. http://dx.doi.org/10.17487/rfc2540.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Eastlake, D. Secure Domain Name System Dynamic Update. RFC Editor, April 1997. http://dx.doi.org/10.17487/rfc2137.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Postel, J. Domain Name System Structure and Delegation. RFC Editor, March 1994. http://dx.doi.org/10.17487/rfc1591.

Full text
APA, Harvard, Vancouver, ISO, and other styles
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography