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

ESXI 5.1 and Name Resolution Question

Scheduled Pinned Locked Moved Virtualization
3 Posts 3 Posters 2.0k 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.
  • P
    phreshjive
    last edited by Feb 10, 2014, 4:15 PM

    Go easy on me.  Been working at this for hours with nothing to show.

    Running ESXI 5.1, 1312873.  Have the following VMs setup with fixed IPs and DNS info pointing towards both 8.8.8.8 and 192.168.1.1.

    192.168.1.1 – pfSense
    192.168.1.2 – Ubuntu Server for UniFi Controller (accessible at https://192.168.1.2:8443/)
    192.168.1.3 – ESXI
    192.168.1.5 – PBX In A Flash
    192.168.1.6 – UnRAID
    192.168.1.7 – Ubuntu Server for ownCloud
    192.168.1.8 – Ubuntu Server for Plex (accessible at http://192.168.1.8:32400/web/index.html#!/dashboard)
    192.168.1.9 – NZBApp
      - Headphones: http://192.168.1.9:8181/home
      - Couchpotato: http://192.168.1.9:8085/home/
      - Sickbeard: http://192.168.1.9:8081/home/

    Similarly to this post: https://forum.pfsense.org/index.php?topic=3292.0, want to be able to type the hostname of the VM (e.g. "pfSense") in the browser of any of the devices on my network and  it would go to its IP (e.g. 192.168.1.1).  Another example would be typing Headphones and arriving at http://192.168.1.9:8181/home.  Read and cannot for the life of me figure out what to do.

    Please help.

    1 Reply Last reply Reply Quote 0
    • H
      heper
      last edited by Feb 13, 2014, 9:41 PM

      check services–>dns forwarder-->host/domain overrides

      you'd have to set your clients dns servers @ 192.168.1.1 for this to work

      1 Reply Last reply Reply Quote 0
      • J
        johnpoz LAYER 8 Global Moderator
        last edited by Feb 14, 2014, 4:06 PM

        ^ yeah you should only point to dns that has records for your local domain.  Pointing to others that don't is going to cause grief.

        "DNS info pointing towards both 8.8.8.8 and 192.168.1.1. "

        That is bad configuration, unless the 192.168.1.1 is not authoritative for any domain.  Also just putting pfsense or any just hostname is not good idea, names should always be fqdn, ie something like headphones.local.lan, or headphones.name.tld where your local dns is authoritative for name.tld

        You can setup your machines to have a search suffix, domain membership so when you put pfsense into your browser it queries for pfsense.yourdomain.tld

        But pointing to 8.8.8.8 as a possible dns - your never going to be 100% sure which dns your client is going to ask, if he asks 8.8.8.8 for pfsense.yourlocaldomain.tld its not going to work.

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.8, 24.11

        1 Reply Last reply Reply Quote 0
        3 out of 3
        • First post
          3/3
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
          This community forum collects and processes your personal information.
          consent.not_received