Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Local hostnames not resolving

    Guacamole
    2
    2
    83
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Dark_Dragone
      Dark_Dragone last edited by

      Not sure what is wrong but when setting up a connection I have to use the FQDN instead of just a local hostname. IE "Alienware-14" wont resolve in guacamole but when using that with the local domain name it does, IE "Alienware-14.dragon"

      I have guacamole setup in cloudron running on ubuntu 20.04 inside of proxmox. The Ubuntu VM is able to resolve the local hostnames for any of my machines just fine as it has the search domain.

      Is there a way to add a search domain in the dns config for cloudron/guacamole? I saw that cloudron uses unbound and think I have the conf set right.

      Stub-zone:
      name: "dragon"
      stub-addr: 192.168.0.5
      stub-first: yes

      girish 1 Reply Last reply Reply Quote 0
      • girish
        girish Staff @Dark_Dragone last edited by girish

        @dark_dragone not 100% sure but I think search domains is a client feature. This means that docker (the DNS client on behalf of the guac container) should be configured to have a dns search. See https://docs.docker.com/config/containers/container-networking/ (--dns-search). Maybe you can quickly try by editing /etc/systemd/system/docker.service.d/cloudron.conf and restarting docker.

        I think you can also add it in your local machine's /etc/resolv.conf

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Powered by NodeBB