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

    Bandwithd with windows DNS and DHCp

    pfSense Packages
    4
    8
    3.1k
    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.
    • A
      amsteel
      last edited by

      I have setup local DNS sever under general setup. I checked "Do not use the DNS Forwarder as a DNS server for the firewall" and also un-checked "Allow DNS server list to be overridden by DHCP/PPP on WAN".

      Everything works fine on all other computers. I can ping any local computers by name and go internet with no issue, including pfsense box. However I got "Configure DNS to reverse this IP" with BandwidthD.

      Are there anythings I missed?

      Thanks for the help.

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

        Hello, does anyone use DNS and DHCP running on anther machine other than pfSense box?

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

          Yes I have DHCP server and DNS server both running windows server 2008 R2 .

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

            @Weiyentan:

            Yes I have DHCP server and DNS server both running windows server 2008 R2 .

            Hi Weiyentan,

            Do you use Bandwithd? Have you ever experience the issue I have?

            Thanks,

            1 Reply Last reply Reply Quote 0
            • P
              phil.davis
              last edited by

              "Configure DNS to reverse this IP" with BandwidthD

              This is a generic message from bandwidthd. It doesn't need you to configure DNS on pfSense. It just needs the DNS that is configured to have reverse lookup zones so that the IP addresses can be turned into names.
              e.g. If you are using DNS on a Windows Server, then you need to add appropriate reverse lookup zone/s for your LAN subnet/s and populate them with entries (and/or let Win Server manage it as clients join the domain…).

              As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
              If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

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

                I use OS X Server for DNS and DHCP and PFSense as MultiWAN gateway. BandwidthD shows the DNS names of the machines that have PTR records in OS X Server.

                If you use Windows Server for this, you should configure a reverse lookup zone, and set PTR records there. New-joined clients will automatically get PTR names, which will last until scavenging occurs.

                Best regards

                Kostas

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

                  Thanks for the reply. The windows admin just informed me that the reverse lookup zone was setup but with wrong subnet. It is corrected now and I will try it later and report results back here.

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

                    After the revers zone issue was corrected, everything works fine now.

                    Thanks for the help.

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