The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Named problem

Discussion in 'General Discussion' started by pacificw, Jun 8, 2008.

  1. pacificw

    pacificw Well-Known Member

    Joined:
    Aug 26, 2007
    Messages:
    65
    Likes Received:
    0
    Trophy Points:
    6
    Hello all,

    Hopefully someone can tell me how to fix this problem. I started to get this error a few days ago when I went to modify a zone file inside of cpanel.

    The section below in BOLD RED is Line 142 of 'Fast.pm'
    TIA
     
  2. pavemen

    pavemen Active Member

    Joined:
    Oct 8, 2003
    Messages:
    27
    Likes Received:
    0
    Trophy Points:
    1
    I am having the same problem. What I found is that the parser is failing at the lines in the zone file that have simply a "." for a field.

    This occurs when you add an A record to the hostname. The nameserver field in the first line (line 4 in the zone file) is a "." rather than something like "ns1.domain.tld." in a regular domain on the server.

    It also occurs on line 12 where you set teh actual NS pointer, the last field is "." but the parser is expecting something like "NS.DOMAIN.TLD."

    The single "." entries are breaking the parser.

    I am manually editing those zone files in /var/named
     
  3. MattDees

    MattDees cPanel Product Owner
    Staff Member

    Joined:
    Apr 29, 2005
    Messages:
    417
    Likes Received:
    1
    Trophy Points:
    18
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    When troubleshooting this issue in our internal test environments, I have been unable to reproduce this issue. I would like to look at your server to find the specific cause of this issue. If you would like for us to look into this issue, please open a ticket at https://tickets.cpanel.net/submit/index.cgi?reqtype=tickets and put "ATTN: QA Fast.pm" and reference this forum thread.
     
  4. pavemen

    pavemen Active Member

    Joined:
    Oct 8, 2003
    Messages:
    27
    Likes Received:
    0
    Trophy Points:
    1
    ticket submitted
     
  5. iUnknown

    iUnknown Member

    Joined:
    Jul 11, 2008
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    1
    Hello,

    What was the solution to this problem?

    Thanks.
     
  6. pavemen

    pavemen Active Member

    Joined:
    Oct 8, 2003
    Messages:
    27
    Likes Received:
    0
    Trophy Points:
    1
    Its been verified, logged as a bug and in the queue for correction. That is all I know.
     
  7. dannybedor

    dannybedor Registered

    Joined:
    Aug 21, 2005
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    Any progress regarding this bug?
    I still get the same error when updating to the latest Release 26881.
     
Loading...

Share This Page