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

    Weird LAN IPs

    Scheduled Pinned Locked Moved
    DHCP and DNS
    3
    5
    2.5k
    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.
    • R
      Raleigh
      last edited by

      Hi there,

      What I have:

      DNS Forwarders enabled
      DNS Server disabled

      The problem: when I tried to ping a computer by hostname, it returned a different IP not the LAN IP (192.168.1.x)

      Need help on this,

      Thanks

      1 Reply Last reply Reply Quote 0
      • Cry HavokC
        Cry Havok
        last edited by

        Details a little to vague to really allow any help, however…

        It sounds like the unspecified hostname is resolved by the DNS server's you are using.

        1 Reply Last reply Reply Quote 0
        • R
          Raleigh
          last edited by

          Everything's running ok until I tried to disable the DNS Forwarder, I lost internet connection. I enabled it again and when I tried to ping a computer by hostname, it returned a different IP (74.200.220.215) not the LAN IP (192.168.0.x)

          I can still ping the LAN but only if I specified their local IP (192.168.0.x)

          What went wrong?

          1 Reply Last reply Reply Quote 0
          • GruensFroeschliG
            GruensFroeschli
            last edited by

            When you disable the DNS Forwarder and your clients have the pfSense as DNS Server the "should" no longer be able to resolve names.

            I suspect that 74.200.220.215 is your public IP on WAN. This happens when you try to resolve a name that does not exist.

            Did you enable on the DNS forwarder page that DHCP-lease names are added to the hosts-list of the DNS forwarder?

            We do what we must, because we can.

            Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

            1 Reply Last reply Reply Quote 0
            • R
              Raleigh
              last edited by

              @GruensFroeschli:

              When you disable the DNS Forwarder and your clients have the pfSense as DNS Server the "should" no longer be able to resolve names.

              I suspect that 74.200.220.215 is your public IP on WAN. This happens when you try to resolve a name that does not exist.

              Did you enable on the DNS forwarder page that DHCP-lease names are added to the hosts-list of the DNS forwarder?

              This is what I only have on my DNS Forwarder…

              Thanks

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