DNS Conformance Test Specification For Client
|
|
|
- Rosamond Hodge
- 8 years ago
- Views:
Transcription
1 DNS Conformance Test Specification For Client Revision 1.0 Yokogawa Electric Corporation
2 References This test specification focus on following DNS related RFCs. RFC 1034 DOMAIN NAMES - CONCEPTS AND FACILITIES RFC 1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION RFC 1123 Requirements for Internet Hosts -- Application and Support RFC 1995 Incremental Zone Transfer in DNS RFC 1996 A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY) RFC 2181 Clarifications to the DNS Specification RFC 2308 Negative Caching of DNS Queries (DNS NCACHE) RFC 2671 Extension Mechanisms for DNS (EDNS0) RFC 2782 A DNS RR for specifying the location of services (DNS SRV) RFC 3401 Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS RFC 3402 Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm RFC 3403 Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database RFC 3404 Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI) Resolution Application RFC 3405 Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARPA Assignment Procedures RFC 3425 Obsoleting IQUERY RFC 3596 DNS Extensions to Support IP Version 6 Yokogawa Electric Corporation DNS Conformance Test Specification
3 ---TOC--- References Introduction Common Topology Terminology Description Client Test Label length Domain name length Rule for label A type in standard query CNAME type in standard query HINFO type in standard query MX type in standard query NS type in standard query PTR type in standard query (A) PTR type in standard query (AAAA) SOA type in standard query IN class in standard query CH class in standard query Zero TTL prohibits caching Carried in TCP Standard message format Opcode (standard query) Opcode (status query) Question section format AXFR qtype in standard query * qtype in standard query * qclass in standard query Recursion desired (RD) in standard query Caching wildcards response Returning of answer Yokogawa Electric Corporation DNS Conformance Test Specification
4 5.26. Returning of name error (NXDOMAIN) Returning of data not found error (NODATA) Encounters a CNAME Cache data vs authoritative data Answer in local information Sending query to servers Analyze the response (delegation) Analyze the response (caching delegation) Analyze the response (caching CNAME) Analyze the response (answer is invalid for recursive) Analyze the response (answer is invalid for caching) Analyze the response (delegation is invalid) Order of transmission of octets and bits Label format Label of root MB type in standard query MG type in standard query MR type in standard query NULL type in standard query WKS type in standard query MINFO type in standard query TXT type in standard query MAILB qtype in standard query HS class in standard query Header section format Message compression Not depend on response in order Invalid response (query is returned) Invalid response (RRs are incorrectly formatted) Invalid response (Long TTL) (optional) Invalid response ( does not match) Invalid response (invalid question section) Yokogawa Electric Corporation DNS Conformance Test Specification
5 5.58. Caching several RRs of same type Unused fields in a query Multiplex concurrent requests Time out of cache Caching truncated responses Multicast query Retransmission control Caching of temporary failure Differing TTLs from non-authoritative source Differing TTLs from authoritative source Received with most significant bit is set Caching of name error (NXDOMAIN) TTL expired negative cache MUST NOT be used (NXDOMAIN) Caching of name error (NXDOMAIN) for query tuple Caching of no data (NODATA) TTL expired negative cache MUST NOT be used (NODATA) Caching of no data (NODATA) for query tuple Negative responses without SOA records Resolver cache a server failure response Resolver cache a server failure response for query tuple Limit of time (5 minutes) for caching (Server Failure) Caching of dead server indication Caching of dead server indication for query tuple Limit of time (5 minutes) for caching (Dead/Unreachable Server) Caching of SOA record OPT pseudo-rr The quantity of OPT pseudo-rrs Check OPT RR format Check Sender's UDP payload size Responders don't understand OPT RR SRV type in standard query Returning of answer Yokogawa Electric Corporation DNS Conformance Test Specification
6 5.90. Returning of answer (w/o Additional Data section) Priority comparing Priority comparing (round-robin) Weight comparing NXDOMAIN NAPTR type in standard query Order comparison Preference comparison Flag "" to control rewriting and interpretation Flag "A" to control rewriting and interpretation Flag "S" to control rewriting and interpretation Selection of services Encounter Unknown flag Both REGEXP and REPLACEMENT fields exist E164 to Uniform Resource Identifiers (URI) URN resolution Obsoleting IQUERY AAAA type in standard query Yokogawa Electric Corporation DNS Conformance Test Specification
7 1. Introduction These DNS conformance test specifications have aimed to evaluate the client's behavior described in RFC1034 which defines domain names concepts and facilities. These specifications evaluate DNS message. And the following points are also evaluated: The DNS client can exchange DNS messages over IPv6 transport satisfying the DNS specifications. The DNS client can exchange DNS messages over IPv4 transport satisfying the DNS specifications. Yokogawa Electric Corporation DNS Conformance Test Specification
8 2. Common Topology Net-y Net-z AP Server1(TN) DNS Server1(TN) 3ffe:501:ffff:101::10 3ffe:501:ffff:101:: ffe:501:ffff:101::/ /24 ROUTER1(TN) 3ffe:501:ffff:100:: ffe:501:ffff:100::/ /24 DNS Client1(NUT) 3ffe:501:ffff:100:XXXX Fig. 1 Topology No.1 AP Server1(TN):A.example.com DNS Server1(TN) DNS Server2(TN) 3ffe:501:ffff:101::10 3ffe:501:ffff:101::20 3ffe:501:ffff:101:: Net-y ffe:501:ffff:101::/ /24 ROUTER1(TN) 3ffe:501:ffff:100:: Net-z ffe:501:ffff:100::/ /24 DNS Client1(NUT) 3ffe:501:ffff:100:XXXX Fig. 2 Toplogy No.2 Yokogawa Electric Corporation DNS Conformance Test Specification
9 Net-y Net-z AP Server1(TN) DNS Server1(TN) 3ffe:501:ffff:101::60 3ffe:501:ffff:101:: ffe:501:ffff:101::/ /24 ROUTER1(TN) 3ffe:501:ffff:100:: ffe:501:ffff:100::/ /24 DNS Client1(NUT) 3ffe:501:ffff:100:XXXX Fig. 3 Topology No.3 AP Server1(TN):A.example.com DNS Server1(TN) DNS Server2(TN) DNS Server3(TN) 3ffe:501:ffff:101::10 3ffe:501:ffff:101::20 3ffe:501:ffff:101::30 3ffe:501:ffff:101:: Net-y ffe:501:ffff:101::/ /24 ROUTER1(TN) 3ffe:501:ffff:100:: Net-z ffe:501:ffff:100::/ /24 DNS Client1(NUT) 3ffe:501:ffff:100:XXXX Fig. 4 Topology No.4 Yokogawa Electric Corporation DNS Conformance Test Specification
10 AP Server1(TN):B.example.com AP Server2(TN):C.example.com DNS Server1(TN) 3ffe:501:ffff:101::60 3ffe:501:ffff:101::70 3ffe:501:ffff:101:: Net-y ffe:501:ffff:101::/ /24 ROUTER1(TN) 3ffe:501:ffff:100:: Net-z ffe:501:ffff:100::/ /24 DNS Client1(NUT) 3ffe:501:ffff:100:XXXX Fig. 5 Topology No.5 XXXX: EUI64 address Yokogawa Electric Corporation DNS Conformance Test Specification
11 3. Terminology NUT_NETZ SV2_NETY SV3_NETY AP1_NETY BRO_MULTI DNS Client1(NUT)'s address DNS Server1(TN)'s address DNS Server2(TN)'s address DNS Server3(TN)'s address AP Server1(TN)'s address Broadcast(for IPv4) or multicast(for IPv6) address Yokogawa Electric Corporation DNS Conformance Test Specification
12 4. Description Each test specification consists of following parts. Purpose: Category: The Purpose is the short statement describing what the test attempts to achieve. It is usually phrased as a simple assertion of the future or capability to be tested. The Category shows what classification of device must satisfy the test. Initialization: The Initialization describes how to initialize and configure the NUT before starting each test. If a value is not provided, then the protocol s default value is used. Procedure: Judgment: References: The Procedure describes step-by-step instructions for carrying out the test. The Judgment describes expected result. If we can observe as same result as the description of Judgment, the NUT passes the test. The References section contains some parts of specification Yokogawa Electric Corporation DNS Conformance Test Specification
13 5. Client Test 5.1. Label length Purpose Verify that a NUT transmits messages name space specifications Each node has a label, which is zero to 63 octets in length Labels must be 63 characters or less. Category Client Initialization Network Topology Refer the topology "Fig. 1 Topology No.1". Setup Set the DNS Server1(TN) s address to NUT as above mentioned Network Topology. Pre-Sequence In order to send the query for A type of AP Server1(TN): AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA.example.com to the DNS Server1(TN), NUT is configured. Procedure This test sequence is following. DNS Client1 (NUT) DNS Server1 (TN) > 1. Send standard query =AAA******A.example.com < > < Standard query response > 3. Send standard query =A.example.com < Standard query response > X 5. Send standard query =AAA******A.example.com < > v v 1. NUT send standard query w/ 63 octets label to TN. Judgment (Check *1) 2. TN send standard query response to NUT. 3. NUT send standard query w/ 1 octets label to TN. Judgment (Check *3) 4. TN send standard query response to NUT. 5. NUT send standard query w/ 64 octets label to TN. Judgment (Check *5) Yokogawa Electric Corporation DNS Conformance Test Specification
14 Packet Description 1st Packet DNS Question section 2nd packet. 1. Standard query from DNS Client1 (NUT) to DNS Server1 (TN) Destination Address Src Port NUT_NETZ Dst Port 53 QR 0 AA RD RA Z RCODE NSCOUNT 0 ARCOUNT AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAA.example.com 2. Standard query response from DNS Server1 (TN) to Client1 (NUT) Destination Address Src Port 53 Dst Port QR 1 AA 1 RD RA 0 Z 0 RCODE 0 ANCOUNT 1 NSCOUNT 1 NUT_NETZ Same as 1st Packet's Src Port Same as 1st Packet's Same as 1st Packet's RD Yokogawa Electric Corporation DNS Conformance Test Specification
15 ARCOUNT 1 DNS Question section DNS Answer section DNS Authority section DNS Additional section NAME AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAA.example.com AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAA.example.com (Pointer 0xC00C) TTL 1 day (86400) RDLENGTH 4 ADDRESS NAME example.com (Pointer 0xC04C) NS (0x0002) TTL 1 day (86400) RDLENGTH 6 NSDNAME NAME NS1.example.com (NS1 + Pointer 0xC04C) NS1.example.com (Pointer 0xC079) TTL 1 day (86400) RDLENGTH 4 ADDRESS rd Packet 2. Standard query from DNS Client1 (NUT) to DNS Server1 (TN) NUT_NETZ Destination Address Src Port Dst Port 53 QR 0 AA RD RA Z RCODE NSCOUNT 0 Yokogawa Electric Corporation DNS Conformance Test Specification
16 DNS Question section ARCOUNT A.example.com 4th Packet 2. Standard query response from DNS Server1 (TN) to Client1 (NUT) Destination Address NUT_NETZ Src Port 53 Dst Port Same as 4th Packet's Src Port Same as 4th Packet's QR 1 AA 1 RD Same as 4th Packet's RD RA 0 Z 0 RCODE 0 ANCOUNT 1 NSCOUNT 1 ARCOUNT 1 A.example.com DNS Question section NAME A.example.com (Pointer 0xC00C) DNS Answer section TTL 1 day (86400) RDLENGTH 4 ADDRESS NAME example.com (Pointer 0xC00E) NS (0x0002) DNS Authority section TTL 1 day (86400) RDLENGTH 6 NSDNAME NS1.example.com (NS1 + Pointer 0xC00E) DNS Additional section NAME NS1.example.com (Pointer 0xC03B) TTL 1 day (86400) Yokogawa Electric Corporation DNS Conformance Test Specification
17 RDLENGTH 4 ADDRESS Termination If NUT has cache function, clear the cache. Judgment 1. Received standard query w/ label length 63 from NUT. 3. Received standard query w/ label length 1 from NUT. 5. Not received standard query w/ label length 64 from NUT. References RFC1034 : DOMAIN NAMES - CONCEPTS AND FACILITIES 3.1. Name space specifications and terminology 3.5. Preferred name syntax RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION Preferred name syntax RFC1123 Requirements for internet Hosts -- Application and Support 2.1 Host Names and Numbers Yokogawa Electric Corporation DNS Conformance Test Specification
18 5.2. Domain name length Purpose Verify that a NUT transmits messages name space specifications To simplify implementations, the total number of octets that represent a domain name (i.e., the sum of all label octets and label lengths) is limited to 255. Category Client Initialization Network Topology Refer the topology "Fig. 1 Topology No.1". Setup Set the DNS Server1(TN) s address to NUT as above mentioned Network Topology. Pre-Sequence In order to send the query for A type of AP Server1(TN): AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA. BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB. CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC. DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD. EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE.example.com. to the DNS Server1(TN), NUT is configured. Procedure This test sequence is following. DNS Client1 (NUT) DNS Server1 (TN) > 1. Send standard query =A**.B**.C**.D**.E**.example.com. <----- Name length is > < Standard query response > 3. Send standard query =A.example.com. < Standard query response > X 5. Send standard query =A**.B**.C**.D**.E**.example2.com. <---- Name length is > v v 1. NUT send standard query w/ 254 octets name to TN.Judgment (Check *1) 2. TN send standard query response to NUT. 3. NUT send standard query w/ 14 octets name to TN.Judgment (Check *3) 2. TN send standard query response to NUT. 5. NUT send standard query w/ 255 octets name to TN.Judgment (Check *5) Yokogawa Electric Corporation DNS Conformance Test Specification
19 Packet Description 1st Packet 1. Standard query from DNS Client1 (NUT) to DNS Server1 (TN) DNS Question section Destination Address Src Port NUT_NETZ Dst Port 53 QR 0 AA RD RA Z RCODE NSCOUNT 0 ARCOUNT 2nd packet. AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA. BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB. CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC. DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD. EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE.example.com. 2. Standard query response from DNS Server1 (TN) to Client1 (NUT) Source Address Destination Address Src Port 53 Dst Port QR 1 AA 1 RD RA 0 Z 0 NUT_NETZ Same as 1st Packet's Src Port Same as 1st Packet's Same as 1st Packet's RD Yokogawa Electric Corporation DNS Conformance Test Specification
20 RCODE 0 DNS Question section DNS Answer section DNS Authority section DNS Additional section ANCOUNT 1 NSCOUNT 1 ARCOUNT 1 NAME AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA. BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB. CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC. DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD. EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE.example.com. AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA. BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB. CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC. DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD. EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE.example.com. (Pointer 0xC00C) TTL 1 day (86400) RDLENGTH 4 ADDRESS NAME example.com (Pointer 0xC0FE) NS (0x0002) TTL 1 day (86400) RDLENGTH 6 NSDNAME NAME NS1.example.com (NS1 + Pointer 0xC0FE) NS1.example.com (Pointer 0xC11F) TTL 1 day (86400) RDLENGTH 4 ADDRESS rd Packet 2. Standard query from DNS Client1 (NUT) to DNS Server1 (TN) NUT_NETZ Destination Address Src Port Dst Port 53 QR 0 AA Yokogawa Electric Corporation DNS Conformance Test Specification
21 DNS Question section RD RA Z RCODE NSCOUNT 0 ARCOUNT A.example.com 4th Packet 2. Standard query response from DNS Server1 (TN) to Client1 (NUT) DNS Question section DNS Answer section DNS Authority section Destination Address NUT_NETZ Src Port 53 Dst Port Same as 4th Packet's Src Port Same as 4th Packet's QR 1 AA 1 RD Same as 4th Packet's RD RA 0 Z 0 RCODE 0 ANCOUNT 1 NSCOUNT 1 ARCOUNT 1 A.example.com NAME A.example.com (Pointer 0xC00C) TTL 1 day (86400) RDLENGTH 4 ADDRESS NAME example.com (Pointer 0xC00E) NS (0x0002) Yokogawa Electric Corporation DNS Conformance Test Specification
22 DNS Additional section TTL 1 day (86400) RDLENGTH 6 NSDNAME NS1.example.com (NS1 + Pointer 0xC00E) NAME NS1.example.com (Pointer 0xC03B) TTL 1 day (86400) RDLENGTH 4 ADDRESS Termination If NUT has cache function, clear the cache. Judgment 1. Received standard query w/ domain name length 255 from NUT. 3. Received standard query w/ domain name length 15 from NUT. 5. Not received standard query w/ domain name length 256 from NUT. References RFC1034 DOMAIN NAMES - CONCEPTS AND FACILITIES 3.1. Name space specifications and terminology RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION Size limits 3.1. Name space definitions RFC1123 Requirements for internet Hosts -- Application and Support 2.1. Host Names and Numbers 11. Name syntax Yokogawa Electric Corporation DNS Conformance Test Specification
23 5.3. Rule for label Purpose Verify that a NUT transmits messages as follow as rule for label The syntax of a legal Internet host name was specified in RFC-952. One aspect of host name syntax is hereby changed: the restriction on the first character is relaxed to allow either a letter or a digit. Host software MUST support this more liberal syntax. Category Client Initialization Network Topology Refer the topology "Fig. 1 Topology No.1". Setup Set the DNS Server1(TN) s address to NUT as above mentioned Network Topology. Pre-Sequence In order to send the query for A type of AP Server1(TN): 1A.example.com to the DNS Server1(TN), NUT is configured. Procedure This test sequence is following. DNS Client1 (NUT) DNS Server1 (TN) > 1. Send standard query =1A.example.com v v 1. NUT send standard query =1A.example.com to TN.Judgment (Check *1) Packet Description 1. Standard query from DNS Client1 (NUT) to DNS Server1 (TN) NUT_NETZ Destination Address Src Port Dst Port 53 QR 0 AA Yokogawa Electric Corporation DNS Conformance Test Specification
24 DNS Question section RD RA Z RCODE NSCOUNT 0 ARCOUNT 1A.example.com Termination If NUT has cache function, clear the cache. Judgment 1. Received standard query =1A.example.com from NUT. References RFC1034 DOMAIN NAMES - CONCEPTS AND FACILITIES 3.1. Name space specifications and terminology 3.5. Preferred name syntax RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION Preferred name syntax RFC1123 Requirements for internet Hosts -- Application and Support 2.1 Host Names and Numbers Yokogawa Electric Corporation DNS Conformance Test Specification
25 5.4. A type in standard query Purpose Verify that a NUT transmits correct standard query format for A type Header section format QR Opcode AA TC RD RA Z RCODE QDCOUNT ANCOUNT NSCOUNT ARCOUNT QR Query (0) Opcode A standard query(query) (0) Z Must be zero NSCOUNT 0 ARCOUNT 0 Question section format / / / / A.example.com A type (1) Yokogawa Electric Corporation DNS Conformance Test Specification
26 Answer section format Must be empty Authority section format Must be empty Additional section format Must be empty Category Client Initialization Network Topology Refer the topology "Fig. 1 Topology No.1". AP server1 has a domain name "A.example.com". Setup Set the DNS Server1(TN) s address on NUT as above mentioned Network Topology. Pre-Sequence In order to send the query for A type of AP Server1(TN): A.example.com to the DNS Server1(TN), NUT is configured. Procedure This test sequence is following. DNS Client1 (NUT) DNS Server1 (TN) > 1. Send standard query v v 1. NUT send standard query to TN.Judgment (Check *1) Packet Description 1. Standard query from DNS Client1 (NUT) to DNS Server1 (TN) NUT_NETZ Destination Address Src Port Dst Port 53 QR 0 AA RD RA Yokogawa Electric Corporation DNS Conformance Test Specification
27 DNS Question section Z RCODE NSCOUNT 0 ARCOUNT A.example.com Termination If NUT has cache function, clear the cache. Judgment 1. Standard query for A type must be base on above Verification Points. References RFC1034 DOMAIN NAMES - CONCEPTS AND FACILITIES 3.6. Resource Records RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION values Yokogawa Electric Corporation DNS Conformance Test Specification
28 5.5. CNAME type in standard query Purpose Verify that a NUT transmits correct standard query format for CNAME type Header section format QR Opcode AA TC RD RA Z RCODE QDCOUNT ANCOUNT NSCOUNT ARCOUNT QR Query (0) Opcode A standard query(query) (0) Z Must be zero NSCOUNT 0 ARCOUNT 0 Question section format / / / / A.example.com CNAME type (5) Yokogawa Electric Corporation DNS Conformance Test Specification
29 Answer section format Must be empty Authority section format Must be empty Additional section format Must be empty Category Client Initialization Network Topology Refer the topology "Fig. 1 Topology No.1". AP server1 has a domain name "A.example.com". Setup Set the DNS Server1(TN) s address on NUT as above mentioned Network Topology. Pre-Sequence In order to send the query for CNAME type of AP Server1(TN): A.example.com to the DNS Server1(TN), NUT is configured. Procedure This test sequence is following. DNS Client1 (NUT) DNS Server1 (NUT) > 1. Send standard query v v 1. NUT send standard query to TN. Judgment (Check *1) Packet Description 1. Standard query from DNS Client1 (NUT) to DNS Server1 (TN) NUT_NETZ Destination Address Src Port Dst Port 53 QR 0 AA RD RA Yokogawa Electric Corporation DNS Conformance Test Specification
30 DNS Question section Z RCODE NSCOUNT 0 ARCOUNT A.example.com CNAME (0x0005) Termination If NUT has cache function, clear the cache. Judgment 1. Standard query for CNAME type must be base on above Verification Points. References RFC1034 DOMAIN NAMES - CONCEPTS AND FACILITIES 3.6. Resource Records RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION values Yokogawa Electric Corporation DNS Conformance Test Specification
31 5.6. HINFO type in standard query Purpose Verify that a NUT transmits correct standard query format for HINFO type Header section format QR Opcode AA TC RD RA Z RCODE QDCOUNT ANCOUNT NSCOUNT ARCOUNT QR Query (0) Opcode A standard query(query) (0) Z Must be zero NSCOUNT 0 ARCOUNT 0 Question section format / / / / A.example.com HINFO type (13) Yokogawa Electric Corporation DNS Conformance Test Specification
32 Answer section format Must be empty Authority section format Must be empty Additional section format Must be empty Category Client Initialization Network Topology Refer the topology "Fig. 1 Topology No.1". AP server1 has a domain name "A.example.com". Setup Set the DNS Server1(TN) s address on NUT as above mentioned Network Topology. Pre-Sequence In order to send the query for HINFO type of AP Server1(TN): A.example.com to the DNS Server1(TN), NUT is configured. Procedure This test sequence is following. DNS Client1 (NUT) DNS Server1 (TN) > 1. Send standard query v v 1. NUT send standard query to TN. Judgment (Check *1) Packet Description 1. Standard query from DNS Client1 (NUT) to DNS Server1 (TN) NUT_NETZ Destination Address Src Port Dst Port 53 QR 0 AA RD Yokogawa Electric Corporation DNS Conformance Test Specification
33 DNS Question section RA Z RCODE NSCOUNT 0 ARCOUNT A.example.com HINFO (0x000d) Termination If NUT has cache function, clear the cache. Judgment 1. Standard query for HINFO type must be base on above Verification Points. References RFC1034 DOMAIN NAMES - CONCEPTS AND FACILITIES 3.6. Resource Records RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION values Yokogawa Electric Corporation DNS Conformance Test Specification
34 5.7. MX type in standard query Purpose Verify that a NUT transmits correct standard query format for MX type Header section format Header section format QR Opcode AA TC RD RA Z RCODE QDCOUNT ANCOUNT NSCOUNT ARCOUNT QR Query (0) Opcode A standard query(query) (0) Z Must be zero NSCOUNT 0 ARCOUNT 0 Question section format / / / / example.com MX type (15) Yokogawa Electric Corporation DNS Conformance Test Specification
35 Answer section format Must be empty Authority section format Must be empty Additional section format Must be empty Category Client Initialization Network Topology Refer the topology "Fig. 1 Topology No.1". AP server1 has a domain name "mail.example.com". Setup Set the DNS Server1(TN) s address on NUT as above mentioned Network Topology. Pre-Sequence In order to send the query for MX type of example.com to the DNS Server1(TN), NUT is configured. Procedure This test sequence is following. DNS Client1 (NUT) DNS Server1 (TN) > 1. Send standard query v v 1. NUT send standard query to TN. Judgment (Check *1) Packet Description 1. Standard query from DNS Client1 (NUT) to DNS Server1 (TN) NUT_NETZ Destination Address Src Port Dst Port 53 QR 0 AA RD Yokogawa Electric Corporation DNS Conformance Test Specification
36 DNS Question section RA Z RCODE NSCOUNT 0 ARCOUNT example.com MX (0x000f) Termination If NUT has cache function, clear the cache. Judgment 1. Standard query for MX type must be base on above Verification Points. References RFC1034 DOMAIN NAMES - CONCEPTS AND FACILITIES 3.6. Resource Records RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION values Yokogawa Electric Corporation DNS Conformance Test Specification
37 5.8. NS type in standard query Purpose Verify that a NUT transmits correct standard query format for NS type Header section format Header section format QR Opcode AA TC RD RA Z RCODE QDCOUNT ANCOUNT NSCOUNT ARCOUNT QR Query (0) Opcode A standard query(query) (0) Z Must be zero NSCOUNT 0 ARCOUNT 0 Question section format / / / / example.com NS type (2) Yokogawa Electric Corporation DNS Conformance Test Specification
38 Answer section format Must be empty Authority section format Must be empty Additional section format Must be empty Category Client Initialization Network Topology Refer the topology "Fig. 1 Topology No.1". AP server1 has a domain name "ns example.com". Setup Set the DNS Server1(TN) s address on NUT as above mentioned Network Topology. Pre-Sequence In order to send the query for NS type of example.com to the DNS Server1(TN), NUT is configured. Procedure This test sequence is following. DNS Client1 (NUT) DNS Server1 (TN) > 1. Send standard query v v 1. NUT send standard query to TN. Judgment (Check *1) Packet Description 1. Standard query from DNS Client1 (NUT) to DNS Server1 (TN) NUT_NETZ Destination Address Src Port Dst Port 53 QR 0 AA RD Yokogawa Electric Corporation DNS Conformance Test Specification
39 DNS Question section RA Z RCODE NSCOUNT 0 ARCOUNT example.com NS (0x0002) Termination If NUT has cache function, clear the cache. Judgment 1. Standard query for NS type must be base on above Verification Points. References RFC1034 DOMAIN NAMES - CONCEPTS AND FACILITIES 3.6. Resource Records RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION values Yokogawa Electric Corporation DNS Conformance Test Specification
40 5.9. PTR type in standard query (A) Purpose Verify that a NUT transmits correct standard query format for PTR type Header section format QR Opcode AA TC RD RA Z RCODE QDCOUNT ANCOUNT NSCOUNT ARCOUNT QR Query (0) Opcode A standard query(query) (0) Z Must be zero NSCOUNT 0 ARCOUNT 0 Question section format / / / / in-addr.arpa. PTR type (12) Yokogawa Electric Corporation DNS Conformance Test Specification
41 Answer section format Must be empty Authority section format Must be empty Additional section format Must be empty Category Client Initialization Network Topology Refer the topology "Fig. 1 Topology No.1". AP server1 has a domain name "A.example.com". Setup Set the DNS Server1(TN) s address on NUT as above mentioned Network Topology. Pre-Sequence In order to send the query for PTR type of AP Server1(TN): A.example.com (A) to the DNS Server1(TN), NUT is configured. Procedure This test sequence is following. DNS Client1 (NUT) DNS Server1 (TN) > 1. Send standard query v v 1. NUT send standard query to TN. Judgment (Check *1) Packet Description 1. Standard query from DNS Client1 (NUT) to DNS Server1 (TN) NUT_NETZ Destination Address Src Port Dst Port 53 QR 0 AA RD RA Yokogawa Electric Corporation DNS Conformance Test Specification
42 DNS Question section Z RCODE NSCOUNT 0 ARCOUNT in-addr.arpa. PTR (0x000c) Termination If NUT has cache function, clear the cache. Judgment 1. Standard query for PTR type must be base on above Verification Points. References RFC1034 DOMAIN NAMES - CONCEPTS AND FACILITIES 3.6. Resource Records RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION values 3.5. IN-ADDR.ARPA domain Yokogawa Electric Corporation DNS Conformance Test Specification
43 5.10. PTR type in standard query (AAAA) Purpose Verify that a NUT transmits correct standard query format for PTR type Header section format QR Opcode AA TC RD RA Z RCODE QDCOUNT ANCOUNT NSCOUNT ARCOUNT QR Query (0) Opcode A standard query(query) (0) Z Must be zero NSCOUNT 0 ARCOUNT 0 Question section format / / / / f.f.f.f e.f.f.3.ip6.arpa. PTR type (12) Yokogawa Electric Corporation DNS Conformance Test Specification
44 Answer section format Must be empty Authority section format Must be empty Additional section format Must be empty Category Client Initialization Network Topology Refer the topology "Fig. 1 Topology No.1". AP server1 has a domain name "A.example.com". Setup Set the DNS Server1(TN) s address on NUT as above mentioned Network Topology. Pre-Sequence In order to send the query for PTR type of AP Server1(TN): A.example.com (AAAA) to the DNS Server1(TN), NUT is configured. Procedure This test sequence is following. DNS Client1 (NUT) DNS Server1 (TN) > 1. Send standard query v v 1. NUT send standard query to TN. Judgment (Check *1) Packet Description 1. Standard query from DNS Client1 (NUT) to DNS Server1 (TN) NUT_NETZ Destination Address Src Port Dst Port 53 QR 0 AA RD Yokogawa Electric Corporation DNS Conformance Test Specification
45 DNS Question section RA Z RCODE NSCOUNT 0 ARCOUNT f.f.f.f e.f.f.3.ip6.arpa. PTR (0x000c) Termination If NUT has cache function, clear the cache. Judgment 1. Standard query for PTR type must be base on above Verification Points. References RFC1034 DOMAIN NAMES - CONCEPTS AND FACILITIES 3.6. Resource Records RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION values RFC3596 DNS Extensions to Support IP Version IP6.ARPA Domain Yokogawa Electric Corporation DNS Conformance Test Specification
46 5.11. SOA type in standard query Purpose Verify that a NUT transmits correct standard query format for SOA type Header section format QR Opcode AA TC RD RA Z RCODE QDCOUNT ANCOUNT NSCOUNT ARCOUNT QR Query (0) Opcode A standard query(query) (0) Z Must be zero NSCOUNT 0 ARCOUNT 0 Question section format / / / / example.com SOA type (6) Yokogawa Electric Corporation DNS Conformance Test Specification
47 Answer section format Must be empty Authority section format Must be empty Additional section format Must be empty Category Client Initialization Network Topology Refer the topology "Fig. 1 Topology No.1". AP server1 has a domain name "A.example.com". Setup Set the DNS Server1(TN) s address on NUT as above mentioned Network Topology. Pre-Sequence In order to send the query for SOA type of example.com to the DNS Server1(TN), NUT is configured. Procedure This test sequence is following. DNS Client1 (NUT) DNS Server1 (TN) > 1. Send standard query v v 1. NUT send standard query to TN. Judgment (Check *1) Packet Description 1. Standard query from DNS Client1 (NUT) to DNS Server1 (TN) NUT_NETZ Destination Address Src Port Dst Port 53 QR 0 AA RD Yokogawa Electric Corporation DNS Conformance Test Specification
48 DNS Question section RA Z RCODE NSCOUNT 0 ARCOUNT example.com SOA (0x0006) Termination If NUT has cache function, clear the cache. Judgment 1. Standard query for SOA type must be base on above Verification Points. References RFC1034 DOMAIN NAMES - CONCEPTS AND FACILITIES 3.6. Resource Records RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION values Yokogawa Electric Corporation DNS Conformance Test Specification
49 5.12. IN class in standard query Purpose Verify that a NUT transmits correct standard query format for IN class Header section format QR Opcode AA TC RD RA Z RCODE QDCOUNT ANCOUNT NSCOUNT ARCOUNT QR Query (0) Opcode A standard query(query) (0) Z Must be zero NSCOUNT 0 ARCOUNT 0 Question section format / / / / A.example.com IN class (1) Yokogawa Electric Corporation DNS Conformance Test Specification
50 Answer section format Must be empty Authority section format Must be empty Additional section format Must be empty Category Client Initialization Network Topology Refer the topology "Fig. 1 Topology No.1". AP server1 has a domain name "A.example.com". Setup Set the DNS Server1(TN) s address on NUT as above mentioned Network Topology. Pre-Sequence In order to send the query for IN class of AP Server1(TN): A.example.com to the DNS Server1(TN), NUT is configured. Procedure This test sequence is following. DNS Client1 (NUT) DNS Server1 (TN) > 1. Send standard query v v 1. NUT send standard query to TN. Judgment (Check *1) Packet Description 1. Standard query from DNS Client1 (NUT) to DNS Server1 (TN) NUT_NETZ Destination Address Src Port Dst Port 53 QR 0 AA RD RA Yokogawa Electric Corporation DNS Conformance Test Specification
51 DNS Question section Z RCODE NSCOUNT 0 ARCOUNT A.example.com Termination If NUT has cache function, clear the cache. Judgment 1. Standard query for IN class must be base on above Verification Points. References RFC1034 DOMAIN NAMES - CONCEPTS AND FACILITIES 3.6. Resource Records RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION values Yokogawa Electric Corporation DNS Conformance Test Specification
52 5.13. CH class in standard query Purpose Verify that a NUT transmits correct standard query format for CH class Header section format QR Opcode AA TC RD RA Z RCODE QDCOUNT ANCOUNT NSCOUNT ARCOUNT QR Query (0) Opcode A standard query(query) (0) Z Must be zero NSCOUNT 0 ARCOUNT 0 Question section format / / / / A.example.com CH class (3) Yokogawa Electric Corporation DNS Conformance Test Specification
53 Answer section format Must be empty Authority section format Must be empty Additional section format Must be empty Category Client Initialization Network Topology Refer the topology "Fig. 1 Topology No.1". AP server1 has a domain name "A.example.com". Setup Set the DNS Server1(TN) s address on NUT as above mentioned Network Topology. Pre-Sequence In order to send the query for CH class of AP Server1(TN): A.example.com to the DNS Server1(TN), NUT is configured. Procedure This test sequence is following. DNS Client1 (NUT) DNS Server1 (TN) > 1. Send standard query v v 1. NUT send standard query to TN. Judgment (Check *1) Packet Description 1. Standard query from DNS Client1 (NUT) to DNS Server1 (TN) NUT_NETZ Destination Address Src Port Dst Port 53 QR 0 AA Yokogawa Electric Corporation DNS Conformance Test Specification
54 DNS Question section RD RA Z RCODE NSCOUNT 0 ARCOUNT A.example.com CH (0x0003) Termination If NUT has cache function, clear the cache. Judgment 1. Standard query for CH class must be base on above Verification Points. References RFC1034 DOMAIN NAMES - CONCEPTS AND FACILITIES 3.6. Resource Records RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION values Yokogawa Electric Corporation DNS Conformance Test Specification
55 5.14. Zero TTL prohibits caching Purpose Verify that a NUT prohibits caching with zero TTL While short TTLs can be used to minimize caching, and a zero TTL prohibits caching, the realities of Internet performance suggest that these times should be on the order of days for the typical host. All DNS name servers and resolvers MUST properly handle RRs with a zero TTL: return the RR to the client but do not cache it. Category Client (with Caching function) Initialization Network Topology Refer the topology "Fig. 1 Topology No.1". AP server1 has a domain name "A.example.com". Setup Set the DNS Server1(TN) s address on NUT as above mentioned Network Topology. Pre-Sequence In order to send the query for A type(in class) of AP Server1 (TN): A.example.com to the DNS Server1(TN), NUT is configured. Procedure This test sequence is following. DNS Client1 (NUT) DNS Server1 (TN) > 1. Send standard query =A.example.com < Standard query response TTL= > 3. Send standard query =A.example.com v v 1. NUT send standard query to TN. Judgment (Check *1) 2. TN send standard query response to NUT. 3. NUT send standard query to TN. Judgment (Check *3) Yokogawa Electric Corporation DNS Conformance Test Specification
56 Packet Description 1st Packet 1. Standard query from DNS Client1 (NUT) to DNS Server1 (TN) NUT_NETZ Destination Address Src Port Dst Port 53 QR 0 AA RD RA Z RCODE NSCOUNT 0 ARCOUNT A.example.com DNS Question section 2nd packet. 2. Standard query response from DNS Server1 (TN) to Client1 (NUT) Destination Address NUT_NETZ Src Port 53 Dst Port Same as 1st Packet's Src Port Same as 1st Packet's QR 1 AA 1 RD Same as 1st Packet's RD RA 0 Z 0 RCODE 0 ANCOUNT 1 NSCOUNT 1 ARCOUNT 1 Yokogawa Electric Corporation DNS Conformance Test Specification
57 DNS Question section DNS Answer section DNS Authority section DNS Additional section A.example.com NAME A.example.com (Pointer 0xC00C) TTL 0 RDLENGTH 4 ADDRESS NAME example.com (Pointer 0xC00E) NS (0x0002) TTL 0 RDLENGTH 6 NSDNAME NS1.example.com (NS1 + Pointer 0xC00E) NAME NS1.example.com (Pointer 0xC03B) TTL 0 RDLENGTH 4 ADDRESS rd Packet 3. Standard query from DNS Client1 (NUT) to DNS Server1 (TN) NUT_NETZ Destination Address Src Port Dst Port 53 QR 0 AA RD RA Z RCODE NSCOUNT 0 ARCOUNT DNS Question section A.example.com Yokogawa Electric Corporation DNS Conformance Test Specification
58 Termination If NUT has cache function, clear the cache. Judgment 1. Received standard query =A.example.com from NUT. 3. Received standard query =A.example.com from NUT. References RFC1034 DOMAIN NAMES - CONCEPTS AND FACILITIES 3.6. Resource Records RFC1123 Requirements for Internet Hosts -- Application and Support Resource Records with Zero TTL: RFC-1035 Section Yokogawa Electric Corporation DNS Conformance Test Specification
59 5.15. Carried in TCP Purpose Verify that a NUT transmits messages in TCP In the Internet, queries are carried in UDP datagrams or over TCP connections DNS resolvers and recursive servers MUST support UDP, and SHOULD support TCP, for sending (non-zone-transfer) queries. Specifically, a DNS resolver or server that is sending a non-zone-transfer query MUST send a UDP query first. If the Answer section of the response is truncated and if the requester supports TCP, it SHOULD try the query again using TCP. The Internet supports name server access using TCP [RFC-793] on server port 53 (decimal). Messages sent over TCP connections use server port 53 (decimal).the message is prefixed with a two byte length field which gives the message length, excluding the two byte length field. If the Answer section of the response is truncated and if the requester supports TCP, it SHOULD try the query again using TCP. Category Client Initialization Network Topology Refer the topology "Fig. 1 Topology No.1". AP server1 has a domain name "A.example.com". Setup Set the DNS Server1(TN) s address to NUT as above mentioned Network Topology. Pre-Sequence In order to send the query for A type of AP Server1(TN): A.example.com to the DNS Server1(TN) in TCP, NUT is configured. Procedure This test sequence is following. DNS Client1 (NUT) DNS Server1 (TN) > 1. Send standard query in UDP < Standard query response TC bit is set > 3. Send standard query in TCP v v 1. NUT send standard query to TN in UDP. Judgment (Check *1) 2. TN send standard query response to NUT. 3. NUT send standard query to TN in TCP.*Send query automatically. Judgment (Check *3) Yokogawa Electric Corporation DNS Conformance Test Specification
60 Packet Description 1st Packet 1. Standard query from DNS Client1 (NUT) to DNS Server1 (TN) in UDP NUT_NETZ Destination Address Src Port Dst Port 53 QR 0 AA RD RA Z RCODE NSCOUNT 0 ARCOUNT A.example.com DNS Question section 2nd packet. 2. Standard query response from DNS Server1 (TN) to Client1 (NUT) Destination Address NUT_NETZ Src Port 53 Dst Port Same as 1st Packet's Src Port Same as 1st Packet's QR 1 AA 1 TC 1 RD Same as 1st Packet's RD RA 0 Z 0 RCODE 0 ANCOUNT 30 NSCOUNT 0 ARCOUNT 0 Yokogawa Electric Corporation DNS Conformance Test Specification
61 DNS Question section DNS Answer section DNS Answer section X 28 ADDRESS DNS Answer section A.example.com NAME A.example.com (Pointer 0xC00C) TTL 1 day (86400) RDLENGTH 4 ADDRESS NAME A.example.com (Pointer 0xC00C) TTL 1 day (86400) RDLENGTH 4 ADDRESS **** NAME A.example.com (Pointer 0xC00C) TTL 1 day (86400) RDLENGTH 4 ADDRESS st session 3. Standard query from DNS Client1 (NUT) to DNS Server1 (TN) in TCP NUT_NETZ Destination Address TCP Header Src Port Dst Port 53 QR 0 AA RD RA Z RCODE NSCOUNT 0 ARCOUNT DNS Question section A.example.com Yokogawa Electric Corporation DNS Conformance Test Specification
62 Termination If NUT has cache function, clear the cache. Judgment 1. Received standard query from NUT in UDP. 3. Received standard query from NUT in TCP. References RFC1034 DOMAIN NAMES - CONCEPTS AND FACILITIES 3.7. Queries 4.2. Transport RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION 4.2. Transport TCP usage RFC1123 Requirements for internet Hosts -- Application and Support Transport Protocols Yokogawa Electric Corporation DNS Conformance Test Specification
63 5.16. Standard message format Purpose Verify that a NUT transmits correct standard message format Header section format QR Opcode AA TC RD RA Z RCODE QDCOUNT ANCOUNT NSCOUNT ARCOUNT QR Query (0) Opcode A standard query(query) (0) Z Must be zero NSCOUNT 0 ARCOUNT 0 Question section format / / / / Yokogawa Electric Corporation DNS Conformance Test Specification
64 Answer section format Must be empty Authority section format Must be empty Additional section format Must be empty Category Client Initialization Network Topology Refer the topology "Fig. 1 Topology No.1". AP server1 has a domain name "A.example.com". Setup Set the DNS Server1(TN) s address on NUT as above mentioned Network Topology. Pre-Sequence In order to send the query for A type(in class) of AP Server1(TN): A.example.com to the DNS Server1(TN), NUT is configured. Procedure A.example.com A type (1) IN class (1) This test sequence is following. DNS Client1 (NUT) DNS Server1 (TN) > 1. Send standard query v v 1. NUT send standard query to TN. Judgment (Check *1) Packet Description 1. Standard query from DNS Client1 (NUT) to DNS Server1 (TN) NUT_NETZ Destination Address Src Port Dst Port 53 QR 0 Yokogawa Electric Corporation DNS Conformance Test Specification
65 DNS Question section AA RD RA Z RCODE NSCOUNT 0 ARCOUNT A.example.com Termination If NUT has cache function, clear the cache. Judgment 1. Standard query must be base on above Verification Points. References RFC1034 DOMAIN NAMES - CONCEPTS AND FACILITIES 3.7. Queries RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION 4.1. Format Yokogawa Electric Corporation DNS Conformance Test Specification
66 5.17. Opcode (standard query) Purpose Verify that a NUT transmits correct Opcode in standard query Header section format QR Opcode AA TC RD RA Z RCODE QDCOUNT ANCOUNT NSCOUNT ARCOUNT Category Client Initialization Opcode A standard query (QUERY) (0) Network Topology Refer the topology "Fig. 1 Topology No.1". AP server1 has a domain name "A.example.com". Setup Set the DNS Server1(TN) s address on NUT as above mentioned Network Topology. Pre-Sequence In order to send the standard query for AP Server1(TN): A.example.com to the DNS Server1(TN), NUT is configured. Procedure This test sequence is following. DNS Client1 (NUT) DNS Server1 (TN) > 1. Send standard query v v 1. NUT send standard query to TN. Judgment (Check *1) Yokogawa Electric Corporation DNS Conformance Test Specification
67 Packet Description 1. Standard query from DNS Client1 (NUT) to DNS Server1 (TN) DNS Question section NUT_NETZ Destination Address Src Port Dst Port 53 QR AA TC RD RA Z RCODE QDCOUNT NSCOUNT 0 ARCOUNT Termination If NUT has cache function, clear the cache. Judgment 1. Standard query must be base on above Verification Points. References RFC1034 DOMAIN NAMES - CONCEPTS AND FACILITIES 3.7. Queries RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION Header section format Yokogawa Electric Corporation DNS Conformance Test Specification
68 5.18. Opcode (status query) Purpose Verify that a NUT transmits correct Opcode in status query Header section format QR Opcode AA TC RD RA Z RCODE QDCOUNT ANCOUNT NSCOUNT ARCOUNT Category Client Initialization Opcode a server status request(status) (2) Network Topology Refer the topology "Fig. 1 Topology No.1". AP server1 has a domain name "A.example.com". Setup Set the DNS Server1(TN) s address on NUT as above mentioned Network Topology. Pre-Sequence In order to send the status query to the DNS Server1(TN), NUT is configured. Procedure This test sequence is following. DNS Client1 (NUT) DNS Server1 (TN) > 1. Send status query v v 1. NUT send status query to TN. Judgment (Check *1) Yokogawa Electric Corporation DNS Conformance Test Specification
Table of Contents DNS. How to package DNS messages. Wire? DNS on the wire. Some advanced topics. Encoding of domain names.
Table of Contents DNS Some advanced topics Karst Koymans Informatics Institute University of Amsterdam (version 154, 2015/09/14 10:44:10) Friday, September 11, 2015 DNS on the wire Encoding of domain names
DNS. Some advanced topics. Karst Koymans. (with Niels Sijm) Informatics Institute University of Amsterdam. (version 2.6, 2013/09/19 10:55:30)
DNS Some advanced topics Karst Koymans (with Niels Sijm) Informatics Institute University of Amsterdam (version 2.6, 2013/09/19 10:55:30) Friday, September 13, 2013 Karst Koymans (with Niels Sijm) (UvA)
1 DNS Packet Structure
Fundamentals of Computer Networking Project 1 Primer: DNS Overview CS4700/CS5700 Fall 2009 17 September 2009 The DNS protocol is well-documented online, however, we describe the salient pieces here for
Some advanced topics. Karst Koymans. Friday, September 11, 2015
DNS Some advanced topics Karst Koymans Informatics Institute University of Amsterdam (version 154, 2015/09/14 10:44:10) Friday, September 11, 2015 Karst Koymans (UvA) DNS Friday, September 11, 2015 1 /
Teldat Router. DNS Client
Teldat Router DNS Client Doc. DM723-I Rev. 10.00 March, 2003 INDEX Chapter 1 Domain Name System...1 1. Introduction...2 2. Resolution of domains...3 2.1. Domain names resolver functionality...4 2.2. Functionality
DNS at NLnet Labs. Matthijs Mekking
DNS at NLnet Labs Matthijs Mekking Topics NLnet Labs DNS DNSSEC Recent events NLnet Internet Provider until 1997 The first internet backbone in Holland Funding research and software projects that aid the
Internetworking with TCP/IP Unit 10. Domain Name System
Unit 10 Domain Name System Structure 10.1 Introduction 10.2 Fully Qualified Domain Names (FQDNs) Generic Domains Country Domains 10.3 Mapping domain names to IP addresses 10.4 Mapping IP Addresses to Domain
Motivation. Domain Name System (DNS) Flat Namespace. Hierarchical Namespace
Motivation Domain Name System (DNS) IP addresses hard to remember Meaningful names easier to use Assign names to IP addresses Name resolution map names to IP addresses when needed Namespace set of all
Domain Name System 2015-04-28 17:49:44 UTC. 2015 Citrix Systems, Inc. All rights reserved. Terms of Use Trademarks Privacy Statement
Domain Name System 2015-04-28 17:49:44 UTC 2015 Citrix Systems, Inc. All rights reserved. Terms of Use Trademarks Privacy Statement Contents Domain Name System... 4 Domain Name System... 5 How DNS Works
Coordinación. The background image of the cover is desgned by http://www.freepik.com/ GUIDE TO DNS SECURITY 2
Autor Antonio López Padilla Coordinación Daniel Fírvida Pereira This publication belongs to INTECO (Instituto Nacional de Tecnologías de la Comunicación) and is under an Attribution- NonCommercial 3.0
Forouzan: Chapter 17. Domain Name System (DNS)
Forouzan: Chapter 17 Domain Name System (DNS) Domain Name System (DNS) Need System to map name to an IP address and vice versa We have used a host file in our Linux laboratory. Not feasible for the entire
Subverting BIND s SRTT algorithm Derandomizing NS selection
Subverting BIND s SRTT algorithm Derandomizing NS selection Roee Hay roeeh@il.ibm.com Jonathan Kalechstein kalechstain@gmail.com Gabi Nakibly, Ph.D. gnakibly@cs.technion.ac.il April 14, 2013 Abstract.
DNS : Domain Name System
1/30 DNS : Domain Name System Surasak Sanguanpong nguan@.ac.th http://www...ac.th/~nguan Last updated: May 24, 1999 Outline 2/30 DNS basic name space name resolution process protocol configurations Why
19 Domain Name System (DNS)
CHAPTER 9 Domain Name System (DNS) I n this chapter, we discuss the second application program, Domain Name System (DNS). DNS is a client/server application program used to help other application programs.
THE DOMAIN NAME SYSTEM DNS
Announcements THE DOMAIN NAME SYSTEM DNS Internet Protocols CSC / ECE 573 Fall, 2005 N. C. State University copyright 2005 Douglas S. Reeves 2 Today s Lecture I. Names vs. Addresses II. III. IV. The Namespace
Introduction BIND. The DNS Protocol. History (1) DNS. History (2) Agenda
History (1) DNS Domain Name System The Internet's Name Service even in the early days of the Internet, hosts have been also identified by s e.g. /etc/hosts.txt file on UNIX systems all s have been maintained
netkit lab dns Università degli Studi Roma Tre Dipartimento di Informatica e Automazione Computer Networks Research Group Version Author(s)
Università degli Studi Roma Tre Dipartimento di Informatica e Automazione Computer Networks Research Group netkit lab dns Version Author(s) E-mail Web Description 2.2 G. Di Battista, M. Patrignani, M.
Domain Name System (DNS) Fundamentals
Domain Name System (DNS) Fundamentals Mike Jager Network Startup Resource Center mike.jager@synack.co.nz These materials are licensed under the Creative Commons Attribution-NonCommercial 4.0 International
Domain Name System (DNS)
Chapter 18 CSC465 Computer Networks Spring 2004 Dr. J. Harrison These slides are based on the text TCP/IP Protocol Suite (2 nd Edition) Domain Name System (DNS) CONTENTS NAME SPACE DOMAIN NAME SPACE DISTRIBUTION
How to Add Domains and DNS Records
How to Add Domains and DNS Records Configure the Barracuda NextGen X-Series Firewall to be the authoritative DNS server for your domains or subdomains to take advantage of Split DNS or dead link detection.
Motivation. Users can t remember IP addresses. Implemented by library functions & servers. - Need to map symbolic names (www.stanford.
Motivation 2 cs.princeton.edu User 1 user @ cs.princeton.edu Name server Mail program 192.12.69.5 3 TCP 192.12.69.5 4 192.12.69.5 5 IP Users can t remember IP addresses - Need to map symbolic names (www.stanford.edu)
Domain Name System (DNS) Session-1: Fundamentals. Ayitey Bulley abulley@ghana.com
Domain Name System (DNS) Session-1: Fundamentals Ayitey Bulley abulley@ghana.com Computers use IP addresses. Why do we need names? Names are easier for people to remember Computers may be moved between
The Domain Name System
DNS " This is the means by which we can convert names like news.bbc.co.uk into IP addresses like 212.59.226.30 " Purely for the benefit of human users: we can remember numbers (e.g., telephone numbers),
Networking Domain Name System
System i Networking Domain Name System Version 5 Release 4 System i Networking Domain Name System Version 5 Release 4 Note Before using this information and the product it supports, read the information
Use Domain Name System and IP Version 6
Use Domain Name System and IP Version 6 What You Will Learn The introduction of IP Version 6 (IPv6) into an enterprise environment requires some changes both in the provisioned Domain Name System (DNS)
DNS ActiveX Control for Microsoft Windows. Copyright Magneto Software All rights reserved
DNS ActiveX Control for Microsoft Windows Copyright Magneto Software All rights reserved 1 DNS Overview... 3 1.1 Introduction... 3 1.2 Usage... 3 1.3 Property... 4 1.4 Event... 4 1.5 Method... 4 1.6 Error
Applications and Services. DNS (Domain Name System)
Applications and Services DNS (Domain Name Service) File Transfer Protocol (FTP) Simple Mail Transfer Protocol (SMTP) Malathi Veeraraghavan Distributed database used to: DNS (Domain Name System) map between
Measurement of the Usage of Several Secure Internet Protocols from Internet Traces
Measurement of the Usage of Several Secure Internet Protocols from Internet Traces Yunfeng Fei, John Jones, Kyriakos Lakkas, Yuhong Zheng Abstract: In recent years many common applications have been modified
Domain Name System. CS 571 Fall 2006. 2006, Kenneth L. Calvert University of Kentucky, USA All rights reserved
Domain Name System CS 571 Fall 2006 2006, Kenneth L. Calvert University of Kentucky, USA All rights reserved DNS Specifications Domain Names Concepts and Facilities RFC 1034, November 1987 Introduction
DNS/DNSSEC loose ends
DNS/DNSSEC loose ends Karst Koymans & Niels Sijm Informatics Institute University of Amsterdam Friday, September 21, 2012 Karst Koymans & Niels Sijm (UvA) DNS/DNSSEC loose ends Friday, September 21, 2012
Local DNS Attack Lab. 1 Lab Overview. 2 Lab Environment. SEED Labs Local DNS Attack Lab 1
SEED Labs Local DNS Attack Lab 1 Local DNS Attack Lab Copyright c 2006 Wenliang Du, Syracuse University. The development of this document was partially funded by the National Science Foundation s Course,
Lecture 2 CS 3311. An example of a middleware service: DNS Domain Name System
Lecture 2 CS 3311 An example of a middleware service: DNS Domain Name System The problem Networked computers have names and IP addresses. Applications use names; IP uses for routing purposes IP addresses.
Networking Domain Name System
System i Networking Domain Name System Version 6 Release 1 System i Networking Domain Name System Version 6 Release 1 Note Before using this information and the product it supports, read the information
Internet Engineering Task Force. Intended status: Experimental Expires: September 6, 2012 March 5, 2012
Internet Engineering Task Force Internet-Draft Intended status: Experimental Expires: September 6, 2012 K. Lynn Consultant D. Sturek Grid2Home March 5, 2012 Extended Multicast DNS draft-lynn-homenet-site-mdns-00
The Use of DNS Resource Records
International Journal of Advances in Electrical and Electronics Engineering 230 Available online at www.ijaeee.com & www.sestindia.org/volume-ijaeee/ ISSN: 2319-1112 Simar Preet Singh Systems Engineer,
More Internet Support Protocols
Domain Name System (DNS) Ch 2.5 More Internet Support Protocols Problem statement: Average brain can easily remember 7 digits On average, IP addresses have 10.28 digits We need an easier way to remember
How do I get to www.randomsite.com?
Networking Primer* *caveat: this is just a brief and incomplete introduction to networking to help students without a networking background learn Network Security. How do I get to www.randomsite.com? Local
DNS zone transfers from FreeIPA to non-freeipa slave servers
FreeIPA Training Series DNS zone transfers from FreeIPA to non-freeipa slave servers FreeIPA 3.0 and bind-dyndb-ldap 2.3 Petr Špaček 01-03-2013 Text file based
No. Time Source Destination Protocol Info 1 0.000000 192.168.1.28 192.168.1.2 DNS Standard query A weather.noaa.gov
/tmp/dump/dump02_arp_dns-weather_syn_fin complete-session - Ethereal Page 1 1 0.000000 192.168.1.28 192.168.1.2 DNS Standard query A weather.noaa.gov Frame 1 (76 bytes on wire, 76 bytes captured) Arrival
Introduction to DNS CHAPTER 5. In This Chapter
297 CHAPTER 5 Introduction to DNS Domain Name System (DNS) enables you to use hierarchical, friendly names to easily locate computers and other resources on an IP network. The following sections describe
Networking Domain Name System
IBM i Networking Domain Name System Version 7.2 IBM i Networking Domain Name System Version 7.2 Note Before using this information and the product it supports, read the information in Notices on page
An Introduction to DNS The Domain Name System
An Introduction to DNS The Domain Name System Jim Reid jim.reid@uninett.no INTRODUCTION The DNS in action What does it do? How is it used? Components, roles & responsibilities Weaknesses/vulnerabilities
Domain Name System. DNS is an example of a large scale client-server application. Copyright 2014 Jim Martin
Domain Name System: DNS Objective: map names to IP addresses (i.e., high level names to low level names) Original namespace was flat, didn t scale.. Hierarchical naming permits decentralization by delegating
Copyright 2012 http://itfreetraining.com
In order to find resources on the network, computers need a system to look up the location of resources. This video looks at the DNS records that contain information about resources and services on the
Configuring DNS. Finding Feature Information
The Domain Name System (DNS) is a distributed database in which you can map hostnames to IP addresses through the DNS protocol from a DNS server. Each unique IP address can have an associated hostname.
DNS Resolving using nslookup
DNS Resolving using nslookup Oliver Hohlfeld & Andre Schröder January 8, 2007 Abstract This report belongs to a talk given at the networking course (Institue Eurecom, France) in January 2007. It is based
DNS (Domain Name System) Tutorial @ IETF-70 (DNS for protocol designers)
DNS (Domain Name System) Tutorial @ IETF-70 (DNS for protocol designers) Ólafur Guðmundsson OGUD consulting Peter Koch DENIC eg 1 Tutorial Overview Goal: Give the audience basic understanding of DNS to
KB259302 - Windows 2000 DNS Event Messages 1 Through 1614
Page 1 of 6 Knowledge Base Windows 2000 DNS Event Messages 1 Through 1614 PSS ID Number: 259302 Article Last Modified on 10/29/2003 The information in this article applies to: Microsoft Windows 2000 Server
Internet-Praktikum I Lab 3: DNS
Kommunikationsnetze Internet-Praktikum I Lab 3: DNS Mark Schmidt, Andreas Stockmayer Sommersemester 2015 kn.inf.uni-tuebingen.de Motivation for the DNS Problem IP addresses hard to remember for humans
TCP/IP Fundamentals. OSI Seven Layer Model & Seminar Outline
OSI Seven Layer Model & Seminar Outline TCP/IP Fundamentals This seminar will present TCP/IP communications starting from Layer 2 up to Layer 4 (TCP/IP applications cover Layers 5-7) IP Addresses Data
what s in a name? taking a deeper look at the domain name system mike boylan penn state mac admins conference
what s in a name? taking a deeper look at the domain name system mike boylan penn state mac admins conference whoami work for robert morris university, pittsburgh, pa primarily mac and voip admin @mboylan
Application Protocols in the TCP/IP Reference Model
Application Protocols in the TCP/IP Reference Model File Transfer E-Mail Network Management WWW Virtual Terminal Name Service File Transfer HTTP FTP Telnet SMTP DNS SNMP TFTP Internet protocols TCP UDP
Application Protocols in the TCP/IP Reference Model. Application Protocols in the TCP/IP Reference Model. DNS - Concept. DNS - Domain Name System
Application Protocols in the TCP/IP Reference Model Application Protocols in the TCP/IP Reference Model File Transfer E-Mail Network Management Protocols of the application layer are common communication
API of DNS hosting. For DNS-master and Secondary services Table of contents
API of DNS hosting. For DNS-master and Secondary services Table of contents API of DNS hosting. For DNS-master and Secondary services... 1 1. Introduction... 3 2. Setting access area of application for
Goal of this session
DNS refresher Overview Goal of this session What is DNS? How is DNS built and how does it work? How does a query work? Record types Caching and Authoritative Delegation: domains vs zones Finding the error:
The Domain Name System
Internet Engineering 241-461 Robert Elz kre@munnari.oz.au kre@coe.psu.ac.th http://fivedots.coe.psu.ac.th/~kre DNS The Domain Name System Kurose & Ross: Computer Networking Chapter 2 (2.5) James F. Kurose
Response Differences between NSD and other DNS Servers
Response Differences between NSD and other DNS Servers Jelte Jansen, NLnet Labs Wouter Wijngaards, NLnet Labs NLnet Labs document 2006-004 September 5, 2006 Abstract This note describes observed differences
Christoph L. Schuba. COAST Laboratory. Purdue University. West Lafayette, IN 47907-1398. schuba@cs.purdue.edu
Addressing Weaknesses in the Domain Name System Protocol Christoph L. Schuba COAST Laboratory Department of Computer Sciences Purdue University West Lafayette, IN 47907-1398 schuba@cs.purdue.edu ii ABSTRACT
How to Configure DNS Zones
How to Configure DNS Zones The Barracuda NG Firewall DNS configuration object contains two predefined zones: _template and. To be able to edit and specify DNS zones within the Barracuda NG Firewall DNS
DNS. Computer networks - Administration 1DV202. fredag 30 mars 12
DNS Computer networks - Administration 1DV202 DNS History Who needs DNS? The DNS namespace How DNS works The DNS database The BIND software Server and client configuration The history of DNS RFC 882 and
# $ # % $ % $ % & ' $( # ) *$ www.microsoft.com mail.virgilio.it ftp.cs.cornell.edu
! www.microsoft.com mail.virgilio.it ftp.cs.cornell.edu " " # $ # % $ % $ % & ' $( # ) *$ #+, $-., www.microsoft.com 131.114.9.252 mail.virgilio.it 192.113.21.27 ftp.cs.cornell.edu 115.116.123.11 / / request(nome)
Hostnames. HOSTS.TXT was a bottleneck. Once there was HOSTS.TXT. CSCE515 Computer Network Programming. Hierarchical Organization of DNS
Hostnames CSCE 515: Computer Network Programming ------ Address Conversion Function and DNS RFC 1034, RFC 1035 Wenyuan Xu http://www.cse..edu/~wyxu/ce515f07.html Department of Computer Science and Engineering
IPv6 Trace Analysis using Wireshark Nalini Elkins, CEO Inside Products, Inc. Nalini.elkins@insidethestack.com
1 IPv6 Trace Analysis using Wireshark Nalini Elkins, CEO Inside Products, Inc. Nalini.elkins@insidethestack.com Agenda What has not changed between IPv4 and IPv6 traces What has changed between IPv4 and
Request for Comments: 1788 Category: Experimental April 1995
Network Working Group W. Simpson Request for Comments: 1788 Daydreamer Category: Experimental April 1995 Status of this Memo ICMP Domain Name Messages This document defines an Experimental Protocol for
The Domain Name System
The Domain Name System Antonio Carzaniga Faculty of Informatics University of Lugano October 9, 2012 2005 2007 Antonio Carzaniga 1 IP addresses and host names Outline DNS architecture DNS process DNS requests/replies
Reverse DNS considerations for IPv6
Reverse DNS considerations for IPv6 Kostas Zorbadelos OTE David Freedman - ClaraNet Reverse DNS in IPv4 Every Internet-reachable host should have a name Make sure your PTR and A records match. For every
Understanding DNS (the Domain Name System)
Understanding DNS (the Domain Name System) A white paper by Incognito Software January, 2007 2007 Incognito Software Inc. All rights reserved. Understanding DNS (the Domain Name System) Introduction...2
3. The Domain Name Service
3. The Domain Name Service n Overview and high level design n Typical operation and the role of caching n Contents of DNS Resource Records n Basic message formats n Configuring/updating Resource Records
Detecting attacks involving DNS servers
Detecting attacks involving DNS servers A Netflow data based approach Stephan Roolvink Supervisors: Dr. ir. A. Pras Dr. R. Sadre A. Sperotto M.Sc. ii Detecting attacks involving DNS servers A Netflow data
Enterprise Architecture Office Resource Document Design Note - Domain Name System (DNS)
Date: 8/27/2012 Enterprise Architecture Office Resource Document Design Note - Domain Name System (DNS) Table of Contents 1 Overview...2 1.1 Other Resources...2 1.1.1 State of Minnesota Standards and Guidelines...2
The Domain Name System (DNS)
The Domain Name System (DNS) Columbus, OH 43210 Jain@CIS.Ohio-State.Edu http://www.cis.ohio-state.edu/~jain/ 24-1 Overview Naming hierarchy hierarchy Name resolution Other information in name servers 24-2
Ólafur Guðmundsson. Peter Koch. Shinkuro, Inc. DENIC eg. DNS Tutorial @ IETF-80 ogud@ogud.com & pk@denic.de 2011-03-27
Ólafur Guðmundsson Shinkuro, Inc. Peter Koch DENIC eg 1 Goal: Give the audience basic understanding of DNS to be able to facilitate new uses of DNS and take advantage of DNSSEC in the protocols they specify
Tanenbaum, Computer Networks (extraits) Adaptation par J.Bétréma. DNS The Domain Name System
Tanenbaum, Computer Networks (extraits) Adaptation par J.Bétréma DNS The Domain Name System RFC 1034 Network Working Group P. Mockapetris Request for Comments: 1034 ISI Obsoletes: RFCs 882, 883, 973 November
Advanced DNS Course. Module 4. DNS Load Balancing
Advanced DNS Course Module 4 DNS Load Balancing Services (SRV) Record The Services RR allows a service to be associated with a host name. A user or application that wishes to discover where a service
DNS Pharming Attack Lab
CNT 5410 - Fall 2014 1 DNS Pharming Attack Lab (This is a modified version of the exercise listed below. Modifications are to provide tighter configuration so as to minimize the risk of traffic leaving
DEPLOYMENT GUIDE Version 1.4. Configuring IP Address Sharing in a Large Scale Network: DNS64/NAT64
DEPLOYMENT GUIDE Version 1.4 Configuring IP Address Sharing in a Large Scale Network: DNS64/NAT64 Table of Contents Table of Contents Configuring IP address sharing in a large scale network... 1 Product
IPv6 and DNS. Secure64
IPv6 and DNS Secure64 About me Stephan Lagerholm Director and Founder of TXv6TF. Secure64 Software Corp. Sponsor of the event. Agenda: DNS and IPv6 basics DNS64 (RFC 6147) 464XLAT (RFC 6877) Heuristic
How-to: DNS Enumeration
25-04-2010 Author: Mohd Izhar Ali Email: johncrackernet@yahoo.com Website: http://johncrackernet.blogspot.com Table of Contents How-to: DNS Enumeration 1: Introduction... 3 2: DNS Enumeration... 4 3: How-to-DNS
Practical DNS Operations
Practical DNS Operations John Kristoff jtk@cymru.com 1 DNS operational observations Flexibility as a virtue and scourge Expert pool is deep, but concentrated Best and common practices often undocumented
Managing DNS Server Properties
CHAPTER 17 Managing DNS Server Properties This chapter explains how to set the DNS server parameters. Before you proceed with the tasks in this chapter, read Chapter 15, Managing Zones, which explains
Module 2. Configuring and Troubleshooting DNS. Contents:
Configuring and Troubleshooting DNS 2-1 Module 2 Configuring and Troubleshooting DNS Contents: Lesson 1: Installing the DNS Server Role 2-3 Lesson 2: Configuring the DNS Server Role 2-9 Lesson 3: Configuring
DNS. Computer Networks. Seminar 12
DNS Computer Networks Seminar 12 DNS Introduction (Domain Name System) Naming system used in Internet Translate domain names to IP addresses and back Communication works on UDP (port 53), large requests/responses
DNS Domain Name System
Domain Name System DNS Domain Name System The domain name system is usually used to translate a host name into an IP address Domain names comprise a hierarchy so that names are unique, yet easy to remember.
Clear and Present Danger Increase in Number of DNS AAAA Queries
Clear and Present Danger Increase in Number of DNS AAAA Queries NTT Information Sharing Platform Labs Tsuyoshi Toyono, Keisuke Ishibashi, and Katsuyasu Toyama {toyono, isibasi, toyama}@nttv6.net 1 Outline
The Domain Name System from a security point of view
The Domain Name System from a security point of view Simon Boman Patrik Hellström Email: {simbo105, pathe321}@student.liu.se Supervisor: David Byers, {davby@ida.liu.se} Project Report for Information Security
Operational Problems in IPv6: Fallback and DNS issues
Operational Problems in : Fallback and DNS issues Tomohiro Fujisaki, Arifumi Matsumoto, Katsuyasu Toyama,Tsuyoshi Toyono and Shirou Niinobe Nippon Telegraph and Telephone Corporation Network problems associated
Chapter 25 Domain Name System. 25.1 Copyright The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
Chapter 25 Domain Name System 25.1 Copyright The McGraw-Hill Companies, Inc. Permission required for reproduction or display. 25.2 Figure 25.1 Example of using the DNS service 25-1 NAME SPACE To be unambiguous,
Application-layer Protocols
Application-layer Protocols Based on Notes by D. Hollinger Based on UNIX Network Programming, Stevens, Chapter 9 Also Java Network Programming and Distributed Computing, Chapter 3,8 Also Online Java Tutorial,
The Root of the Matter: Hints or Slaves
The Root of the Matter: Hints or Slaves David Malone October 21, 2003 Abstract We consider the possibility of having a name server act as a slave to the root zone, rather than caching
State of the "DNS privacy" project. Stéphane Bortzmeyer AFNIC bortzmeyer@nic.fr
State of the "DNS privacy" project Stéphane Bortzmeyer AFNIC bortzmeyer@nic.fr 1 / 1 State of the "DNS privacy" project Stéphane Bortzmeyer AFNIC bortzmeyer@nic.fr Warsaw OARC workshop May 2014: talk of
KAREL UCAP DNS AND DHCP CONCEPTS MANUAL MADE BY: KAREL ELEKTRONIK SANAYI ve TICARET A.S. Organize Sanayi Gazneliler Caddesi 10
KAREL UCAP DNS AND DHCP CONCEPTS MANUAL MADE BY: KAREL ELEKTRONIK SANAYI ve TICARET A.S. Organize Sanayi Gazneliler Caddesi 10 Sincan 06935 Ankara, Turkey Version Table Manual Version/Date AAA/22.03.2011
CSE 127: Computer Security. Network Security. Kirill Levchenko
CSE 127: Computer Security Network Security Kirill Levchenko December 4, 2014 Network Security Original TCP/IP design: Trusted network and hosts Hosts and networks administered by mutually trusted parties
Multicast DNS in Wireless Ad-hoc Networks of. Low-resource Devices
Technische Universiteit Eindhoven Department of Mathematics and Computer Science Multicast DNS in Wireless Ad-hoc Networks of Low-resource Devices By Yu Lu Supervisors Prof. Dr. J.J. Lukkien Dr. ir. P.H.F.M.Richard
Bulk DNS Update CSV File
Bulk DNS Updates Bulk DNS Update CSV File Each line in the comma-separated value (CSV) file represents a resource record. A line break must follow each line, and the file may contain up to 5000 lines.
My Services Online Service Support. User Guide for DNS and NTP services
My Services Online Service Support User Guide for DNS and NTP services Table of Contents 1 MY SERVICES... 3 2 ACCESSING MY SERVICES VIA THE INTERNET... 3 2.1 Logging into My Services... 3 2.2 My Services
TECHNICAL REPORT Network Technologies (NTECH); Description of the DNS protocol usage in IP based operators networks
TR 184 012 V1.1.1 (2015-05) TECHNICAL REPORT Network Technologies (NTECH); Description of the DNS protocol usage in IP based operators networks 2 TR 184 012 V1.1.1 (2015-05) Reference DTR/NTECH-00003-NNAR-DNS
Remote DNS Cache Poisoning Attack Lab
SEED Labs Remote DNS Cache Poisoning Attack Lab 1 Remote DNS Cache Poisoning Attack Lab Copyright c 2014 Wenliang Du, Syracuse University. The development of this document is/was funded by the following
DNS Session 4: Delegation and reverse DNS. Joe Abley AfNOG 2006 workshop
DNS Session 4: Delegation and reverse DNS Joe Abley AfNOG 2006 workshop How do you delegate a subdomain? In principle straightforward: just insert NS records for the subdomain, pointing at someone else's
The Design of the Domain Name System June 2012
The Design of the Domain Name System June 2012 Introduction Abstract The Domain Name Systems is a globally distributed realtime database. We look at aspects of its design, and how that affects what kinds
- Domain Name System -
1 Name Resolution - Domain Name System - Name resolution systems provide the translation between alphanumeric names and numerical addresses, alleviating the need for users and administrators to memorize