ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Unable to ping FQDN .local hosts from Fedora 26

    IT Discussion
    4
    8
    1.0k
    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.
    • ObsolesceO
      Obsolesce
      last edited by

      I came across an issue on Fedora 26 where I was unable to ping the FQDN address of anything .local (server.domain.local). It was weird because I could ping the IP, I could ping the server without the .domain.local, nslookup server.domain.local would show the correct results, as would dig, but using the FQDN with .local just did not work.

      After some digging around, I found that editing the following file and changing the line below and rebooting resolved the issue:

      # Edit this file:  /etc/avahi/avahi-daemon.conf

# Uncomment the below line:
domain-name=local

# Change the above line to ".local" (add a period):
domain-name=.local

      Then reboot.

      Problem resolved.

      I'm not sure what exactly was happening, but you'd think something like this would work out-of-box. Just one more thing to configure added to the list...

      JaredBuschJ black3dynamiteB 2 Replies Last reply Reply Quote 1
      • JaredBuschJ
        JaredBusch @Obsolesce
        last edited by

        @tim_g said in Unable to ping FQDN .local hosts from Fedora 26:

        I came across an issue on Fedora 26 where I was unable to ping the FQDN address of anything .local (server.domain.local). It was weird because I could ping the IP, I could ping the server without the .domain.local, nslookup server.domain.local would show the correct results, as would dig, but using the FQDN with .local just did not work.

        After some digging around, I found that editing the following file and changing the line below and rebooting resolved the issue:

        # Edit this file:  /etc/avahi/avahi-daemon.conf

# Uncomment the below line:
domain-name=local

# Change the above line to ".local" (add a period):
domain-name=.local

        Then reboot.

        Problem resolved.

        I'm not sure what exactly was happening, but you'd think something like this would work out-of-box. Just one more thing to configure added to the list...

        Or just don't use .local? 🙂

        ObsolesceO 1 Reply Last reply Reply Quote 0
        • black3dynamiteB
          black3dynamite @Obsolesce
          last edited by

          @tim_g said in Unable to ping FQDN .local hosts from Fedora 26:

          I came across an issue on Fedora 26 where I was unable to ping the FQDN address of anything .local (server.domain.local). It was weird because I could ping the IP, I could ping the server without the .domain.local, nslookup server.domain.local would show the correct results, as would dig, but using the FQDN with .local just did not work.

          After some digging around, I found that editing the following file and changing the line below and rebooting resolved the issue:

          # Edit this file:  /etc/avahi/avahi-daemon.conf

# Uncomment the below line:
domain-name=local

# Change the above line to ".local" (add a period):
domain-name=.local

          Then reboot.

          Problem resolved.

          I'm not sure what exactly was happening, but you'd think something like this would work out-of-box. Just one more thing to configure added to the list...

          I notice that too. But I see it has them making us stop using .local for FQDN.
          Have you notice that most if not all distro uses .localdomain instead of .local when doing a clean install?

          ObsolesceO 1 Reply Last reply Reply Quote 0
          • ObsolesceO
            Obsolesce @JaredBusch
            last edited by

            @jaredbusch said in Unable to ping FQDN .local hosts from Fedora 26:

            @tim_g said in Unable to ping FQDN .local hosts from Fedora 26:

            I came across an issue on Fedora 26 where I was unable to ping the FQDN address of anything .local (server.domain.local). It was weird because I could ping the IP, I could ping the server without the .domain.local, nslookup server.domain.local would show the correct results, as would dig, but using the FQDN with .local just did not work.

            After some digging around, I found that editing the following file and changing the line below and rebooting resolved the issue:

            # Edit this file:  /etc/avahi/avahi-daemon.conf

# Uncomment the below line:
domain-name=local

# Change the above line to ".local" (add a period):
domain-name=.local

            Then reboot.

            Problem resolved.

            I'm not sure what exactly was happening, but you'd think something like this would work out-of-box. Just one more thing to configure added to the list...

            Or just don't use .local? 🙂

            Nothing wrong with .local. It's not worth switching.

            1 Reply Last reply Reply Quote 0
            • ObsolesceO
              Obsolesce @black3dynamite
              last edited by

              @black3dynamite said in Unable to ping FQDN .local hosts from Fedora 26:

              @tim_g said in Unable to ping FQDN .local hosts from Fedora 26:

              I came across an issue on Fedora 26 where I was unable to ping the FQDN address of anything .local (server.domain.local). It was weird because I could ping the IP, I could ping the server without the .domain.local, nslookup server.domain.local would show the correct results, as would dig, but using the FQDN with .local just did not work.

              After some digging around, I found that editing the following file and changing the line below and rebooting resolved the issue:

              # Edit this file:  /etc/avahi/avahi-daemon.conf

# Uncomment the below line:
domain-name=local

# Change the above line to ".local" (add a period):
domain-name=.local

              Then reboot.

              Problem resolved.

              I'm not sure what exactly was happening, but you'd think something like this would work out-of-box. Just one more thing to configure added to the list...

              I notice that too. But I see it has them making us stop using .local for FQDN.
              Have you notice that most if not all distro uses .localdomain instead of .local when doing a clean install?

              There's no need for that silly limitation. I should be able to have a domain called whatever I want, and when I ping or go to it by FQDN, it should work if DNS is set up right.

              1 Reply Last reply Reply Quote 0
              • momurdaM
                momurda
                last edited by momurda

                I think you might be able to add using
                search=domain.com domain.local
                in resolv.conf or ifcfg-eth0 file

                ObsolesceO 1 Reply Last reply Reply Quote 0
                • ObsolesceO
                  Obsolesce @momurda
                  last edited by

                  @momurda said in Unable to ping FQDN .local hosts from Fedora 26:

                  I think you might be able to add using
                  search=domain.com domain.local
                  in resolv.conf or ifcfg-eth0 file

                  resolve.conf already had domain.local. So the issue had to be elsewhere.

                  1 Reply Last reply Reply Quote 0
                  • black3dynamiteB
                    black3dynamite
                    last edited by

                    I don't remember where I found it, but there was another possible solution to fix it by changing a line in /etc/nsswitch.conf

                    # Default setting
hosts:      files mdns4_minimal [NOTFOUND=return] dns myhostname

# Noticed dns is now in front of mdns4_minimal
hosts:      files dns mdns4_minimal [NOTFOUND=return] myhostname
                    1 Reply Last reply Reply Quote 0
                    • 1 / 1
                    • First post
                      Last post