IPv6 DNS issues draft-ietf-dnsop-ipv6-dns-issues-00.txt

Slides:



Advertisements
Similar presentations
DNS46 for the IPv4/IPv6 Stateless Translator
Advertisements

DNS Proxy Bypass by Recursive DNS Discovery and LOCAL.ARPA draft-ietf-dns-recursive-discovery Ray Bellis IETF76 DNSOP WG Hiroshima, 11 th November 2009.
NAT64-CPE Mode Operation for Opening Residential Service Gang Chen Hui Deng
Host Centric Multi6 Christian Huitema Architect Windows Networking & Communications Microsoft Corporation.
1 IPv6 and IPv4 Interoperation and Transition Tony Hain co-chair IETF ngtrans WG
IPv6 Glue Why registrars need to support it Elise Gerich VP, IANA.
IPv6-The Next Generation Protocol RAMYA MEKALA UIN:
Sergei Komarov. DNS  Mechanism for IP hostname resolution  Globally distributed database  Hierarchical structure  Comprised of three components.
IPv4 & IPv6 Coexistence & Migration Joe Zhao SW2 Great China R&D Center ZyXEL Communications, Inc.
IP Version 6 Next generation IP Prof. P Venkataram ECE Dept. IISc.
IPv6: The Future of the Internet? July 27th, 1999 Auug.
TDC375 Autumn 03/04 John Kristoff - DePaul University 1 Network Protocols Internet Protocol version 6 (IPv6)
DirectAccess is an Enterprise Solution: No support for Windows 7 Professional Requires two consecutive public IP addresses Cannot NAT to the DirectAccess.
TDC 375 Winter 2002John Kristoff1 Network Protocols IPv6.
IPv4/IPv6 Translation: Framework Li, Bao, and Baker.
IAB/IESG Recommendations on IPv6 Address Allocation Bob Hinden at RIPE Sept Brian Carpenter at ARIN Oct Alain Durand at APNIC Oct
1 Issue Definition*: 6RD and IPv6 allocation policy Jan Žorž (Go6 Institute Slo) Mark Townsley (Cisco) *Or, Why we had to wake up on Friday to be here?
1 IPv6 Address Management Rajiv Kumar. 2 Lecture Overview Introduction to IP Address Management Rationale for IPv6 IPv6 Addressing IPv6 Policies & Procedures.
Lecturer : Ms.Trần Thị Ngọc Hoa Chapter 2 Methods Configuring Name Resolution Methods.
Domain Name System | DNSSEC. 2  Internet Protocol address uniquely identifies laptops or phones or other devices  The Domain Name System matches IP.
Module 10 Advanced Topics. DNS and DHCP DHCP can be configured to auto- update (using DDNS) the forward and reverse map zones Can be secured using allow-update.
LIS Discovery using IP address and Reverse DNS draft-thomson-geopriv-res-gw-lis-discovery-03 Ray Bellis, Advanced Projects, Nominet UK IETF 77, GeoPriv.
IAB/IESG Recommendations on IPv6 Address Allocation Bob Hinden at RIPE Sept Brian Carpenter at ARIN Oct Alain Durand at APNIC Oct
資 管 Lee Lesson 11 Coexistence and Migration. 資 管 Lee Lesson Objectives Coexistence and migration overview Coexistence mechanisms ◦ Dual Stack ◦ Tunneling.
Information-Centric Networks03a-1 Week 3 / Paper 1 What DNS is not –Paul Vixie –CACM, December 2009, vol. 52, no. 12 Main point –“DNS is many things to.
IP Version 6 COMT 222. © 2005 Hans Kruse & Shawn Ostermann, Ohio University 2 Why change IP Number of addresses Routing Table Size Client configuration.
Chapter 16 – DNS. DNS Domain Name Service This service allows client machines to resolve computer names (domain names) to IP addresses DNS works at the.
DHCP: Dual-Stack Issues draft-ietf-dhc-dual-stack-01 Tim Chown dhc WG, IETF 60, San Diego, August 2, 2004.
IPv6 RADIUS attributes for IPv6 access networks draft-lourdelet-radext-ipv6-access-01 Glen Zorn, Benoit Lourdelet Wojciech Dec, Behcet Sarikaya Radext/dhc.
Coexistence and Migration
Microsoft Windows Server 2003 TCP/IP Protocols and Services Technical Reference Slide: 1 Lesson 17 Domain Name System (DNS)
資 管 Lee Lesson 13 IPv6 and Name Resolution. 資 管 Lee Lesson Objectives IPv6 name-to-address and address-to-name resolution IPv6 name resolution support.
May 20, 2004MARID WG Interim Meeting1 DNS Considerations for the MARID WG (esp., why TXT is bad) Edward Lewis
Basic Transition Mechanisms for IPv6 Hosts and Routers -RFC 4213 Kai-Po Yang
October 8, 2015 University of Tulsa - Center for Information Security Microsoft Windows 2000 DNS October 8, 2015.
Draft-ietf-v6ops-scanning-implications-00 IPv6 Implications for Network Scanning Tim Chown University of Southampton (UK) IETF 66,
1 Simplified DNS Query under IPv4/IPv6 Mixed Environment Hiroshi KITAMURA NEC Corporation
Measuring IPv6 Deployment Geoff Huston George Michaelson
IETF 531 DNS Discovery Update draft-ietf-ipv6-dns-discovery-04.txt Dave Thaler
IPv6 – What You Need To Know Tom Hollingsworth CCNP,CCVP,CCSP, MCSE.
Deploying a Web Application Presented By: Muhammad Naveed Date:
Working Group #4: Network Security Best Practices March 22, 2012 Presenter: Tony Tauber, Comcast WG #4 Member Via teleconference: Rod Rasmussen, Internet.
Draft-vandevelde-v6ops-addcon-00.txt IPv6 Unicast Address Assignment Considerations Gunter Van de Velde (editor) Tim Chown Ciprian Popoviciu IETF 65, March.
Testing Eyeball Happiness Fred Baker. The issue I bring to your attention In dual stack networks, especially if BCP 38 is in use, opening a session can.
IANA Reserved IPv4 Prefix for IPv6 Transition draft-weil-opsawg-provider-address-space-00 IETF 78 July
DNS SRV and NAPTR Use for SPEERMINT - Tom Creighton, Gaurav Khandpur Comcast SPEERMINT Intermin Meeting Philadelphia Sept
IPv6/IPv4 XLATE Trial Service for sharing IPv4 address Japan Internet Exchange Co., Ltd. Masataka MAWATARI.
Address planning. Introduction Network-Level Design Considerations Factors affecting addressing scheme Recommended practices Case studies 6/4/20162.
IP Version 6 ITL. © 2003 Hans Kruse & Shawn Ostermann, Ohio University 2 Information Sources Christian Huitema, “IPv6, The New Internet Protocol”,
Company Confidential 1 ICMPv6 Echo Replies for Teredo Clients draft-denis-icmpv6-generation-for-teredo-00 behave, IETF#75 Stockholm Teemu Savolainen.
* Agenda  What is the DNS ?  Poisoning the cache  Short term solution  Long term solution.
1 NCM _05_2001_c1 © 2001, Cisco Systems, Inc. All rights reserved. How would you prepare for the technology you need.
RFC 4477 DHCP: Dual-Stack Issues Speaker: Ching-Chen Chang Date:
NAT64-CPE Mode Operation for Opening Residential Service Gang Chen Hui
Information-Centric Networks Section # 3.1: DNS Issues Instructor: George Xylomenos Department: Informatics.
DNS Security 1. Fundamental Problems of Network Security Internet was designed without security in mind –Initial design focused more on how to make it.
File: /ram/wgchairs.sxi Date: 18 January, 2016 Slide 1 Impact of IPv6 Site-Local Addressing on Applications Margaret Wasserman Wind River
1 Computer Networks IPv6. 2 Motivation The primary motivation from changing the IP datagram format is to increase the size of the useable address space.
Well known site local unicast addresses to communicate with recursive DNS servers draft-ietf-ipv6-dns-discovery-07.txt
1 ipv6-node-02.PPT/ 18 November 2002 / John Loughney IETF 55 IPv6 Working Group IPv6 Node Requirements draft-ietf-ipv6-node-requirements-02.txt John Loughney.
1 3gpp_trans/ / IPv6 Transition Solutions for 3GPP Networks draft-wiljakka-3gpp-ipv6-transition-00.txt Juha Wiljakka,
&. & DNS and IPv6 IPv6 Summit, Canberra 31st October & 1 st November 2005 Chris Wright, Chief Technology Officer &
1 Unique Local Addresses / IPv6 WG / July 2003 / Bob Hinden Unique Local IPv6 Unicast Addresses Bob Hinden.
Internet Naming Service: DNS* Chapter 5. The Name Space The name space is the structure of the DNS database –An inverted tree with the root node at the.
IPv6 Workshop APAN Aug John Barlow Advanced Communication Services Coordinator, GrangeNet.
6 October 20031IPv6-WG - 9th Global Grid Forum, Chicago Guidelines for IP version independence in GGF specs T.Chown, J.Bound, S.Jiang Piers O’Hanlon.
Monitoring, analyzing and cleaning DNS configuration errors across European NRENs Slavko Gajin University of Belgrade, Serbia
Deploying Dual-Stack Lite in IPv6 Network draft-boucadair-dslite-interco-v4v6-04 Mohamed Boucadair
draft-pim-with-ipv4-prefix-over-ipv6-nh
M. Boucadair, J. Touch, P. Levis and R. Penno
Presentation transcript:

