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

    Configure DNS to reverse this IP

    Scheduled Pinned Locked Moved DHCP and DNS
    6 Posts 4 Posters 17.5k 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.
    • L Offline
      Landmine
      last edited by

      I'm trying to get names to go with my IP's in BandwidthD.

      It is telling me to "Configure DNS to reverse this IP"

      I know it should be simple, but I'm accessing it remotely, and I'm scared if I do it wrong I'll kill the connection and have to wait a week or so to get to it locally to fix it.

      1 Reply Last reply Reply Quote 0
      • P Offline
        podilarius
        last edited by

        Just go to System -> General and put in some DNS servers.

        1 Reply Last reply Reply Quote 0
        • V Offline
          vladick0732
          last edited by

          I did so, but the problem remained. Maybe it's not working for IP on the LAN?

          1 Reply Last reply Reply Quote 0
          • P Offline
            podilarius
            last edited by

            On LAN … most likely not ... unless you use an internal DNS server to serve that to pfSense.

            1 Reply Last reply Reply Quote 0
            • johnpozJ Online
              johnpoz LAYER 8 Global Moderator
              last edited by

              So you can use the dns forwarder and setup records for your boxes for dns, or have it resolve dhcp clients..  So for example clients on my network can resolve my 192.168.1.x IPs via the dns forwarder on pfsense.

              ;; QUESTION SECTION:
              ;100.1.168.192.in-addr.arpa.    IN      PTR

              ;; ANSWER SECTION:
              100.1.168.192.in-addr.arpa. 1  IN      PTR    i5-w7.local.lan.

              ;; Query time: 3 msec
              ;; SERVER: 192.168.1.253#53(192.168.1.253)

              So depending on how you have pfsense itself for dns you may or may not be able to resolve them.

              so since I point pfsense to 127.0.0.1 it works on pfsense

              [2.1-BETA0][admin@pfsense.local.lan]/root(2): dig -x 192.168.1.100
              ;; QUESTION SECTION:
              ;100.1.168.192.in-addr.arpa.    IN      PTR

              ;; ANSWER SECTION:
              100.1.168.192.in-addr.arpa. 1  IN      PTR    i5-w7.local.lan.

              ;; Query time: 4 msec
              ;; SERVER: 127.0.0.1#53(127.0.0.1)

              But if you are pointing pfsense to say your ISP, then no it would never resolve a PTR for a private network IP.

              An intelligent man is sometimes forced to be drunk to spend time with his fools
              If you get confused: Listen to the Music Play
              Please don't Chat/PM me for help, unless mod related
              SG-4860 24.11 | Lab VMs 2.8, 24.11

              1 Reply Last reply Reply Quote 0
              • V Offline
                vladick0732
                last edited by

                Activated rules DHCP Registration and Static DHCP in the tab Services: DNS forwarder and it worked. Thanks for the advice!

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