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

    PFSense + Kloxo, setting up name-servers.

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

      @Metu69salemi:

      Add a portforward ( Firewall: NAT: Port Forward )

      
      WAN  TCP/UCP   *   *    50.xx.xx.51  53  first.internal.address   53
      
      
      
      WAN  TCP/UCP   *   *    50.xx.xx.52  53  second.internal.address   53
      
      

      let these port forwarding rule add firewall rules.

      I put these rules in, and reset all states…
      Nothing.

      External Resolution is not working.

      http://www.intodns.com/technoriot.com

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

        there is something else, because i can use 50-73-183-52-pennsylvania.hfc.comcastbusiness.net as lookup server in nslookup, but i can't make any queries

        1 Reply Last reply Reply Quote 0
        • G Offline
          ghost1one
          last edited by

          What could it be? I'm lost  :'(

          1 Reply Last reply Reply Quote 0
          • G Offline
            ghost1one
            last edited by

            Can anyone shed some light into setting up an internal DNS server on a CENT OS machine behind Pfsense for external resolution?

            I want all incoming dns queries to be handled by a name server behind the firewall.

            1 Reply Last reply Reply Quote 0
            • W Offline
              wallabybob
              last edited by

              Have you configured the server to accept such requests?

              Does the server log any DNS requests?

              1 Reply Last reply Reply Quote 0
              • G Offline
                ghost1one
                last edited by

                It is a kloxo install with iptables turned off at the moment.

                Pfsense is preventing it from being accessed somehow.

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

                  if you have created portforward rules, which i gave you earlier, then pfsense isn't blocking those.

                  1 Reply Last reply Reply Quote 0
                  • G Offline
                    ghost1one
                    last edited by

                    Could it be my virtual ip mapping? What would be the proper settings for my virtual up addresses?

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

                      I highly doubt that, because i can connect to your dns/bind server, but can't make any queries.

                      
                      Microsoft Windows [Version 6.1.7601]
                      Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
                      
                      C:\Users\*sanitized*>nslookup
                      Default Server:  v*sanitized*m
                      Address:  192.168.0.25
                      
                      > www.google.com
                      Server:  v*sanitized*m
                      Address:  192.168.0.25
                      
                      Non-authoritative answer:
                      Name:    www.l.google.com
                      Addresses:  209.85.148.104
                                209.85.148.105
                                209.85.148.106
                                209.85.148.147
                                209.85.148.99
                                209.85.148.103
                      Aliases:  www.google.com
                      
                      > lserver 8.8.8.8
                      Default Server:  google-public-dns-a.google.com
                      Address:  8.8.8.8
                      
                      > www.google.com
                      Server:  google-public-dns-a.google.com
                      Address:  8.8.8.8
                      
                      Non-authoritative answer:
                      Name:    www.l.google.com
                      Addresses:  74.125.39.147
                                74.125.39.105
                                74.125.39.104
                                74.125.39.103
                                74.125.39.99
                                74.125.39.106
                      Aliases:  www.google.com
                      
                      > lserver ns1.technoriot.com
                      Default Server:  ns1.technoriot.com
                      Address:  50.73.183.51
                      
                      > www.google.com
                      Server:  ns1.technoriot.com
                      Address:  50.73.183.51
                      
                      DNS request timed out.
                          timeout was 2 seconds.
                      DNS request timed out.
                          timeout was 2 seconds.
                      DNS request timed out.
                          timeout was 2 seconds.
                      DNS request timed out.
                          timeout was 2 seconds.
                      *** Request to ns1.technoriot.com timed-out
                      >
                      
                      
                      1 Reply Last reply Reply Quote 0
                      • W Offline
                        wallabybob
                        last edited by

                        @ghost1one:

                        It is a kloxo install with iptables turned off at the moment.

                        Disabling iptables may not be sufficient; the name server software itself might need to be configured to respond to DNS requests from public IP addresses. (Some SSH server packages need to be configured to specify the IP addresses from which the server is allowed to accept connections.)

                        @ghost1one:

                        Pfsense is preventing it from being accessed somehow.

                        That might be true. Can you provide evidence? For example, does the pfSense firewall log report blocked DNS requests on the appropriate interface?

                        1 Reply Last reply Reply Quote 0
                        • G Offline
                          ghost1one
                          last edited by

                          http://network-tools.com/default.asp?prog=express&host=ns1.technoriot.com

                          When doing a trace route, it times out after hop 14…

                          Also, my server does not return any records...

                          How can I fix this?

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

                            These failures are "easy" to fix:

                            1. Missing MX-record: add mx-record to your mail-server's public ip
                            2. Missing SOA: add Start Of Authority number, which must increased every update

                            but all of these seems to be dns-server problems. And that's why doesn't mean that pfsense is only quilty.

                            1 Reply Last reply Reply Quote 0
                            • G Offline
                              ghost1one
                              last edited by

                              I think I might have fixed it…

                              For some reason if you check " Non-cached DNS " on that site, it'll show my SOA record.

                              Weird.

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