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

    Since upgrade to 2.2 dns for lan is broken

    Scheduled Pinned Locked Moved DHCP and DNS
    15 Posts 5 Posters 3.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.
    • M Offline
      Mayoor
      last edited by

      very good information and I am newbie ….. not too familiar with linux or pfsense .... step by step will help.

      I think when pinging from pfsense computer fdqn is resolved. I can ping yahoo.com or google.com from the pfsense computer it does resolve.

      Problem is when on the lan computer ..... dns is set to 192.168.1.1 and pfsense is not forwarding or giving connection to the lan computer to resolve fdqn.

      Will greatly appreciate a step by step to fix.

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

        so on a windows machine do nslookup.. like this

        C:>nslookup
        Default Server:  pfSense.local.lan
        Address:  192.168.1.253

        www.google.com
        Server:  pfSense.local.lan
        Address:  192.168.1.253

        Non-authoritative answer:
        Name:    www.google.com
        Addresses:  2607:f8b0:4002:c07::67
                  74.125.196.147
                  74.125.196.105
                  74.125.196.99
                  74.125.196.103
                  74.125.196.106
                  74.125.196.104

        What do you get?

        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.1 | Lab VMs 2.8.1, 25.07.1

        1 Reply Last reply Reply Quote 0
        • M Offline
          Mayoor
          last edited by

          Here is before using  obtain automatic dns server …...

          nslookup

          DNS request timed out.
                  timeout was 2 seconds
          Defualt Server: Unknown
          Address:  192.168.2.1

          www.yahoo.com
          Server: UnKnown
          Address:  192.168.2.1

          DNS request timed out.
                  timeout was 2 seconds (repeated 3 more times)
          *** Request ot UnKnown timed out

          After use this setting for dns server .... set to 75.75.75.75 and 8.8.8.8 using network and sharing in windows 7 pro ...

          nslookup
          Default Server: cdns01.comcast.net
          Address: 75.75.75.75

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

            well clearly pfsense is not answering your query..  So why is that - simple troubleshooting..  For starters if the forwarder or resolver even running?  Check your services.

            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.1 | Lab VMs 2.8.1, 25.07.1

            1 Reply Last reply Reply Quote 0
            • M Offline
              Mayoor
              last edited by

              unbound resolver is stopped …. I tried to restart and not starting.

              Back at work will try to find more articles on what caused that.... I have very rudimentary setup.

              I have taken in back to factory reset and only changed the lan to 192.168.2.x

              Nothing else installed

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

                well if its not running.. That would explain why it didn't even tell you nx, or serv error.

                What does the log say about unbound (resolver) not starting?

                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.1 | Lab VMs 2.8.1, 25.07.1

                1 Reply Last reply Reply Quote 0
                • M Offline
                  Mayoor
                  last edited by

                  To fix I went to Services >>> DNS Resolver >>>> unclick Enable DNS Resolver >>>> Save

                  went back clicked DNS Resolver >>>> Save and unbound Service started ….

                  This must be some type of bug .... Maybe someone will have a solution or an upgrade.

                  I am checking this out at home before installing at work .... so far it is a no go .... to temperamental.

                  I need to use dansguardian or snort and virus guard of some sort .... may be need to and get paid untangle

                  1 Reply Last reply Reply Quote 0
                  • O Offline
                    orangesofcourse
                    last edited by

                    I'm having a similar issue with Pfsense 2.2.

                    I have a clean install of pfsense on esxi and every week or so it will stop responding to DNS queries. I can ping the DNS server (8.8.8.8) just fine from the PC but i'm unable to access any web pages using the domain name. The way to fix this issue for me is to restart the unbound service. I have attached my settings for DNS resolver and the dns servers.

                    Here is the output for nslookup:

                    www.google.com
                    Server:  pfSense.lab.local
                    Address:  192.168.1.1

                    Non-authoritative answer:
                    Name:    www.google.com
                    Addresses:  2607:f8b0:4003:c01::67
                              74.125.30.104
                              74.125.30.147
                              74.125.30.105
                              74.125.30.103
                              74.125.30.99
                              74.125.30.106

                    I can provide more information if required.

                    pfsense-resolver.png
                    pfsense-resolver.png_thumb
                    pfsense-general.png
                    pfsense-general.png_thumb

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

                      There is another thread talking about unbound restarting.. If you are having an issue where unbound is having issue then yes it can stop.

                      Look in your logs is unbound restarting or stoping?  If having issues with unbound, switch back to just the forwarder.

                      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.1 | Lab VMs 2.8.1, 25.07.1

                      1 Reply Last reply Reply Quote 0
                      • O Offline
                        orangesofcourse
                        last edited by

                        @johnpoz:

                        There is another thread talking about unbound restarting.. If you are having an issue where unbound is having issue then yes it can stop.

                        Look in your logs is unbound restarting or stoping?  If having issues with unbound, switch back to just the forwarder.

                        Unbound is not restarting on its own. I have to restart the service for it to start responding to DNS queries. i'll try forwarder and see how it works out.

                        1 Reply Last reply Reply Quote 0
                        • C Offline
                          CiscoKid85
                          last edited by

                          Simple question but any idea why pfSense isn't replying with its hostname? nslookup comes back quickly but is listed as "Unknown". Is this a reverse DNS thing?

                          C:\Users\Ryan>nslookup
                          Default Server:  UnKnown
                          Address:  2601:6:7780:581a:20d:b9ff:xxxx:xxxx
                          
                          > google.com
                          Server:  UnKnown
                          Address:  2601:6:7780:581a:20d:b9ff:xxxx:xxxx
                          
                          Non-authoritative answer:
                          Name:    google.com
                          Addresses:  2607:f8b0:4006:80d::1000
                                    74.125.226.66
                                    74.125.226.69
                                    74.125.226.64
                                    74.125.226.68
                                    74.125.226.78
                                    74.125.226.71
                                    74.125.226.70
                                    74.125.226.65
                                    74.125.226.72
                                    74.125.226.67
                                    74.125.226.73
                          
                          >
                          
                          1 Reply Last reply Reply Quote 0
                          • C Offline
                            CiscoKid85
                            last edited by

                            bump

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