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

    TinyDNS Wizard

    Scheduled Pinned Locked Moved DHCP and DNS
    3 Posts 2 Posters 995 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.
    • reginaldo_barretoR Offline
      reginaldo_barreto
      last edited by

      Hello colleagues,

      I would like everyone's help to resolve a doubt for enriching my knowledge in pfSense.

      I have a domain running under W2k3, the main server I have running Active Directory and DNS Server.
      I have a pfSense doing the work of DHCP server.

      My goal is to leave the pfSense serving internal DNS and DHCP.

      current structure
      domain CM2.local

      -Domain Controller (Win) - IP 192.168.0.254
      -DNS-Server (Win) - IP 192.168.0.254
      -DHCP server (pfSense) - IP 192.168.0.253

      desired structure
      domain CM2.local

      -Domain Controller (Win) - IP 192.168.0.254
      -DNS-Server (pfSense) - IP 192.168.0.253
      -DHCP server (pfSense) - IP 192.168.0.253

      If possible show you step by step what to fill in the wizard.

      Reginaldo Barreto

      1 Reply Last reply Reply Quote 0
      • V Offline
        vindenesen
        last edited by

        Hei Reginaldo Barreto,

        You might know this already, but just wanted to say that DNS is such an important and integrated component of Active Directory, that I would highly recommend you to keep using the AD controller as DNS server. Also see http://technet.microsoft.com/en-us/library/cc726034.aspx (which explains the advantages of using AD-integrated DNS).

        If you should still choose to use pfSense as your local DNS server, I see two options:

        • Create and maintain all Active Directory-related DNS records on pfSense to make sure your domain members are able to locate the domain controllers. A quick google-search returned this: http://searchwindowsserver.techtarget.com/tip/Basic-DNS-records-for-Active-Directory-DCs , not sure if that includes all requirements.

        • Setup pfSense to use your domain controllers as the DNS server.

        Support the project by buying a Gold Subscription at https://portal.pfsense.org
        Running pfSense on SuperMicro A1SRI-2758F with ESXi 5.5

        1 Reply Last reply Reply Quote 0
        • reginaldo_barretoR Offline
          reginaldo_barreto
          last edited by

          thanks for the feedback,

          I will continue with my current network structure.

          Reginaldo Barreto

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