IPv6 DNS issues draft-ietf-dnsop-ipv6-dns-issues-00.txt

Draft objective Accepted as wg document last meeting Document IPv6 related issues Proposed operational recommendations Candidate for BCP or Informational

Name space continuity Every recursive DNS server SHOULD be either IPv4-only or dual stack. Every single DNS zone SHOULD be served by at least one IPv4 reachable DNS server This recommendation could be revisited if/when translation techniques between IPv4 & IPv6 are deployed.

Local scope addresses Link local addresses SHOULD NOT be published in the DNS. Site local addresses SHOULD NOT be published in the public DNS. They MAY be published in a site view of the DNS if two-face DNS is deployed. Question: –Can we recommend to put SL in the.local.arpa (or.site.arpa) zone?

SL & Reverse path DNS Site local addresses SHOULD NOT be populated in the public reverse tree. If two-face DNS is deployed, site local addresses MAY be populated in the local view of reverse tree.

RFC3041 & Reverse path DNS RFC3041 (privacy extension) addresses SHOULD NOT be published in reverse path DNS

6to4 & Reverse path DNS (unresolved) draft-moore-6to4-dns-03.txt draft-ymbk-…. ? Rfc1101 trick (see later)

“pre-populating” Reverse path DNS (unresolved) Widespread current practice for ISP serving home customers 2 reasons: –letting the customer manage the tree –Don’t want to answer calls when something goes wrong because of the absence of a PTR The size of v6 address space does not allow this practice any more

Pre-populating: solutions Wildcard entry –Several people are uneasy with wildcard in general DNS record synthesis (reverse & forward tree) –may affect DNSsec RFC1101 trick (not in the draft)

RFC1101 “trick” (last resort when no PTR has been found) Network admin configures PTR & AAAA for network name as in RFC1101 getaddrinfo(): –If PTR exist, returns it –If not, zero the interface ID and ask a PTR –Return string: $InterfaceID “+” $NetName getnameinfo(): –If AAAA exist, returns it –If not and syntax $InterfaceID “+” $NetName, get AAAA for NetName and paste $IntefaceID

Possible extensions Repeat trick at /48 boundary: –$InterfaceID “+” $SubnetID “+” $PrefixName Use it for 6to4 –$InterfaceID “+” $SubnetID “+6to4+” PTR(IPv4 underlying address)