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

    Unbound and android 4.1

    Scheduled Pinned Locked Moved pfSense Packages
    18 Posts 4 Posters 3.6k Views
    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.
    • G
      grandrivers
      last edited by

      ive not just the dns entrys under general setup

      pfsense plus 25.03 super micro A1SRM-2558F
      C2558 32gig ECC  60gig SSD

      1 Reply Last reply Reply Quote 0
      • D
        doktornotor Banned
        last edited by

        Either specify your DNS servers in DHCP server configuration, or remove those IPv6 ones from general setup. (If you can reproduce this with latest 2.1.1 snapshot, you should file a bug; DHCPv4 server is not supposed to pick up IPv6 stuff it does not understand from somewhere.)

        (Apparently, you only see this with DNS forwarder disabled, no matter whether unbound is installed or not.)

        1 Reply Last reply Reply Quote 0
        • B
          bryan.paradis
          last edited by

          @grandrivers:

          ive not just the dns entrys under general setup

          Are you sure you do not have the 3 dns entries inserted on this page? Services -> DHCP Server -> Any interface tab. You can see where I am referring to in the attached picture. DNS here should be left blank.

          /usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpd.conf -pf /var/run/dhcpd.pid em2
          

          Could this be on a secondary interface you have setup? I only have 1 interface "LAN" but you may have multiple tabs setup. The error above refers to em2. Please double check. Also can you copy and paste your /var/dhcpd/etc/dhcpd.conf file?

          ![2014-02-23 19_42_39-pfsense.localdomain - Services_ DHCP server.png](/public/imported_attachments/1/2014-02-23 19_42_39-pfsense.localdomain - Services_ DHCP server.png)
          ![2014-02-23 19_42_39-pfsense.localdomain - Services_ DHCP server.png_thumb](/public/imported_attachments/1/2014-02-23 19_42_39-pfsense.localdomain - Services_ DHCP server.png_thumb)

          1 Reply Last reply Reply Quote 0
          • G
            grandrivers
            last edited by

            not related to unbound i had set under general tab dns 2 ivp6 addresses and that caused problems for dhcpv4

            pfsense plus 25.03 super micro A1SRM-2558F
            C2558 32gig ECC  60gig SSD

            1 Reply Last reply Reply Quote 0
            • W
              wagonza
              last edited by

              Ok great. The only issue for unbound is the dump of the cache. I need to make it work a little bit more reliable.
              Will check it out.

              Follow me on twitter http://twitter.com/wagonza
              http://www.thepackethub.co.za

              1 Reply Last reply Reply Quote 0
              • B
                bryan.paradis
                last edited by

                @grandrivers:

                not related to unbound i had set under general tab dns 2 ivp6 addresses and that caused problems for dhcpv4

                What verison of pfsense are you running?

                1 Reply Last reply Reply Quote 0
                • G
                  grandrivers
                  last edited by

                  runnng 2.1.1 64 bit its present in 2.1 also

                  pfsense plus 25.03 super micro A1SRM-2558F
                  C2558 32gig ECC  60gig SSD

                  1 Reply Last reply Reply Quote 0
                  • D
                    doktornotor Banned
                    last edited by

                    Enough, pretty clear bug…

                    https://redmine.pfsense.org/issues/3483

                    1 Reply Last reply Reply Quote 0
                    • B
                      bryan.paradis
                      last edited by

                      https://redmine.pfsense.org/projects/pfsense/repository/revisions/9399370b367df7b73b84d605f4f44599c93b0bbe/diff

                      https://redmine.pfsense.org/issues/3015

                      1 Reply Last reply Reply Quote 0
                      • D
                        doktornotor Banned
                        last edited by

                        @bryan.paradis:

                        https://redmine.pfsense.org/projects/pfsense/repository/revisions/9399370b367df7b73b84d605f4f44599c93b0bbe/diff

                        https://redmine.pfsense.org/issues/3015

                        That fix clearly did not work (presumably due to the fact is is failing to check anything but the first and second DNS entries in System - General Setup.)

                        1 Reply Last reply Reply Quote 0
                        • B
                          bryan.paradis
                          last edited by

                          @doktornotor:

                          @bryan.paradis:

                          https://redmine.pfsense.org/projects/pfsense/repository/revisions/9399370b367df7b73b84d605f4f44599c93b0bbe/diff

                          https://redmine.pfsense.org/issues/3015

                          That fix clearly did not work (presumably due to the fact is is failing to check anything but the first and second DNS entries in System - General Setup.)

                          It is related to the same problem but it is a fix for DNS zones. I have updated your bug report with the related information.

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