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

    SOA record for local DNS

    Scheduled Pinned Locked Moved DHCP and DNS
    3 Posts 2 Posters 1.6k 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.
    • F
      fcapizzo
      last edited by

      I use my pfSense (2.1.5) box as a DHCP and a DNS server, configured as a subdomain of .local (something.local).  With Apple's iOS 8 and OS X 10 coming out recently, DNS is partially broken for me in that using the FQDN for a local system (like server.something.local) will not resolve.  Though for some strange reason just using the hostname by itself does work.

      After contacting Apple and seeing articles like this http://brain.adejones.com/2014/10/fix-name-resolution-on-windows-pptp-vpn-after-ios8-os-x-10-10-yosemite-update/, I need to have an SOA record for my local DNS server, which is my pfSense box.

      I have DNS forwarder installed on pfSense, but I don't see where I can add an SOA record.  I may also have pfSense mis-configured in regards to DNS but I'm not sure.  If anyone can point me in the right direction I would appreciate it.  Thanks!

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        .local is resolved using mDNS in the apple sphere.  Use something - anything - else for the DNS TLD.  .private would work.

        http://support.apple.com/en-us/ts3389

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

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

          I had a feeling that was the answer, so I just changed the TLD to .lan and it's all good now.  Thanks!

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