32-bit ASN for DNS Services
•
0 likes•663 views
Presented by Anand Buddhdev in Closing Plenary at RIPE 60, Prague
Recommended
More Related Content
What's hot
What's hot (10)
Similar to 32-bit ASN for DNS Services
Similar to 32-bit ASN for DNS Services (20)
More from RIPE Meetings
More from RIPE Meetings (18)
Recently uploaded
Recently uploaded (20)
32-bit ASN for DNS Services
- 1. RIPE Network Coordination Centre 32-bit ASN for DNS Services Anand Buddhdev DNS Services Manager, RIPE NCC Anand Buddhdev RIPE 60, May 2010 http://www.ripe.net 1
- 2. RIPE Network Coordination Centre Background • RIPE NCC managed zones - Forward zones (ripe.net, etc) - Reverse zones (IPv4 and IPv6) - ENUM (e164.arpa) - Secondary for ip6.arpa and many other zones • Two servers - ns-pri.ripe.net - ns-sec.ripe.net • Single servers • Unicast Anand Buddhdev RIPE 60, May 2010 http://www.ripe.net 2
- 3. RIPE Network Coordination Centre Upcoming Changes • Multi-server architecture • Anycast - 193.0.9.0/24 - 2001:67c:e0::/48 • Serve in-addr.arpa • Independent ASN Anand Buddhdev RIPE 60, May 2010 http://www.ripe.net 3
- 4. RIPE Network Coordination Centre ASN 197000 Anand Buddhdev RIPE 60, May 2010 http://www.ripe.net 4
- 5. RIPE Network Coordination Centre Interoperability • Older BGP speakers talk to AS 23456 • Transitive attribute AS4_PATH contains the 32-bit ASN • 32-bit ASN speakers reconstruct the correct path • All major vendors have 32-bit ASN support Anand Buddhdev RIPE 60, May 2010 http://www.ripe.net 5
- 6. RIPE Network Coordination Centre Connection Details • Connection at Amsterdam Internet Exchange • 6 transit providers - All support 32-bit ASNs • Peering with AMS-IX route servers - Recent OpenBGPD - Also supports 32-bit ASNs - 111 of 333 peers have 32-bit ASN support Anand Buddhdev RIPE 60, May 2010 http://www.ripe.net 6
- 7. RIPE Network Coordination Centre View from Route Servers SAIX Route Server (older Cisco IOS) BGP routing table entry for 193.0.9.0/24, version 62729846 Paths: (4 available, best #4, table Default-IP-Routing-Table) Not advertised to any peer 3491 6939 23456 196.25.9.45 from 196.43.9.254 (196.43.9.254) Origin IGP, metric 2, localpref 100, valid, internal Community: 5713:777 Originator: 196.43.9.245, Cluster list: 196.43.9.254 Anand Buddhdev RIPE 60, May 2010 http://www.ripe.net 7
- 8. RIPE Network Coordination Centre View from Route Servers Opentransit Route Server (JunOS 9.3S7.2) 193.0.9.0/24 *[BGP/170] 2w6d 10:26:46, MED 100, localpref 85, from 193.251.245.11 AS path: 1273 197000 I Anand Buddhdev RIPE 60, May 2010 http://www.ripe.net 8
- 9. RIPE Network Coordination Centre Success Criteria • Prefix visibility in NetSense • Visibility in DNSMON - Will DNS clients be able to reach us? Anand Buddhdev RIPE 60, May 2010 http://www.ripe.net 9
- 10. RIPE Network Coordination Centre 100% Visibility in NetSense Anand Buddhdev RIPE 60, May 2010 http://www.ripe.net 10
- 11. RIPE Network Coordination Centre 100% Visibility in DNSMON (IPv4) Anand Buddhdev RIPE 60, May 2010 http://www.ripe.net 11
- 12. RIPE Network Coordination Centre 100% Visibility in DNSMON (IPv6) Anand Buddhdev RIPE 60, May 2010 http://www.ripe.net 12
- 13. RIPE Network Coordination Centre “It Just Works!” Anand Buddhdev RIPE 60, May 2010 http://www.ripe.net 13
- 14. RIPE Network Coordination Centre Anand Buddhdev RIPE 60, May 2010 http://www.ripe.net 14