BIND 10 #1627: Error: Server configuration failed: incomplete textual name

[BIND 10 Development]

#1627: Error: Server configuration failed: incomplete textual name
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:  UnAssigned
                       Type:         |                Status:  reviewing
  defect                             |             Milestone:
                   Priority:         |  Sprint-20120403
  medium                             |            Resolution:
                  Component:  bind-  |             Sensitive:  0
  ctl                                |           Sub-Project:  Core
                   Keywords:         |  Estimated Difficulty:  2
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by muks):

 Replying to [comment:7 jreed]:
 > If the problem is just a missing origin, how about just have "missing
 origin"?  Is it parsing? Why "textual name"?
 That error is from the name parser (origin is parsed by the name parser),
 so that's the general parse error message.

 We now get:
 {{{
 Error: unable to parse zone's origin: incomplete textual name
 }}}

 The name parser can return various errors. The general format is:
 {{{
 Error: unable to parse zone's origin: <name-parser-error>
 }}}

-- 
Ticket URL: <http://bind10.isc.org/ticket/1627#comment:8>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development