1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Unable to resolve target system name

Discussion in 'Plesk for Linux - 8.x and Older' started by edreport, Sep 22, 2008.

  1. edreport

    edreport Guest

    0
     
    My VPS (educationreporting.com) is at ipower.com and they have not found a fix for this message in last 24 hours - "Unable to resolve target system name" - when I run a tracert.

    The issue is I have to reboot my server every 2-3 minutes because everything will be fine and then I click a link on the site and get a "cannot find the server" message. If I reboot the server then enverything will be fine for a couple of minutes then I get the "cannot find the server" message again and have to reboot.

    Until yesterday afternoon everything has been perfect for last month and no major changes were made yesterday, just FTPing files.

    Anyone have any idea on how I can resolve this or what to examine?

    Thanks for you help in advance, steu
     
  2. Amin Taheri

    Amin Taheri Golden Pleskian Plesk Certified Professional

    33
     
    Joined:
    Jul 5, 2007
    Messages:
    1,398
    Likes Received:
    1
    Location:
    Seattle Area
    it sounds like a dns problem, I would start there.
     
  3. servertechs

    servertechs Guest

    0
     
    Check logs first
     
  4. ziba@

    ziba@ Guest

    0
     
    Hi,

    It this happenning to a particular domain (in this case let us know the domain name) or to all domains on this server?
    In any case when this problem reappears you should check how this domain resolves using the following commands:
    host -ta DOMAIN_NAME
    and
    dig +trace DOMAIN_NAME

    Also make sure that bind is up and running on your server:
    /etc/init.d/named status

    and check /var/log/messages for named related errors.
     
Loading...