unable to resolve host address from client

Discussion in 'ISPConfig 3 Priority Support' started by erickr, Dec 21, 2013.

  1. erickr

    erickr New Member

    I suspect this is a dns issue.

    I'm hosted at Digital Ocean and my ns records at my registrar all point to ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com for all of my domains (myhostname.com, mydomain.info).

    At Digital Ocean my DNS records are:

    myhostname.com:

    $TTL 1800
    @ IN SOA NS1.DIGITALOCEAN.COM. hostmaster.myhostname.com. (
    1387510867 ; last update: 2013-12-20 03:41:07 UTC
    3600 ; refresh
    900 ; retry
    1209600 ; expire
    1800 ; ttl
    )
    IN NS NS1.DIGITALOCEAN.COM.
    NS NS2.DIGITALOCEAN.COM.
    NS NS3.DIGITALOCEAN.COM.
    MX 1 ASPMX.L.GOOGLE.COM.
    MX 5 ALT1.ASPMX.L.GOOGLE.COM.
    MX 5 ALT2.ASPMX.L.GOOGLE.COM.
    MX 10 ASPMX2.GOOGLEMAIL.COM.
    MX 10 ASPMX3.GOOGLEMAIL.COM.
    @ IN A 123.456.789.012
    server1 CNAME @




    mydomain.info:

    $TTL 1800
    @ IN SOA NS1.DIGITALOCEAN.COM. hostmaster.mydomain.info. (
    1387313990 ; last update: 2013-12-17 20:59:50 UTC
    3600 ; refresh
    900 ; retry
    1209600 ; expire
    1800 ; ttl
    )
    IN NS NS1.DIGITALOCEAN.COM.
    NS NS2.DIGITALOCEAN.COM.
    NS NS3.DIGITALOCEAN.COM.
    @ IN A 123.456.789.012



    I performed a clean install using the Perfect Server guide for Debian Wheezy (nginx).

    The hostname is server1.myhostname.com. I've created 1 client (client1), 1 website (mydomain.info), 1 ftp user (client1ftpuser) and one shell user (client1client1).

    The DNS records in ISPConfig for mydomain.info are:

    A mydomain.info. 123.456.789.012 0 3600
    CNAME www mydomain.info. 0 3600
    NS mydomain.info. ns1.myhostname.com. 0 86400
    NS mydomain.info. ns2.myhostname.com. 0 86400


    The website (mydomain.info) resolves correctly.

    When I attempt to access the shell (as client1client1) and wget the latest joomla package from joomlacode.org I receive the error "unable to resolve host address `joomlacode.org'"

    If I attempt to wget using my admin user it resolves correctly. The issue only arises when I'm logged in as the client.

    When I try to upload via ftps my connection is very slow (~30KBps). I've uploaded to another server server at the same node at over 1 MBs over sftp. I'm not sure if the slower speed is a result of ssl encryption or dns issues.

    I suspect my DNS setup is incorrect and possibly inefficient. Can you help me correct and advise on potential ftps speed issues?
     
    erickr, Dec 21, 2013
    #1
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    If your dns records point o the digitalocean nameserver, then you will have to crete the dns records in the dns server of digitalocean and not your ispconfig server. Sp you dont need the rcords in your ispconig server.

    Dns issues cab cause a slowdown in the initial connect of. Ftp connection, but they can not low down the transfer speed.

    Regarding dns resolution isdue eith wget, please check that the nameservers listed in /etc/resolv.conf are correct and reachable from your server.
     
    till, Dec 21, 2013
    #2

Share This Page