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

    DNS setting and redirection

    Scheduled Pinned Locked Moved DHCP and DNS
    15 Posts 3 Posters 2.0k 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.
    • T
      TheNarc @mikekoke
      last edited by

      @mikekoke From what I can tell, you should have everything configured the way you want it. However, I don't have an answer for why 8.8.8.8 is being used if you don't have it configured anywhere. It inspired me to check the states on one of my own pfSense machines and I saw multiple DNS queries to both 8.8.8.8 and 8.8.4.4 coming from a Roku on my network. It could be that you have one or more devices on your LAN that override any DNS servers they are assigned with Google's. I'm not super familiar with the notations used in the display of states, but based on what you pasted, I would guess that the request to 8.8.8.8 is being redirected to 127.0.0.1, per your NAT port forward, and subsequently sent out via the DNS server you specified (8.8.8.4).

      I did notice, though, that (8.8.8.8.83) makes no sense to me. Did you paste that directly, or could this be a typo? I would expect that to be (8.8.8.8:53).

      lohphatL M 2 Replies Last reply Reply Quote 0
      • lohphatL
        lohphat @TheNarc
        last edited by

        @thenarc I have DNS restricted on my network to only allow the gateway (which DHCP specifies) and I still see 8.8.8.8 requests from my google home device (not surprising).

        Many IoT devices have their DNS settings hard-wired.

        SG-3100 24.11-RELEASE (arm) | Avahi (2.2_6) | ntopng (5.6.0_1) | openvpn-client-export (1.9.5) | pfBlockerNG-devel (3.2.1_20) | System_Patches (2.2.20_5)

        M 1 Reply Last reply Reply Quote 0
        • M
          mikekoke @TheNarc
          last edited by

          @thenarc said in DNS setting and redirection:

          @mikekoke From what I can tell, you should have everything configured the way you want it. However, I don't have an answer for why 8.8.8.8 is being used if you don't have it configured anywhere. It inspired me to check the states on one of my own pfSense machines and I saw multiple DNS queries to both 8.8.8.8 and 8.8.4.4 coming from a Roku on my network. It could be that you have one or more devices on your LAN that override any DNS servers they are assigned with Google's. I'm not super familiar with the notations used in the display of states, but based on what you pasted, I would guess that the request to 8.8.8.8 is being redirected to 127.0.0.1, per your NAT port forward, and subsequently sent out via the DNS server you specified (8.8.8.4).

          I did notice, though, that (8.8.8.8.83) makes no sense to me. Did you paste that directly, or could this be a typo? I would expect that to be (8.8.8.8:53).

          Sorry i was wrong to write, it was (8.8.8.8.83).
          However, if I understand correctly the DNS requests are all redirected to 8.8.4.4 right?

          T 1 Reply Last reply Reply Quote 0
          • T
            TheNarc @mikekoke
            last edited by

            @mikekoke From what you pasted, I believe so. Is that your expectation? Is 8.8.4.4 the only DNS server that you specified in General Settings?

            M 1 Reply Last reply Reply Quote 0
            • M
              mikekoke @TheNarc
              last edited by

              @thenarc said in DNS setting and redirection:

              @mikekoke From what you pasted, I believe so. Is that your expectation? Is 8.8.4.4 the only DNS server that you specified in General Settings?

              The target is to direct all the dns requests to pfsense in order to filter the url through pfblockerng and squid proxy and finally send the requests to the set dns
              As dns I configured 8.8.4.4 (this is because 8.8.8.8 is not responding and from the LAN I can not ping it) and then 1.1.1.1 and 1.0.0.1

              1 Reply Last reply Reply Quote 0
              • M
                mikekoke @lohphat
                last edited by mikekoke

                @lohphat said in DNS setting and redirection:

                @thenarc I have DNS restricted on my network to only allow the gateway (which DHCP specifies) and I still see 8.8.8.8 requests from my google home device (not surprising).

                Many IoT devices have their DNS settings hard-wired.

                All devices are configured to receive DNS from the router's DHCP

                T 1 Reply Last reply Reply Quote 0
                • T
                  TheNarc @mikekoke
                  last edited by

                  @mikekoke So it sounds like things are working as you would expect then? I don't see any further issue.

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    mikekoke @TheNarc
                    last edited by

                    @thenarc said in DNS setting and redirection:

                    @mikekoke So it sounds like things are working as you would expect then? I don't see any further issue.

                    Yes, but it is strange that the dns 8.8.8.8 is used and that the LAN can not ping the same dns

                    T 1 Reply Last reply Reply Quote 0
                    • T
                      TheNarc @mikekoke
                      last edited by

                      @mikekoke I don't think that 8.8.8.8 is being used. The output you provided looked to me as if some device on your network is trying to use 8.8.8.8, but the port forwarding rule you made is redirecting 8.8.8.8 to 127.0.0.1, and ultimately the request is being made to 8.8.4.4. I don't know why you'd be able to ping 8.8.4.4 and not 8.8.8.8 though.

                      M 1 Reply Last reply Reply Quote 0
                      • M
                        mikekoke @TheNarc
                        last edited by

                        @thenarc said in DNS setting and redirection:

                        @mikekoke I don't think that 8.8.8.8 is being used. The output you provided looked to me as if some device on your network is trying to use 8.8.8.8, but the port forwarding rule you made is redirecting 8.8.8.8 to 127.0.0.1, and ultimately the request is being made to 8.8.4.4. I don't know why you'd be able to ping 8.8.4.4 and not 8.8.8.8 though.

                        I found a device with the dns setting on 8.8.8.8, when I removed the setting even the states related to that dns were removed.

                        T 1 Reply Last reply Reply Quote 0
                        • T
                          TheNarc @mikekoke
                          last edited by

                          @mikekoke Well if a device is set to use 8.8.8.8 as a DNS server, you're going to see that in the states. But just seeing it in the states doesn't mean that pfSense is allowing it to use 8.8.8.8. It's saying "This client asked to do a DNS query to 8.8.8.8, but I'm redirecting that query to 127.0.0.1 since you told me to." And from there, unbound (the DNS resolver) takes over and forwards it to 8.8.4.4 since you configured it for forwarding mode.

                          M 1 Reply Last reply Reply Quote 0
                          • M
                            mikekoke @TheNarc
                            last edited by

                            @thenarc said in DNS setting and redirection:

                            @mikekoke Well if a device is set to use 8.8.8.8 as a DNS server, you're going to see that in the states. But just seeing it in the states doesn't mean that pfSense is allowing it to use 8.8.8.8. It's saying "This client asked to do a DNS query to 8.8.8.8, but I'm redirecting that query to 127.0.0.1 since you told me to." And from there, unbound (the DNS resolver) takes over and forwards it to 8.8.4.4 since you configured it for forwarding mode.

                            Thanks again for the clarification is just that I use Pfsense still recently and with some things I still have problems.

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