Navigation

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

    .local domains conflict with Bonjour/Avahi

    DHCP and DNS
    1
    1
    6188
    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.
    • V
      vynce last edited by

      If you have your domain set to local in pfSense and you have clients using Bonjour/Avahi on your network (if you have any Apple machines/devices on your network then Bonjour is being used), then those clients will not be able to resolve any local hostnames (i.e. pfsense.local) because Bonjour will intercept any .local name requests and attempt to handle them itself. The solution is to change the domain in pfSense to something other than local. Mac OS X 10.6 will work correctly if you simply add an additional label to the domain: i.e. mynet.local. Older versions of Mac OS X and Linux systems using Avahi will likely only work if your domain does not end in .local and/or require additional configuration.

      If you're trying to debug this problem, affected machines will have no problems resolving .local hostnames via dig and nslookup, but name resolution will fail via more indirect methods (web browser and other utilities that go through the full hostname lookup procedure). You will still be able to access the service directly by IP.

      References:
      Mac OS X v10.4, 10.5, 10.6: How to look up ".local" hostnames via both Bonjour and standard DNS
      Avahi and Unicast Domains .local
      iPhone DNS - pfSense

      pfSense devs: It might be a good idea to change the default pfSense domain to something other than local or include a warning.

      1 Reply Last reply Reply Quote 0
      • First post
        Last post