[mythtv-commits] Ticket #2469: mythTV backends do not perform DNS lookups

[MythTV]

#2469: mythTV backends do not perform DNS lookups
-----------------------------+----------------------------------------------
 Reporter:  wm161 at wm161.net  |        Owner:  ijr     
     Type:  defect           |       Status:  reopened
 Priority:  minor            |    Milestone:  0.21    
Component:  mythtv           |      Version:  0.20    
 Severity:  medium           |   Resolution:          
-----------------------------+----------------------------------------------
Changes (by hugh at mimosa.com):

 * cc: hugh at mimosa.com (added)
  * status:  closed => reopened
  * resolution:  wontfix =>

Comment:

 I consider this a bug.  Why?

  * mythtvsetup accepts a domain name without complaint

  * mythfrontend accepts a domain name without complaint

  * a domain name does not work.  The diagnostic is highly misleading.
 Here is an example from a mythfrontend log:

 {{{
 2006-11-10 00:05:44.178 Connecting to backend server:
 redburn.mimosa.com:6543 (try 1 of 5)
 2006-11-10 00:05:44.181 Connection timed out.
                         You probably should modify the Master Server
                         settings in the setup program and set the
                         proper IP address.
 }}}
 What it is ''actually'' trying is 0.0.0.0:6543 and yet it reports
 redburn.mimosa.com.
 Do we really expect users to use tcpdump to find their errors?

 Recommendations:

 1. wherever an IP address is expected, accept a domain name.

 2. mythtv-setup should validate each IP address input.  If it is badly
    formed, report right away, when it is easiest for the user to fix it.

 3. (not as important, but for consistency)
    * Wherever a port is expected, accept a service name (see the man
    page services(5)).
    * Port number syntax should be checked on input.
    * It might be useful if the mythtv-setup form specified whether these
 ports are
    TCP or UDP.

 4. the mythfrontend log entry should not just show what the user
    entered as an IP address but also what it was interpreted as.

    For example, in my case, it could have said:
    {{{Connecting to backend server: redburn.mimosa.com:6543 (0.0.0.0:6543)
 (try 1 of 5)}}}

 PS: if there is now a Feature Wishlist wiki entry for this, please place a
 pointer in this trac entry.

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/2469#comment:4>
MythTV <http://www.mythtv.org/>
MythTV