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

    Understanding Static IP Mappings

    Scheduled Pinned Locked Moved DHCP and DNS
    2 Posts 2 Posters 2.9k 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.
    • B Offline
      broncoBrad
      last edited by

      I'm curious why does the Static IP Mapping allow for defining a hostname. Like say my windows computer has the name (hostname) jimbob-PC. So typically when pinging/connecting, I can just type ping jimbob-PC.

      But if I want to create a static IP mapping for my windows computer and I were to assign it a hostname other than jimbob-PC, such as myworldnow, does that mean that pinging/connecting now uses myworldnow or can I still connect via jimbob-PC??

      Say, I go to another windows computer on my LAN and want to view my computer in Network Places. How is it going to show up?

      Thanks in advance!

      1 Reply Last reply Reply Quote 0
      • W Offline
        wallabybob
        last edited by

        @broncoBrad:

        I'm curious why does the Static IP Mapping allow for defining a hostname. Like say my windows computer has the name (hostname) jimbob-PC. So typically when pinging/connecting, I can just type ping jimbob-PC.

        So the DNS forwarder can be given a known name for the IP address. A name can be included in a DHCP request. I presume the name in the pfSense static IP mapping overrides any name supplied in the DHCP request.

        @broncoBrad:

        But if I want to create a static IP mapping for my windows computer and I were to assign it a hostname other than jimbob-PC, such as myworldnow, does that mean that pinging/connecting now uses myworldnow or can I still connect via jimbob-PC??

        You can connect by whatever name is known to the name server you are using. If you are using DNS then the name needs to be known to DNS. If you are using Windows networking to browse shares then I believe you can use the DNS registered name(s) OR the name(s) configured in Windows networking.

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