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

    DNS Settings

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    10 Posts 3 Posters 5.7k 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
      jpmtg
      last edited by

      I'm unsure of what name servers to have listed in my setup. I have DNS installed on two windows servers. Should I have these listed in pfsense? Should the domain be my actual windows domain? Here is the current resolv.conf

      [2.0-RELEASE][admin@pfsense.localdomain]/root(1): cat /etc/resolv.conf
      domain localdomain
      nameserver 127.0.0.1
      nameserver 69.89.74.4
      nameserver 69.89.70.4

      I ask this because I cannot access packages from the GUI. Here is the error I receive:
      Unable to communicate with www.pfsense.com. Please verify DNS and interface configuration, and that pfSense has functional Internet connectivity.

      When I try to traceroute to pfsense I get the following:
      [2.0-RELEASE][admin@pfsense.localdomain]/root(11): traceroute pfsense.com
      traceroute: unknown host pfsense.com

      Thank you for assisting me.

      1 Reply Last reply Reply Quote 0
      • M
        Metu69salemi
        last edited by

        nameserver 69.89.74.4 isn't answering but another one is.
        Do you have dns servers running on windwos servers?

        1 Reply Last reply Reply Quote 0
        • J
          jpmtg
          last edited by

          @Metu69salemi:

          nameserver 69.89.74.4 isn't answering but another one is.
          Do you have dns servers running on windwos servers?

          I do. I have two running

          1 Reply Last reply Reply Quote 0
          • M
            Metu69salemi
            last edited by

            do you have set forwarders or root hints working on those?
            if so you could try if those work better.
            try with windows

            
            cmd
            nslookup
            lserver "ip-address of your windows dns server"
            8.8.8.8 <- there should come google-public-dns-a.google.com
            www.google.com <- there should come few ip-addresses and url's
            
            

            if those work you could change the dns to internal.

            but i'm using 8.8.8.8 and 8.8.4.4 by pfsense and dhcp is sharing internal dns(windows DC)

            1 Reply Last reply Reply Quote 0
            • pttP
              ptt Rebel Alliance
              last edited by

              Check this:

              http://forum.pfsense.org/index.php/topic,41073.msg212176.html#msg212176

              http://forum.pfsense.org/index.php/topic,40442.0.html

              Maybe you are in the same situation / scenario

              1 Reply Last reply Reply Quote 0
              • J
                jpmtg
                last edited by

                @ptt:

                Check this:

                http://forum.pfsense.org/index.php/topic,41073.msg212176.html#msg212176

                http://forum.pfsense.org/index.php/topic,40442.0.html

                Maybe you are in the same situation / scenario

                I do not fall into this scenario.

                1 Reply Last reply Reply Quote 0
                • J
                  jpmtg
                  last edited by

                  @Metu69salemi:

                  do you have set forwarders or root hints working on those?
                  if so you could try if those work better.
                  try with windows

                  
                  cmd
                  nslookup
                  lserver "ip-address of your windows dns server"
                  8.8.8.8 <- there should come google-public-dns-a.google.com
                  www.google.com <- there should come few ip-addresses and url's
                  
                  

                  if those work you could change the dns to internal.

                  but i'm using 8.8.8.8 and 8.8.4.4 by pfsense and dhcp is sharing internal dns(windows DC)

                  X:>nslookup
                  Default Server:  server1.domain.local
                  Address:  10.0.1.100

                  8.8.8.8
                  Server:  server1.domain.local
                  Address:  10.0.1.100

                  Name:    google-public-dns-a.google.com
                  Address:  8.8.8.8

                  www.google.com
                  Server:  server1.domain.local
                  Address:  10.0.1.100

                  Non-authoritative answer:
                  Name:    www.l.google.com
                  Addresses:  74.125.65.106
                            74.125.65.104
                            74.125.65.105
                            74.125.65.147
                            74.125.65.99
                            74.125.65.103
                  Aliases:  www.google.com

                  1 Reply Last reply Reply Quote 0
                  • M
                    Metu69salemi
                    last edited by

                    then you can use internal dns servers on pfsense or you could use 8.8.8.8 & 8.8.4.4

                    1 Reply Last reply Reply Quote 0
                    • J
                      jpmtg
                      last edited by

                      @Metu69salemi:

                      then you can use internal dns servers on pfsense or you could use 8.8.8.8 & 8.8.4.4

                      So my ISP name servers just plain suck i assume?

                      1 Reply Last reply Reply Quote 0
                      • M
                        Metu69salemi
                        last edited by

                        that is possible, but problem could reside almost everywhere

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