#11203 NORM Not Tri: search string in /etc/resolv.conf might be backwards

[Zarro Boogs per Child]

#11203: search string in /etc/resolv.conf might be backwards
-----------------------------+----------------------------------------------
 Reporter:  jvonau           |                 Owner:  dsd                               
     Type:  defect           |                Status:  new                               
 Priority:  normal           |             Milestone:  Not Triaged                       
Component:  network manager  |               Version:  Development source as of this date
 Keywords:  11.3.0           |           Next_action:  never set                         
 Verified:  0                |   Deployment_affected:                                    
Blockedby:                   |              Blocking:                                    
-----------------------------+----------------------------------------------
 I'm using dhcp to hand out a search string to search additional domains.
 The dhclient.*.lease file created is attached. With the attached
 resolv.conf file I'm unable to ping "schoolserver" which would resolve to
 schoolserver.home.vonau.ca. If I switch the order of the search string to
 have home.vonau.ca appear first, the ping to schoolserver works fine. I'm
 wondering if this is a resolver issue in the sense that the extra domains
 are not searched or is NM putting resolv.conf together incorrectly.

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