I make a web site to my local. I set bindings local.com and www.local.com. I add hosts xml to
127.0.0.1 local.com
127.0.0.1 www.local.com
So, I can connet on my pc like
local.com,
www.local.com,
192.168.1.35
But another pc on my network can't conenct with friendly name
www.local.com,
local.com,
But same pc can connet with ip
192.168.1.35
How can that another pc connect with friendly name ?
IP Addresses are the numerical identification for each device on a computer network.
Named Addresses invented, because remembering each device Address's turned to a difficult job.
So someone must know's which names must be converted to which IP Address.
DNS Servers are responsible to do this translation. But you done that locally. Actually you don't have a DNS Server on your local System, So you can't tell to others that "WWW.Something.COM" is my Address.
If you didn't connected to the internet, you must establish a DNS Server or done this task manually in all clients:
https://helpdeskgeek.com/networking/edit-hosts-file/
Running a DNS Server is another task. you can search for DNS Server applications like https://simpledns.com/ or you can setup a DNS Server using Windows Server. for both scenarios you need to tell to your clients to add your DNS Server Address to their network Adapter settings.
or If you are connected to the Internet, you can Use a NoIP to register a free Address:
https://www.noip.com/
you then need to download an application (In Noip.com) to monitor IP changes, it will monitors your IP address and it changes and then tells to NOIP.com to translate your address into your current IP address.
Actually NOIP will registers your address globally around the Internet network and each one who can access to the internet is able to reach to your address.
Related
I've created a node.js app. When it runs my mobile phone can connect to it using address 192.168.1.5. In other words, when I open a browser on my phone and enter 192.168.1.5 I get a welcome page served by the app running on my PC.
The problem is that the IP address is not human friendly. Is there a way to access my app by an alias? For example, http://myapp or something like this?
Yes, these aliases are provided by the domain name service (DNS). You need to set up a hostname on DNS to point to your machine's local address.
Put that IP address into a DNS server.
Here's a free way to do that.
Create a FreeDNS account by visiting https://freedns.afraid.org/
Click on Subdomains.
Click the Add link.
Create a subdomain hostname under one of FreeDNS's public domains. Maybe mydev.manidos.mooo.com is a good choice
Put your machine's IP address into it.
Then, use https://mydev.manidos.mooo.com to hit your development machine's nodejs app.
You can pay FreeDNS to register your own domain name and use that if you prefer.
There are all sorts of other ways to register a domain and then add address records to it, to translate from hostnames to IP addresses.
Edit If you were connecting to and from your desktop / laptop machine, you could add a hostname to your hosts file. The hosts file is itself a little DNS registry that's local to your machine. On windows it's at C:\Windows\System32\drivers\etc\hosts. On *nix and mac it's at /etc/hosts.
But, you are connecting to your app from a mobile device. Editing the hosts file in a mobile device is unreasonably difficult.
I have setup GitHub enterprise in a server for on-premise usage. There it is having a private IP and has to be configured a hostname. It is showing
"Ensure this domain is routable on your network."
If I map the hostname with IP address and add to my windows hosts file, then it's fine.
But I want a solution so that any people connecting to the office network has it resolved automatically without a manual entry in their host file.
If you have enough users of your GitHub Enterprise Server that maintaining the hosts files is a pain, I'd suggest this happens when you have more than 10 users, then you will need to look at a DNS server for your Office Network. If you do not already have one then there are many options open to you depending on what your network looks like.
The other day I was trying to RDC from my work laptop to work desktop using my PC's hostname but it could find the desktop. Later on I tried with my desktop's IP which worked. Both the time I was on premise and was connected to the network physically.
I could RDC every other computer in our network.
After my research, I checked firewall was disabled, flushed and re-registered dns etc. Everything seems to be in order. However, when I tried to do reverse DNS lookup it didnt work for my desktop.
After that my IT guy and I checked everything on the AD server and there was no entry for my hostname or the IP. So we manually added the dns record which didnt work either.
Following is the note from IT:
AD / DHCP on a server on a different subnet DNS on another server on
the above subnet
The Pc is on a VLAN again different subnet. The Cisco Switch controls
the VLAN but talks to DHCP server for scope
Even adding the A host on forward lookup manually can’t resolve using
hostname for ping / mstsc. Both work for IP so deff DNS issue.
Tried to ipconfig /release and renew after giving a different PC the
IP address that was originally assigned to this one thinking it would
force DNS to update.
There is no entry for the IP or the Hostname in DNS even when the IP
changed after a renew. The firewall on the PC is off. However there is
the entry in the DHCP address lease table.
Tried flushDNS and ReregisterDNS.
If anyone could point me to the right direction here I would be grateful. Also, if you need further information please let me know.
Thanks
This is not the correct forum for this question. However, I can point you in the right direction.
Your correct that this is a DNS issue (so it seems).
The entry that is missing is from the host you are trying to reach (not the client that your trying this from).
Make sure all of the systems are using the same DNS servers. Make sure the DHCP Client Service is running (even if IP address is hard coded) as that is what actually records the the host name and IP address in DNS.
It sounds like you have the routing set up or you would not be able to do it by IP address.
Is the DNS zone in AD set up to allow dynamic updates? Do you have the domain name being sent out via DHCP?
Windows will (but not always) try to find a host by DNS and will fall back to a broadcast for the PC name. This might be why it works from one VLAN, and not from another.
I created a IIS site in my windows server 2012 virtual machine. I want to be able to access it online on my android phone. I can access it locally on the server. The ip address of the server is 199.86.19.2 and for the IIS site its 192.168.113.133. Also the server is a dynamic ip. I have tried using an online site called noip.com to make a domain. I created a domain
mydomain.no-ip.biz and gave it the ip address 192.168.113.133. I even installed the client program so it keeps my ip up to date. However when I visit mydomain.no-ip.biz. it says it cannot be found.
Does anyone know what is wrong here?
Thanks.
192.168.113.133 is your local IP address on your network. 199.86.19.2 is your external IP address that your IPS assigned to your server (until it expires). I'm assuming you are doing this at home so you would need to make sure if you have a router, you need to configure it to set it up to port forward to your local IP address.
Set your 'mydomain.no-ip.biz' ip address to 199.86.19.2 and make sure your router (if you have one) is forwarding to 192.168.113.133.
We are installing a security camera system in our company which comes with a DVR that hosts a website on which you can view the cameras via the web.
I have setup the DVR with a static IP of 192.168.120.199 on our network and can view the website while on our network (either when at work or logged in via VPN). The camera DVR uses port 80 for viewing the webpage and port 9000 for Media Port.
We use GoDaddy to host our DNS info and I have added an Host(A) record of 'cameras' that points to the address of our server. I have also added a forward lookup Host(A) to our domain's DNS manager of 'cameras' that points to 192.168.120.199. When I use the address 'cameras.mysite.com' within our domain the website displays properly, but when I try the same address from outside our domain (ie, at home) it displays the default IIS 7 page (from our domain server).
Two questions about this setup:
Why does the forward lookup work when inside our domain but not outside (why does it go to the IIS default page when outside the network)?
How do I get this to forward correctly if not via the forward lookup host?
Because internally you're looking it up on your internal DNS server and you get the right 192.168.x.x machine. When you look it up externally GoDaddy is giving you back the 192.168.x.x, but that's not a publicly routable IP, so doesn't go anywhere. If you really want to be able to connect to your security cameras from outside your facility then I suggest setting up a VPN for security reasons. But if you want GoDaddy to directly route to your internal machine from the public internet then you'll have to give it a publicly routable IP.
As a further note on that - 10.x.x.x, 192.168.x.x and 172.16-31.255.255 are not publicly routable. They're called private IP blocks.