BIND 10 #228: bindctl could stall if it can't resolve its own host name

[BIND 10 Development]

#228: bindctl could stall if it can't resolve its own host name
-------------------------+--------------------------------------------------
 Reporter:  jinmei       |       Owner:  UnAssigned                 
     Type:  enhancement  |      Status:  new                        
 Priority:  minor        |   Milestone:  05. 3rd Incremental Release
Component:  bind-ctl     |    Keywords:                             
Sensitive:  0            |  
-------------------------+--------------------------------------------------
 The current implementation of !BindCmdInterpreter tries to resolve its own
 host name into an IPv4 address using socket.gethostbyname to generate a
 (psuedo?)unique session ID.

 I think this is not a good idea.  It's not good for several reasons, but
 most important one would be that the resolution is not always successful
 or could even stall (e.g.) if the recursive server happens to be
 unreachable.

 As far as I see it, it doesn't have to be an IPv4 address.  So I'd suggest
 to apply the attached patch.

 Please review it.  I hope it will be included in the next release.

-- 
Ticket URL: <http://bind10.isc.org/ticket/228>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development