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

    DNS names not picked up by bandwidthd

    Scheduled Pinned Locked Moved
    DHCP and DNS
    3
    6
    8.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.
    • P
      Pootle
      last edited by

      I have DHCP running and I have register DHCP leases and static mappings set in the DNS service page.

      I can see pc names in the DHCP leases and I can connect to machines using my local domain name (iain.local) and all works fine.

      But bandwidthd just shows IP addresses and only the machine with a static mapping (and pfsense itself) are identified by name.

      Does the DNS relay not support reverse lookup for dhcp leases?

      I'm running
      1.0.1-SNAPSHOT-02-27-2007
      built on Fri Mar 2 00:59:00 EST 2007

      1 Reply Last reply Reply Quote 0
      • S
        sullrich
        last edited by

        @Pootle:

        I have DHCP running and I have register DHCP leases and static mappings set in the DNS service page.

        I can see pc names in the DHCP leases and I can connect to machines using my local domain name (iain.local) and all works fine.

        But bandwidthd just shows IP addresses and only the machine with a static mapping (and pfsense itself) are identified by name.

        Does the DNS relay not support reverse lookup for dhcp leases?

        I'm running
        1.0.1-SNAPSHOT-02-27-2007
        built on Fri Mar 2 00:59:00 EST 2007

        BandwidthD will not work in this way.  It uses the ISP's dns server or whatever items that are entered into the system, general page.

        Pointing the DNS at itself would be dangerous and can have unpredictable results in case that is your follow up question.

        1 Reply Last reply Reply Quote 0
        • H
          hoba
          last edited by

          the dnsforwarder will detect a loop and shut down requests for some time (have seen that on not properly configured systems). So don't use "loopback" DNS.

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

            Sorry I don't follow this, I'm not trying to change the DNS setup in any way, and bandwidthd is only a user of the DNS service.  Surely bandwidthd could use the local (on the same machine) DNS service and not use the DNS identified to pfSense general settings.

            Using nslookup on my laptop, with pfsense machine as the DNS server, it quite happily resolves the IP addresses back to names for the DHCP allocated addresses.

            Surely what is needed is to be able to configure bandwidthd to use the local machine as a DNS server instead of picking up the DNS servers configured on the machine itself?

            1 Reply Last reply Reply Quote 0
            • S
              sullrich
              last edited by

              No, bandwidthd uses the standard resolver.  There is no way to force it to use a different DNS server and I really don't feel like changing the C code.

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

                Ah! OK Thanks Sullrich, one to put in the wibni list then  :)

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post