#23 BLOC 8.2.0 (: DNS configuration

[Zarro Boogs per Child]

#23: DNS configuration
------------------------------+---------------------------------------------
   Reporter:  jg              |       Owner:  cscott              
       Type:  task            |      Status:  assigned            
   Priority:  blocker         |   Milestone:  8.2.0 (was Update.2)
  Component:  infrastructure  |     Version:                      
 Resolution:                  |    Keywords:                      
Next_action:  never set       |    Verified:  0                   
  Blockedby:                  |    Blocking:                      
------------------------------+---------------------------------------------

Comment(by martin.langhoff):

 I don't think this is a blocker for 8.2.0, the DNS infrastructure is
 satisfactory at the moment. This can be either closed as done (as I am
 providing a summary below) or relabelled to "DNS infrastructure long-term-
 goals" and set to "Future release".

 The current implementation is:

  - The XS runs a traditional IPv4 NAT'ed LAN and a split-horizon DNS
 server implemented with BIND. See #7655 - where I'm exploring dnsmasq as a
 replacement. The internal LAN sees additional per-service local names that
 point to the XS (but could be disaggregated later to several servers).

  - XOs get DHCP on a IPv4 LAN. They do not get a public IP address, and do
 not get a usable DNS name. We could improve on this but it's low-pri as
 collaboration is coordinated via XMPP.

  - XSs get their nameservers set via DHCP if available or via manual
 configuration by the local NOC & technicians.

  - Given that most XSs will be _behind NAT_ themselves, any extensive DNS
 setup will depend of a move to IPv6 with some kind of tunnelling between
 IPv6 sites (XSs, MoE/NOC) which is a huge task in itself.

-- 
Ticket URL: <http://dev.laptop.org/ticket/23#comment:13>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system