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

    Disabling connection-specific DNS suffix [SOLVED]

    Scheduled Pinned Locked Moved DHCP and DNS
    7 Posts 3 Posters 8.1k 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.
    • A
      Alween
      last edited by

      How the heck do you disable the DNS suffix on pfSense 1.2.2 embedded? I just can't figure it out! >:(
      The DHCP server automatically serves it to all clients, and it breaks DNS on my subnet.

      This is how my /etc/resolv.conf looks like on a linux client that requests a lease from the router:

      domain mydomain.com
      search mydomain.com

      nameserver 192.168.1.1

      Those lines in bold shouldn't be there.
      Removing them by hand fixes the DNS issue.
      See previous thread.

      1 Reply Last reply Reply Quote 0
      • F
        focalguy
        last edited by

        This just a guess but try removing the Domain setting in  System: General Setup.

        1 Reply Last reply Reply Quote 0
        • A
          Alween
          last edited by

          It does not work. the domain name is mandatory.

          The following input errors were detected:
              * The field 'Domain' is required.

          1 Reply Last reply Reply Quote 0
          • dotdashD
            dotdash
            last edited by

            1. Why not use domain.local or somesuch?
            2. Reflection is a cheap hack for the lazy, there are better ways of going about it.
            1 Reply Last reply Reply Quote 0
            • A
              Alween
              last edited by

              @dotdash:

              1. Why not use domain.local or somesuch?
              2. Reflection is a cheap hack for the lazy, there are better ways of going about it.

              Hey, that seems to have worked! Thanks.
              Nat reflection is working properly. I am using it because I'm lazy the domain has a wildcard forward rule at my ISP's DNS server. Trying to access any subdomain from my LAN doesn't quite work.

              1 Reply Last reply Reply Quote 0
              • dotdashD
                dotdash
                last edited by

                @Alween:

                the domain has a wildcard forward rule at my ISP's DNS server.

                Oh, that explains why you were getting the weird behavior described in the previous thread.

                1 Reply Last reply Reply Quote 0
                • A
                  Alween
                  last edited by

                  Funny thing is this has never happened on my linksys WRT54GL with dd-wrt that I was using prior installing pfSense/Alix.
                  Anyway, [SOLVED].

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