Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    TinyDNS for internal DNS, need help

    DHCP and DNS
    5
    10
    11.4k
    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.
    • R
      romainp
      last edited by

      Hi guys,
      I hope that someone could help me with this. I am trying to understand how works dns package of pfsense and its use.
      My primary goal is to use the dns server tiny dns as my internal dns server so I can manage my domain and records.
      But I can't understand how to configure to right way with dns forwarder and dhcp and can't fin a valid how to to achieve this.

      Can somebody gives me some hints or advices to do this? BTW I am using PFsense 2 right now
      Thanks

      1 Reply Last reply Reply Quote 0
      • C
        cirmler
        last edited by

        @romainp:

        Hi guys,
        I hope that someone could help me with this. I am trying to understand how works dns package of pfsense and its use.
        My primary goal is to use the dns server tiny dns as my internal dns server so I can manage my domain and records.
        But I can't understand how to configure to right way with dns forwarder and dhcp and can't fin a valid how to to achieve this.

        Can somebody gives me some hints or advices to do this? BTW I am using PFsense 2 right now
        Thanks

        Same here! Would be great if someone could offer some "first steps" including how to set up the rule to query from LAN

        1 Reply Last reply Reply Quote 0
        • P
          Porklaser
          last edited by

          Same here. I'd like to run my own resolver for 2 reasons:

          1. My ISP's dns servers are infected with adware and can't be trusted. (No charter, putting a cookie in my browser and showing me a fake 404 page instead of an ad laden search page doesn't cut it)

          2. Google's DNS servers (And other public DNS resolvers) work, but break brain-dead geolocation caching schemes so. (Akamai and friends)

          1 Reply Last reply Reply Quote 0
          • C
            cirmler
            last edited by

            Maybe someone can point us to an manual… ?!  :'(

            Thanks!

            1 Reply Last reply Reply Quote 0
            • A
              arunkeerthan
              last edited by

              Same here….I dont know why people always remains silent when we are talking about tiny DNS and internal DNS server.    I have some unanswered old threads related with .
              Nobody here to help in this whole forum..... ???

              1 Reply Last reply Reply Quote 0
              • P
                p0ddie
                last edited by

                Add me to the list of people trying to get tinydns to work as internal dns server… I started my own thread here http://forum.pfsense.org/index.php/topic,33441.0.html before I found this one… It seems like either no one knows how tinydns works, it's simply broken and people ran out of patience replying to posts about it... or no one likes tinydns and ignores it ;-)

                Does anyone have a running installation?

                1 Reply Last reply Reply Quote 0
                • R
                  romainp
                  last edited by

                  I haven't for a while now since I focus on having a stable pf2 running.
                  But for what I understand, all traffic comming from your lan (for ex) to the port 53  udp should be redirected to 127.0.0.1 where the tindns daemon listen for connection.

                  I will test further as soon as I can.

                  1 Reply Last reply Reply Quote 0
                  • P
                    p0ddie
                    last edited by

                    Spent another hour trying to figure out how to set this up, also with firewall rules.

                    Please check out my setup:

                    Setup of tinyDNS: http://img412.imageshack.us/i/tinyb.jpg/
                    Firewall rule: http://img13.imageshack.us/i/rule2.jpg/
                    Firewall rule in detail: http://img195.imageshack.us/i/ruleb.jpg/

                    Is there something faulty or should it work like this?

                    1 Reply Last reply Reply Quote 0
                    • R
                      romainp
                      last edited by

                      Seems good. At least that's what I wanted to setup.

                      Only thing: have you setup the port forward?
                      For what I understand, the dhcp server (from the lan let's say) should give the ip of the lan ip as the dns server
                      then forward the port 53 udp from the lan ip to the 127.0.0.1 ip.
                      It should then be able to resolve internaly. For external resolution, I think tinydns should give the request to the dns forwarder.
                      At this point, it should work as the package wants us to do so.

                      I have not tested this solution right now, but as soon as I can I will try the exact same config as yours.

                      1 Reply Last reply Reply Quote 0
                      • P
                        p0ddie
                        last edited by

                        I was under the impression tinyDNS is a real dns server, querying root servers for all external dns entries… that's what I need. If I wanted to rely on dns queries being forwarded to other dns servers, I'd just stick to the dns forwarder (which I am doing now because I currently have no other dns server around...).

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.