I have a device that have the configuration page. I setup port forwarding in the router. It works fine when access from outside via public IP so I map that public IP to a DynDNS url. Sweet! easy access for our customer.
However within the building it cant be accessed via the DynDNS url or its public IP. I google it and see the problem is at NAT loopback but the router doesnt have NAT loopback setting? Is there other way that I can setup to access the device by a DynDNS url no matter my customer is inside or outside of the LAN? Just to keep thing simple for our customer.
Thanks very much for any suggestion!
The address is (hopefully) static inside the subnet. I would configure a caching DNS server in the subnet to return the internal IP and then forward any other DNS requests out to whatever DNS server they use (probably the ISP).
EDIT: research BIND views
It sounds like the easiest config would be build a caching DNS server with internal and external views.
Related
I've bought a .com domain from a provider on the internet. But, I want to host it locally.
I know that I can host a local web by using XAMPP or WAMP, but I want to make it accessible on the internet.
I also know that we could host a web to be accessible on the internet like ngrok, serveo, etc.
But, I want it with my .com domain that I bought. Could this possible? How to? Is there any references?
Thanks in advance ^_^
It seems to me you are asking 1. if it is possible to map a DNS entry such that traffic to the URL would be directed to a server in your personal network, and 2. if it is possible, how to do it.
The answer to the first question is yes, it is possible. The second question is difficult to answer because it depends on many factors such as your ISP, country, your web host provider's rules and services, etc.
First, you must determine two IP addresses:
The public IP address for your network (whatismyip.com)
The private IP address of the local machine which will host your website (typically (192.168.0.x)
Then, you must enable port forwarding in your router configuration, such that any requests to port 80 and/or port 443 on the external interface (public) will be forwarded to the internal port on which your website is hosted. If done properly, putting the public IP in your browser will take you to the website you are hosting locally.
Once you verify access via public IP, then you must go into your DNS entries on your domain host and create a CNAME record which points your root domain (www.yourwebsite.com) to your public IP address. That will route all traffic to your .com to your local server.
I do NOT recommend doing this however, and would caution against it, because it leaves your local server/network open to the public, and makes your domain vulnerable to things such as spoofing etc. To do it properly, you should obtain a security certificate for your domain through a Certificate Authority (CA) - generally, you can request a certificate via your domain hosting service. Once you have a certificate, you must upload the key to your server and configure your web application/hosting service to use the certificate, and then change your port forwarding to use 443 instead.
This is a very complex topic that takes time to learn, and your question is extremely non-specific. There is no good place to start really, and no shortage of information/resources available online. To start, you need to understand how your DNS works. For any local webhosting, port forwarding is important to learn. You should also determine if your ISP blocks the forwarding of certain external ports, which effectively disables any private webhosting.
I'm attempting to create a server using IIS.
I created a site. Configured the firewall. It's available in the browser as localhost(http://localhost:8555/) and static IP(http://10.12.66.79:8555/) too
But from another network like my phone. I tried accessing using the static IP but it failed. then I tried using the virtual IP then it show me the login page of my service provider.
what I can do next?
Hope you grab a computer networking book some time to study the basic concepts.
10...* is a private address your ISP gives to your server,
https://en.wikipedia.org/wiki/IP_address#Private_addresses
So that this server can be accessed by other devices on the same network.
Your phone is on another network (via Internet in most cases), so it won't be able to access your server.
To pass packets between two networks, many other devices and settings are required.
If you do want to do experiments, public cloud computing platforms are far better an option, as they can give your server public IP addresses that can be accessed anywhere.
you can change the mobile's default DNS to your system's(IIS) IP may be this could help you but it can be able to run locally only. Make sure that your site is working in your system through the static IP (http://10.12.66.79:8555/) if it is working properly then this could be the only problem change the DNS.
I am able to access my website via the domain name outside of the network.
On the internal network I am able to access the site via "localhost/websiteName/", "internalIP/websiteName", and "computerName/websiteName", but I am unable to hit either "http://example.com" or "http://www.example.com".
I was able to get it to work on a computer by adding the ip and website to the hosts file, but I am still unable to access the website using the domain via mobile devices on the internal WiFi.
I completely disabled the firewall, so I know that that is not the problem.
I have bindings set up for www and without www with all IP Adresses unassigned.
I did try adding a binding for both www and not, using the internal and external IP addresses, both IPv4 and IPv6.
I am running this on http without any certificates.
I have a cname record for www
My # record is pointing to my external, static IP
The website is set up separately from the default website and it is not a virtual directory.
I am using Comcast Business with their Cisco DPC3939B router.
This is initial setup of the website, and it is not an issue that just started after having worked previously.
I figured it out. All I did was add an # record to the DNS to resolve the website to the internal IP. Here is a really great reference for accessing websites on a Local Network: devside.net
i need to point from my hosting account to my local server
so i thought the best way is to do it using a subdomain
though the issue is that i cant figure which is the right way to do it
using same DNS as my domain / leaving it blank
using my internet isp dns maybe ?
what is the right way to point a subdomain to a static ip of my isp internet account at home ?
You don't need a subdomain, you need an A record (address). You could set up a subdomain, and then use an A record within that, so, if your domain is example.com:
Your domain is set up as example.com, your public web server A record might be www.example.com. You could then set up your home server A record as homeserver.example.com
A sub domain might be 'home.example.com`, and a server in the sub domain will have an A record of myserver.home.example.com.
In all these cases the IP address of your A record should be the IP address of the network side (external side) of your home internet router. If the address is static this will work, but if it's not you'll need to subscribe to a DNS service that supports Dynamic DNS, and that's a whole different story.
How you go about setting all this up is ISP-dependent.
Note that the external address of your network will not match the internal address of your server, so you'll need to set up port-mapping on the router to allow inbound traffic to reach your server.
..and lastly, do you really want to risk opening up your home network to the ravages of the public internet? Do this only if you really know what you're doing, and possibly not even then.
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.