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

    DNS Lookups going to Google DNS even though I have OpenDNS configured?

    Scheduled Pinned Locked Moved DHCP and DNS
    15 Posts 4 Posters 1.8k 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.
    • J Offline
      JimPhreak
      last edited by

      @KOM:

      Is it possible that there is an application running on .208 that is doing the resolving for whatever reason, like a DNS benchmark for instance?

      Nope, I have nothing that would do any resolving running on .208.  It's a linux storage box that just has a few Dockers running (like Plex and a few others but nothing that has any DNS configured).

      @Derelict:

      Dude.  Those logs say 192.168.4.208 is making requests to google's 8.8.8.8 and 8.8.4.4. and they are being blocked by the rules on the LAN interface.

      That's correct, I purposely am blocking them.  The question is why are they making requests to Google?

      1 Reply Last reply Reply Quote 0
      • DerelictD Offline
        Derelict LAYER 8 Netgate
        last edited by

        That is a great question for the makers of that box.  it has nothing to do with pfSense.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • J Offline
          JimPhreak
          last edited by

          @Derelict:

          That is a great question for the makers of that box.  it has nothing to do with pfSense.

          I wasn't blaming pfsense I was just looking for some insight from others running pfsense.  Being that I'm pretty new to pfsense I wasn't sure if I misconfigured something on it.  But I'll look more closely at my server now.

          1 Reply Last reply Reply Quote 0
          • DerelictD Offline
            Derelict LAYER 8 Netgate
            last edited by

            dig/drill are your friends

            On 192.168.4.208:

            You can selectively do DNS queries to various servers:

            dig @8.8.8.8 www.google.com
            dig @192.168.4.1 www.google.com

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 0
            • KOMK Offline
              KOM
              last edited by

              It could also be something as simple as someone running nslookup from the command line and then specifying the Google DNS.

              dns.png
              dns.png_thumb

              1 Reply Last reply Reply Quote 0
              • J Offline
                JimPhreak
                last edited by

                @KOM:

                It could also be something as simple as someone running nslookup from the command line and then specifying the Google DNS.

                I would but it's a linux box.  And the dig/drill commands don't appear to be present.

                It looks like it's an issue with one of my dockers though so I'm looking into that.

                1 Reply Last reply Reply Quote 0
                • KOMK Offline
                  KOM
                  last edited by

                  I would but it's a linux box.

                  cough

                  dns.png
                  dns.png_thumb

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

                    "I would but it's a linux box.  And the dig/drill commands don't appear to be present."

                    Well then install them..  What linux distro are you using that nslookup is not installed?

                    Last login: Wed Jul  8 12:02:03 2015 from 10.0.8.6
                    user@ubuntu:~$ nslookup

                    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 25.07 | Lab VMs 2.8, 25.07

                    1 Reply Last reply Reply Quote 0
                    • J Offline
                      JimPhreak
                      last edited by

                      @johnpoz:

                      "I would but it's a linux box.  And the dig/drill commands don't appear to be present."

                      Well then install them..  What linux distro are you using that nslookup is not installed?

                      Last login: Wed Jul  8 12:02:03 2015 from 10.0.8.6
                      user@ubuntu:~$ nslookup

                      It's an unRAID server which is built off Slackware.  But I've determined it's definitely an issue with a particular Docker.  I see the nameserver's listed as the Google DNS servers in the Docker's log so it's not even really a Linux issue.

                      1 Reply Last reply Reply Quote 0
                      • KOMK Offline
                        KOM
                        last edited by

                        But I've determined it's definitely an issue with a particular Docker.

                        For me, playing detective is the funnest part of the job.

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