DOCSLIB.ORG

Domain Name System - Wikipedia, the Free Encyclopedia

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Domain Name System - Wikipedia, the free encyclopedia Create account Log in Article Talk Read Edit View history Domain Name System From Wikipedia, the free encyclopedia Main page The ( ) is a hierarchical Domain Name System DNS Internet protocol suite Contents distributed naming system for computers, services, or Application layer Featured content any resource connected to the Internet or a private DHCP · DHCPv6 · DNS · FTP · HTTP · Current events network. It associates various information with domain IMAP · IRC · LDAP · MGCP · NNTP · BGP · Random article names assigned to each of the participating entities. NTP · POP · RPC · RTP · RTSP · RIP · SIP · Donate to Wikipedia Most prominently, it translates easily memorised domain SMTP · SNMP · SOCKS · SSH · Telnet · TLS/SSL · XMPP · (more) · Interaction names to the numerical IP addresses needed for the Transport layer Help purpose of locating computer services and devices TCP · UDP · DCCP · SCTP · RSVP · (more) · About Wikipedia worldwide. By providing a worldwide, distributed Internet layer Community portal keyword-based redirection service, the Domain Name IP(IPv4 · IPv6 · ·ICMP · ICMPv6 · ECN · System is an essential component of the functionality of Recent changes IGMP · IPsec · (more) · the Internet. Contact Wikipedia Link layer An often-used analogy to explain the Domain Name ARP/InARP · NDP · OSPF · Toolbox System is that it serves as the phone book for the Tunnels(L2TP · ·PPP · Print/export Internet by translating human-friendly computer Media access control(Ethernet · DSL · ISDN · FDDI · ·(more) · hostnames into IP addresses. For example, the domain Languages V T E name www.example.com translates to the addresses · · · Afrikaans 192.0.43.10 (IPv4) and 2001:500:88:200::10 (IPv6). Unlike a phone book, the DNS can be quickly updated, allowing a service's location on the network العربية Asturianu to change without affecting the end users, who continue to use the same host name. Users take Azərbaycanca advantage of this when they use meaningful Uniform Resource Locators (URLs) and e-mail addresses without having to know how the computer actually locates the services. Беларуская The Domain Name System distributes the responsibility of assigning domain names and mapping Беларуская (тарашкевіца) those names to IP addresses by designating authoritative name servers for each domain. Български Authoritative name servers are assigned to be responsible for their particular domains, and in turn Boarisch can assign other authoritative name servers for their sub-domains. This mechanism has made the Bosanski DNS distributed and fault tolerant and has helped avoid the need for a single central register to be Català continually consulted and updated. Additionally, the responsibility for maintaining and updating the Česky master record for the domains is spread among many domain name registrars, who compete for the Dansk end-user's (the domain-owner's) business. Domains can be moved from registrar to registrar at any Deutsch time. Eesti The Domain Name System also specifies the technical functionality of this database service. It Ελληνικά defines the DNS protocol, a detailed specification of the data structures and data communication Español exchanges used in DNS, as part of the Internet Protocol Suite. Esperanto The Internet maintains two principal namespaces, the domain name hierarchy[1] and the Internet Euskara Protocol (IP) address spaces.[2] The Domain Name System maintains the domain name hierarchy فارسی and provides translation services between it and the address spaces. Internet name servers and a Français [3] Galego communication protocol implement the Domain Name System. A DNS name server is a server that 한국어 stores the DNS records for a domain name, such as address (A or AAAA) records, name server (NS) records, and mail exchanger (MX) records (see also list of DNS record types); a DNS name http://en.wikipedia.org/wiki/Domain_Name_System[4/04/2013 5:07:12 PM] Domain Name System - Wikipedia, the free encyclopedia Հայերեն server responds with answers to queries against its database. Hrvatski Contents [hide] Bahasa Indonesia 1 History Italiano 2 Structure עברית 2.1 Domain name space Қазақша 2.2 Domain name syntax Latgaļu 2.3 Internationalized domain names Latviešu 2.4 Name servers Lietuvių 2.4.1 Authoritative name server Limburgs 3 Operation Magyar 3.1 Address resolution mechanism Македонски 3.1.1 Recursive and caching name server 3.2 DNS resolvers Bahasa Melayu 3.3 Circular dependencies and glue records Nederlands 3.4 Record caching 日本語 3.5 Reverse lookup Norsk bokmål 3.6 Client lookup Norsk nynorsk 3.6.1 Broken resolvers Олык марий 3.7 Other applications Polski 4 Protocol details Português 5 DNS resource records Română 5.1 Wildcard DNS records Русский 6 Protocol extensions Саха тыла 7 Dynamic zone updates Shqip 8 Security issues Simple English 9 Domain name registration Slovenčina 10 Internet standards Slovenščina 10.1 Security See also 11 کوردی Српски / srpski 12 References Srpskohrvatski / 13 External links српскохрватски Suomi [edit] Svenska History Tagalog The practice of using a name as a simpler, more memorable abstraction of a host's numerical address on a network dates back to the ARPANET era. Before the DNS was invented in 1982, each computer on the network retrieved a file called HOSTS.TXT from a computer at SRI (now SRI ไทย International).[4][5] The HOSTS.TXT file mapped names to numerical addresses. A hosts file still Türkçe exists on most modern operating systems by default and generally contains a mapping of "localhost" Українська to the IP address 127.0.0.1. Many operating systems use name resolution logic that allows the .administrator to configure selection priorities for available name resolution methods اردو Tiếng Việt The rapid growth of the network made a centrally maintained, hand-crafted HOSTS.TXT file ייִדיש unsustainable; it became necessary to implement a more scalable system capable of automatically Yorùbá disseminating the requisite information. 中文 Edit links At the request of Jon Postel, Paul Mockapetris invented the Domain Name System in 1983 and wrote the first implementation. The original specifications were published by the Internet Engineering Task Force in RFC 882 and RFC 883 , which were superseded in November 1987 by RFC 1034 [1] and RFC 1035 .[3] Several additional Request for Comments have proposed various extensions to the core DNS protocols. http://en.wikipedia.org/wiki/Domain_Name_System[4/04/2013 5:07:12 PM] Domain Name System - Wikipedia, the free encyclopedia In 1984, four Berkeley students—Douglas Terry, Mark Painter, David Riggle, and Songnian Zhou— wrote the first Unix name server implementation, called The Berkeley Internet Name Domain (BIND) Server.[6] In 1985, Kevin Dunlap of DEC significantly re-wrote the DNS implementation. Mike Karels, Phil Almquist, and Paul Vixie have maintained BIND since then. BIND was ported to the Windows NT platform in the early 1990s. BIND was widely distributed, especially on Unix systems, and is the dominant DNS software in use on the Internet.[7] Alternative name servers have been developed, partly motivated by a desire to improve upon BIND's record of vulnerability to attack. BIND version 9 is also written from scratch and has a security record comparable to other modern DNS software.[citation needed] Structure [edit] Domain name space [edit] The domain name space consists of a tree of domain names. Each node or leaf in the tree has zero or more resource records, which hold information associated with the domain name. The tree sub- divides into zones beginning at the root zone. A DNS zone may consist of only one domain, or may consist of many domains and sub-domains, depending on the administrative authority delegated to the manager. Administrative responsibility over any zone may be divided by creating additional zones. Authority is said to be delegated for a portion of the old space, usually in the form of sub- domains, to another name server and administrative entity. The old zone ceases to be authoritative for the new zone. Domain name [edit] syntax The definitive descriptions of the rules for forming domain names appear in RFC The hierarchical Domain Name System, organized into zones, each served 1035 , RFC 1123 , and by a name server RFC 2181 . A domain name consists of one or more parts, technically called labels, that are conventionally concatenated, and delimited by dots, such as example.com. The right-most label conveys the top-level domain; for example, the domain name www.example.com belongs to the top-level domain com. The hierarchy of domains descends from right to left; each label to the left specifies a subdivision, or subdomain of the domain to the right. For example: the label example specifies a subdomain of the com domain, and www is a sub domain of example.com. This tree of subdivisions may have up to 127 levels. Each label may contain up to 63 characters. The full domain name may not exceed the length of 253 characters in its textual representation.[1] In the internal binary representation of the DNS the http://en.wikipedia.org/wiki/Domain_Name_System[4/04/2013 5:07:12 PM] Domain Name System - Wikipedia, the free encyclopedia maximum length requires 255 octets of storage, since it also stores the length of the name.[3] In practice, some domain registries may have shorter limits.[citation needed] DNS names may technically consist of any character representable in an octet. However, the allowed formulation of domain names in the DNS root zone, and most other sub domains, uses a preferred format and character set. The characters allowed in a label are a subset of the ASCII character set, and includes the characters a through z, A through Z, digits 0 through 9, and the hyphen. This rule is known as the LDH rule (letters, digits, hyphen). Domain names are interpreted in case-independent manner.[8] Labels may not start or end with a hyphen.[9] There is an additional rule that essentially requires that top-level domain names not be all-numeric.[10] A hostname is a domain name that has at least one IP address associated.
Recommended publications
  • On IP Networking Over Tactical Links

    On IP Networking Over Tactical Links

    On IP Networking over Tactical Links Claude Bilodeau The work described in this document was sponsored by the Department of National Defence under Work Unit 5co. Defence R&D Canada √ Ottawa TECHNICAL REPORT DRDC Ottawa TR 2003-099 Communications Research Centre CRC-RP-2003-008 August 2003 On IP networking over tactical links Claude Bilodeau Communications Research Centre The work described in this document was sponsored by the Department of National Defence under Work Unit 5co. Defence R&D Canada - Ottawa Technical Report DRDC Ottawa TR 2003-099 Communications Research Centre CRC RP-2003-008 August 2003 © Her Majesty the Queen as represented by the Minister of National Defence, 2003 © Sa majesté la reine, représentée par le ministre de la Défense nationale, 2003 Abstract This report presents a cross section or potpourri of the numerous issues that surround the tech- nical development of military IP networking over disadvantaged network links. In the first sec- tion, multi-media services are discussed with regard to three aspects: applications, operational characteristics and service models. The second section focuses on subnetworks and bearers; mainly impairments caused by characteristics of the wireless environment. An overview of the Iris tactical bearers is provided as an example of a tactical IP environment. The last section looks at how IP can integrate these two elements i.e. multi-media services and impaired sub- network links. These three sections are unified by a common theme, quality of service, which runs in the background of the discussions. Résumé Ce rapport présente une coupe transversale ou pot-pourri de questions reliées au développe- ment technique des réseaux militaires IP pour des liaisons défavorisées.
  • Qos: NBAR Protocol Library, Cisco IOS XE Release 3.8S

    Qos: NBAR Protocol Library, Cisco IOS XE Release 3.8S

    QoS: NBAR Protocol Library, Cisco IOS XE Release 3.8S Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 C O N T E N T S 3COM-AMP3 through AYIYA-IPV6-TUNNELED 34 3COM-AMP3 35 3COM-TSMUX 36 3PC 37 9PFS 38 914C G 39 ACAP 40 ACAS 40 ACCESSBUILDER 41 ACCESSNETWORK 42 ACP 43 ACR-NEMA 44 ACTIVE-DIRECTORY 45 ACTIVESYNC 45 ADOBE-CONNECT 46 AED-512 47 AFPOVERTCP 48 AGENTX 49 ALPES 50 AMINET 50 AN 51 ANET 52 ANSANOTIFY 53 ANSATRADER 54 ANY-HOST-INTERNAL 54 AODV 55 AOL-MESSENGER 56 AOL-MESSENGER-AUDIO 57 AOL-MESSENGER-FT 58 QoS: NBAR Protocol Library, Cisco IOS XE Release 3.8S ii Contents AOL-MESSENGER-VIDEO 58 AOL-PROTOCOL 59 APC-POWERCHUTE 60 APERTUS-LDP 61 APPLEJUICE 62 APPLEQTC 63 APPLEQTCSRVR 63 APPLIX 64 ARCISDMS 65 ARGUS 66 ARIEL1 67 ARIEL2 67 ARIEL3 68 ARIS 69 ARNS 70 ARUBA-PAPI 71 ASA 71 ASA-APPL-PROTO 72 ASIPREGISTRY 73 ASIP-WEBADMIN 74 AS-SERVERMAP 75 AT-3 76 AT-5 76 AT-7 77 AT-8 78 AT-ECHO 79 AT-NBP 80 AT-RTMP 80 AT-ZIS 81 AUDIO-OVER-HTTP 82 AUDIT 83 AUDITD 84 AURORA-CMGR 85 AURP 85 AUTH 86 QoS: NBAR Protocol Library, Cisco IOS XE Release 3.8S iii Contents AVIAN 87 AVOCENT 88 AX25 89 AYIYA-IPV6-TUNNELED 89 BABELGUM through BR-SAT-MON 92 BABELGUM 93 BACNET 93 BAIDU-MOVIE 94 BANYAN-RPC 95 BANYAN-VIP 96 BB 97 BBNRCCMON 98 BDP 98 BFTP 99 BGMP 100 BGP 101 BGS-NSI 102 BHEVENT 103 BHFHS 103 BHMDS 104 BINARY-OVER-HTTP 105 BITTORRENT 106 BL-IDM 107 BLIZWOW 107 BLOGGER 108 BMPP 109 BNA 110 BNET 111 BORLAND-DSJ 112 BR-SAT-MON 112
  • Simulacijski Alati I Njihova Ograničenja Pri Analizi I Unapređenju Rada Mreža Istovrsnih Entiteta

    Simulacijski Alati I Njihova Ograničenja Pri Analizi I Unapređenju Rada Mreža Istovrsnih Entiteta

    SVEUČILIŠTE U ZAGREBU FAKULTET ORGANIZACIJE I INFORMATIKE VARAŽDIN Tedo Vrbanec SIMULACIJSKI ALATI I NJIHOVA OGRANIČENJA PRI ANALIZI I UNAPREĐENJU RADA MREŽA ISTOVRSNIH ENTITETA MAGISTARSKI RAD Varaždin, 2010. PODACI O MAGISTARSKOM RADU I. AUTOR Ime i prezime Tedo Vrbanec Datum i mjesto rođenja 7. travanj 1969., Čakovec Naziv fakulteta i datum diplomiranja Fakultet organizacije i informatike, 10. listopad 2001. Sadašnje zaposlenje Učiteljski fakultet Zagreb – Odsjek u Čakovcu II. MAGISTARSKI RAD Simulacijski alati i njihova ograničenja pri analizi i Naslov unapređenju rada mreža istovrsnih entiteta Broj stranica, slika, tablica, priloga, XIV + 181 + XXXVIII stranica, 53 slike, 18 tablica, 3 bibliografskih podataka priloga, 288 bibliografskih podataka Znanstveno područje, smjer i disciplina iz koje Područje: Informacijske znanosti je postignut akademski stupanj Smjer: Informacijski sustavi Mentor Prof. dr. sc. Željko Hutinski Sumentor Prof. dr. sc. Vesna Dušak Fakultet na kojem je rad obranjen Fakultet organizacije i informatike Varaždin Oznaka i redni broj rada III. OCJENA I OBRANA Datum prihvaćanja teme od Znanstveno- 17. lipanj 2008. nastavnog vijeća Datum predaje rada 9. travanj 2010. Datum sjednice ZNV-a na kojoj je prihvaćena 18. svibanj 2010. pozitivna ocjena rada Prof. dr. sc. Neven Vrček, predsjednik Sastav Povjerenstva koje je rad ocijenilo Prof. dr. sc. Željko Hutinski, mentor Prof. dr. sc. Vesna Dušak, sumentor Datum obrane rada 1. lipanj 2010. Prof. dr. sc. Neven Vrček, predsjednik Sastav Povjerenstva pred kojim je rad obranjen Prof. dr. sc. Željko Hutinski, mentor Prof. dr. sc. Vesna Dušak, sumentor Datum promocije SVEUČILIŠTE U ZAGREBU FAKULTET ORGANIZACIJE I INFORMATIKE VARAŽDIN POSLIJEDIPLOMSKI ZNANSTVENI STUDIJ INFORMACIJSKIH ZNANOSTI SMJER STUDIJA: INFORMACIJSKI SUSTAVI Tedo Vrbanec Broj indeksa: P-802/2001 SIMULACIJSKI ALATI I NJIHOVA OGRANIČENJA PRI ANALIZI I UNAPREĐENJU RADA MREŽA ISTOVRSNIH ENTITETA MAGISTARSKI RAD Mentor: Prof.
  • RADIUS and Freeradius

    RADIUS and Freeradius

    RADIUS and FreeRADIUS Frank Kuse Presented at AfNOG 2018 Dakar Ingredients Theory What is RADIUS Why use RADIUS How RADIUS works User databases Attributes Practical Installing FreeRADIUS Configuration of Radius with LDAP Database backend Testing Radius Authentication with LDAP user account What is RADIUS? Remote Authentication Dial In User Service Authentication “Who are you?” Authorization “What services am I allowed to give you?” Accounting “What did you do with my services while you were using them?,,Accounting information may be used to track the user's usage for charging purposes Why RADIUS? What are the alternatives? LDAP, Kerberos, Active Directory Advantages of RADIUS: Lightweight and efficient Supported by many clients, e.g. 802.1x, switches and routers Disadvantages of RADIUS: Limited attribute set, limited use for desktop authentication How does RADIUS work? Authentication Password authentication, plain text and hashed Lookup in various user databases: passwd, SQL, text Authorization Using a set of rules or other templates Accounting Measuring, communicating and recording resources accessed by user See Wikipedia for list of RFCs RADIUS Architecture (1) RADIUS protocol is between NAS(Network Access Server) or a RAS(Remote Access server) and AAA server NAS controls access to protected resource RADIUS Architecture (2) Scenario 1 In this scenario, a front-end NAS (network access server) or RAS (remote access server) performs authentication of a user with a backend RADIUS server. The NAS/RAS sends user information (credentials) to the RADIUS server carried in RADIUS packets. The RADIUS server implements the access policy (who is granted access with what authorizations) or may retrieve policies from a database through LDAP (Lightweight Directory Access Protocol).
  • Proactive Cyberfraud Detection Through Infrastructure Analysis

    Proactive Cyberfraud Detection Through Infrastructure Analysis

    PROACTIVE CYBERFRAUD DETECTION THROUGH INFRASTRUCTURE ANALYSIS Andrew J. Kalafut Submitted to the faculty of the Graduate School in partial fulfillment of the requirements for the degree Doctor of Philosophy in Computer Science Indiana University July 2010 Accepted by the Graduate Faculty, Indiana University, in partial fulfillment of the requirements of the degree of Doctor of Philosophy. Doctoral Minaxi Gupta, Ph.D. Committee (Principal Advisor) Steven Myers, Ph.D. Randall Bramley, Ph.D. July 19, 2010 Raquel Hill, Ph.D. ii Copyright c 2010 Andrew J. Kalafut ALL RIGHTS RESERVED iii To my family iv Acknowledgements I would first like to thank my advisor, Minaxi Gupta. Minaxi’s feedback on my research and writing have invariably resulted in improvements. Minaxi has always been supportive, encouraged me to do the best I possibly could, and has provided me many valuable opportunities to gain experience in areas of academic life beyond simply doing research. I would also like to thank the rest of my committee members, Raquel Hill, Steve Myers, and Randall Bramley, for their comments and advice on my research and writing, especially during my dissertation proposal. Much of the work in this dissertation could not have been done without the help of Rob Henderson and the rest of the systems staff. Rob has provided valuable data, and assisted in several other ways which have ensured my experiments have run as smoothly as possible. Several members of the departmental staff have been very helpful in many ways. Specifically, I would like to thank Debbie Canada, Sherry Kay, Ann Oxby, and Lucy Battersby.
  • Reference Manual GUI Graphical User Interface EAGLE One Rel. 5.3

    Reference Manual GUI Graphical User Interface EAGLE One Rel. 5.3

    Reference Manual GUI Graphical User Interface Industrial Ethernet Firewall EAGLE One RM GUI EAGLE One Technical Support Release 5.3.0 09/2013 https://hirschmann-support.belden.eu.com The naming of copyrighted trademarks in this manual, even when not specially indicated, should not be taken to mean that these names may be considered as free in the sense of the trademark and tradename protection law and hence that they may be freely used by anyone. © 2013 Hirschmann Automation and Control GmbH Manuals and software are protected by copyright. All rights reserved. The copying, reproduction, translation, conversion into any electronic medium or machine scannable form is not permitted, either in whole or in part. An exception is the preparation of a backup copy of the software for your own use. For devices with embedded software, the end-user license agreement on the enclosed CD/DVD applies. The performance features described here are binding only if they have been expressly agreed when the contract was made. This document was produced by Hirschmann Automation and Control GmbH according to the best of the company's knowledge. Hirschmann reserves the right to change the contents of this document without prior notice. Hirschmann can give no guarantee in respect of the correctness or accuracy of the information in this document. Hirschmann can accept no responsibility for damages, resulting from the use of the network components or the associated operating software. In addition, we refer to the conditions of use specified in the license contract. You can get the latest version of this manual on the Internet at the Hirschmann product site (www.hirschmann.com).
  • SAP Business Connector SAP Adapter Guide

    SAP Business Connector SAP Adapter Guide

    SAP Business Connector SAP Adapter Guide SAP SYSTEM Release 4.7 SAP® AG Neurottstr. 16 D-69190 Walldorf SAP AG SAP Business Connector SAP Adapter Guide Copyright ©Copyright 2003 SAP AG. All rights reserved. No part of this description of functions may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft®, WINDOWS® and EXCEL®, NT® and SQL-Server® are registered trademarks of Microsoft Corporation. IBM®, OS/2®, DB2/6000®, AIX®, OS/400® and AS/400® are registered trademarks of IBM Corporation. OSF/Motif® is a registered trademark of Open Software Foundation. ORACLE® is a registered trademark of ORACLE Corporation, California, USA. webMethods® is a registered trademark of webMethods Incorporated, Virginia, USA. INFORMIX®-OnLine for SAP is a registered trademark of Informix Software Incorporated. UNIX® and X/Open® are registered trademarks of SCO Santa Cruz Operation. SAP®, R/2®, R/3®, RIVA®, ABAP/4®, SAPaccess®, SAPmail®, SAPoffice®, SAP-EDI®, SAP Business Workflow®, SAP EarlyWatch®, SAP ArchiveLink®, R/3 Retail®, ALE/WEB®, SAPTRONIC® are registered trademarks of SAP AG. All rights reserved. SAP Business Connector ii SAP AG SAP Business Connector SAP Adapter Guide Typographical Conventions Type Style Description Interface Text Words or characters that appear on the screen. This includes field names, screen titles, pushbuttons, menu names, and menu options. Document Title Cross-references to other documentation. User Entry Words and characters that you enter exactly as they appear in the documentation.
  • Hrpc Research Group Presentation

    Hrpc Research Group Presentation

    Proposed Human Rights Protocol Considerations Research Group IRTF Chairs: Avri Doria & Niels ten Oever Presentation: Joana Varon & Niels ten Oever March 27 2015 - IETF92 Dallas 1 Agenda ● Agenda ● Jabber scribe, note takers ● Notewell ● Introduction ● Status of proposed research group ● Context of research ● Discussion of draft draft-doria-hrpc-proposal-01 ● Next steps ● Other relevant research, issues or topics 2 ● Discussion ● Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: • The IETF plenary session • The IESG, or any member thereof on behalf of the IESG • Any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices • Any IETF working group or portion thereof • Any Birds of a Feather (BOF) session • The IAB or any member thereof on behalf of the IAB • The RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 5378 and RFC 3979 (updated by RFC 4879). Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 5378 and RFC 3979 for details.
  • Synology NAS User's Guide Based on DSM 4.3

    Synology NAS User's Guide Based on DSM 4.3

    Synology NAS User's Guide Based on DSM 4.3 Document ID Syno_UsersGuide_NAS_20130906 Table of Contents Chapter 1: Introduction Chapter 2: Get Started with Synology DiskStation Manager Install Synology NAS and DSM ............................................................................................................................................. 8 Log into Synology DiskStation Manager .............................................................................................................................. 8 DiskStation Manager Appearance ........................................................................................................................................ 9 Manage DSM with the Main Menu ..................................................................................................................................... 11 Manage Personal Options ................................................................................................................................................... 12 Chapter 3: Modify System Settings Change DSM Settings .......................................................................................................................................................... 14 Change Network Settings .................................................................................................................................................... 16 Modify Regional Options .....................................................................................................................................................
  • NBAR2 Standard Protocol Pack 1.0

    NBAR2 Standard Protocol Pack 1.0

    NBAR2 Standard Protocol Pack 1.0 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 © 2013 Cisco Systems, Inc. All rights reserved. CONTENTS CHAPTER 1 Release Notes for NBAR2 Standard Protocol Pack 1.0 1 CHAPTER 2 BGP 3 BITTORRENT 6 CITRIX 7 DHCP 8 DIRECTCONNECT 9 DNS 10 EDONKEY 11 EGP 12 EIGRP 13 EXCHANGE 14 FASTTRACK 15 FINGER 16 FTP 17 GNUTELLA 18 GOPHER 19 GRE 20 H323 21 HTTP 22 ICMP 23 IMAP 24 IPINIP 25 IPV6-ICMP 26 IRC 27 KAZAA2 28 KERBEROS 29 L2TP 30 NBAR2 Standard Protocol Pack 1.0 iii Contents LDAP 31 MGCP 32 NETBIOS 33 NETSHOW 34 NFS 35 NNTP 36 NOTES 37 NTP 38 OSPF 39 POP3 40 PPTP 41 PRINTER 42 RIP 43 RTCP 44 RTP 45 RTSP 46 SAP 47 SECURE-FTP 48 SECURE-HTTP 49 SECURE-IMAP 50 SECURE-IRC 51 SECURE-LDAP 52 SECURE-NNTP 53 SECURE-POP3 54 SECURE-TELNET 55 SIP 56 SKINNY 57 SKYPE 58 SMTP 59 SNMP 60 SOCKS 61 SQLNET 62 SQLSERVER 63 SSH 64 STREAMWORK 65 NBAR2 Standard Protocol Pack 1.0 iv Contents SUNRPC 66 SYSLOG 67 TELNET 68 TFTP 69 VDOLIVE 70 WINMX 71 NBAR2 Standard Protocol Pack 1.0 v Contents NBAR2 Standard Protocol Pack 1.0 vi CHAPTER 1 Release Notes for NBAR2 Standard Protocol Pack 1.0 NBAR2 Standard Protocol Pack Overview The Network Based Application Recognition (NBAR2) Standard Protocol Pack 1.0 is provided as the base protocol pack with an unlicensed Cisco image on a device.
  • Domain Name System 1 Domain Name System

    Domain Name System 1 Domain Name System

    Domain Name System 1 Domain Name System The Domain Name System (DNS) is a hierarchical distributed naming system for computers, services, or any resource connected to the Internet or a private network. It associates various information with domain names assigned to each of the participating entities. A Domain Name Service translates queries for domain names (which are easier to understand and utilize when accessing the internet) into IP addresses for the purpose of locating computer services and devices worldwide. An often-used analogy to explain the Domain Name System is that it serves as the phone book for the Internet by translating human-friendly computer hostnames into IP addresses. For example, the domain name www.example.com translates to the addresses 192.0.43.10 (IPv4) and 2620:0:2d0:200::10 (IPv6). The Domain Name System makes it possible to assign domain names to groups of Internet resources and users in a meaningful way, independent of each entity's physical location. Because of this, World Wide Web (WWW) hyperlinks and Internet contact information can remain consistent and constant even if the current Internet routing arrangements change or the participant uses a mobile device. Internet domain names are easier to remember than IP addresses such as 208.77.188.166 (IPv4) or 2001:db8:1f70::999:de8:7648:6e8 (IPv6). Users take advantage of this when they recite meaningful Uniform Resource Locators (URLs) and e-mail addresses without having to know how the computer actually locates them. The Domain Name System distributes the responsibility of assigning domain names and mapping those names to IP addresses by designating authoritative name servers for each domain.
  • DNS Performance – a Study of Free, Public and Popular DNS Servers in 2019

    DNS Performance – a Study of Free, Public and Popular DNS Servers in 2019

    Linköping University | Department of Computer and Information Science Bachelor’s thesis, 16 ECTS | Informationsteknologi 2019 | LIU-IDA/LITH-EX-G--19/037--SE DNS Performance – A study of free, public and popular DNS servers in 2019 DNS prestanda – En studie av gratis, publika och populära DNS servrar år 2019 Filip Ström Felix Zedén Yverås Supervisor : Niklas Carlsson Examiner : Marcus Bendtsen Linköpings universitet SE–581 83 Linköping +46 13 28 10 00 , www.liu.se Upphovsrätt Detta dokument hålls tillgängligt på Internet - eller dess framtida ersättare - under 25 år från publicer- ingsdatum under förutsättning att inga extraordinära omständigheter uppstår. Tillgång till dokumentet innebär tillstånd för var och en att läsa, ladda ner, skriva ut enstaka ko- pior för enskilt bruk och att använda det oförändrat för ickekommersiell forskning och för undervis- ning. Överföring av upphovsrätten vid en senare tidpunkt kan inte upphäva detta tillstånd. All annan användning av dokumentet kräver upphovsmannens medgivande. För att garantera äktheten, säker- heten och tillgängligheten finns lösningar av teknisk och administrativ art. Upphovsmannens ideella rätt innefattar rätt att bli nämnd som upphovsman i den omfattning som god sed kräver vid användning av dokumentet på ovan beskrivna sätt samt skydd mot att dok- umentet ändras eller presenteras i sådan form eller i sådant sammanhang som är kränkande för up- phovsmannens litterära eller konstnärliga anseende eller egenart. För ytterligare information om Linköping University Electronic Press se förlagets hemsida http://www.ep.liu.se/. Copyright The publishers will keep this document online on the Internet - or its possible replacement - for a period of 25 years starting from the date of publication barring exceptional circumstances.