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


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. AdGuard Home
  3. Question about DNS stuffs

Question about DNS stuffs

Scheduled Pinned Locked Moved AdGuard Home
6 Posts 4 Posters 1.3k Views 4 Watching
  • 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.
    • ? Offline
      ? Offline
      A Former User
      wrote on last edited by A Former User
      #1

      So when I go to the setup guide tab it lists an IP address that does not quite match my server's IP. It does not appear to be accessible off the network. All of my IPs start at 192.168 and this one begins with 172.18.

      Is this normal? lol no clue how to interpret this.

      girishG 1 Reply Last reply
      0
      • robiR Offline
        robiR Offline
        robi
        wrote on last edited by
        #2

        it's the internal container network.

        Conscious tech

        1 Reply Last reply
        0
        • ? A Former User

          So when I go to the setup guide tab it lists an IP address that does not quite match my server's IP. It does not appear to be accessible off the network. All of my IPs start at 192.168 and this one begins with 172.18.

          Is this normal? lol no clue how to interpret this.

          girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by
          #3

          @atrilahiji The 172.18 IP is the internal docker IP address. You can ignore that. You should be able to configure devices using your server IP - i.e the 192.168 one.

          ? 1 Reply Last reply
          0
          • girishG girish

            @atrilahiji The 172.18 IP is the internal docker IP address. You can ignore that. You should be able to configure devices using your server IP - i.e the 192.168 one.

            ? Offline
            ? Offline
            A Former User
            wrote on last edited by
            #4

            @girish Ah I see. Also seems like the docker IP works lol. But cool I'll use the one my router assigns. Thanks for answering this noob question lol

            1 Reply Last reply
            0
            • necrevistonnezrN Offline
              necrevistonnezrN Offline
              necrevistonnezr
              wrote on last edited by
              #5

              As per https://docs.cloudron.io/apps/adguard-home/, I have added 192.168.1.0/24 to the Access settings of AdGuard - that’s all I have to do to restrict DNS queries to my local network, correct? Should I add e.g. the Docker IPs as well (starting with 172….)?

              When adding the DNS Server to the router, I used the local IP of my Cloudron, 192.168.1.10, as was suggested above, and it works. What do I use as the IPv6 address?

              girishG 1 Reply Last reply
              0
              • necrevistonnezrN necrevistonnezr

                As per https://docs.cloudron.io/apps/adguard-home/, I have added 192.168.1.0/24 to the Access settings of AdGuard - that’s all I have to do to restrict DNS queries to my local network, correct? Should I add e.g. the Docker IPs as well (starting with 172….)?

                When adding the DNS Server to the router, I used the local IP of my Cloudron, 192.168.1.10, as was suggested above, and it works. What do I use as the IPv6 address?

                girishG Offline
                girishG Offline
                girish
                Staff
                wrote on last edited by girish
                #6

                @necrevistonnezr Yes, that should be enough. You can verify if this is the case by trying out host www.cloudron.io <public-ip-of-your-cloudron-server>. It should timeout.

                As for IPv6, from a quick look at the code, it looks like we only bind port 53 to the server's IPv4 addresses. Let me check and get back tomorrow.

                1 Reply Last reply
                0
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                  • Login

                  • Don't have an account? Register

                  • Login or register to search.
                  • First post
                    Last post
                  0
                  • Categories
                  • Recent
                  • Tags
                  • Popular
                  • Bookmarks
                  • Search