I was trying to redirect my domain to a raspberry which is running in my local network.
I do not have static ip but i am trying it through dynamic ip.
These are the steps i have done
I have purchased a domain from google domain.
Created synthetic records as suggested by google (followed their article)
I have used ddClient on raspberry to point my local ip to the dns (as suggested by google -https://support.google.com/domains/answer/6147083?hl=en)
I have created a sample node js app on my raspberry and which i could access it from local network.
I have also ensured domain is configured correctly by contacting google support over chat.
I have a bsnl router (which is wired) and i connected that to a wireless router to which my raspberry is now networked
I tried to do port forwarding but i am confused. I am unable to understand where should i actually port forward?, should i be doing at BSNL or the wifi router. Infact i tried it in both, but still my issue is i can't access the app over internet via my domain.
Please help
Sanjay BSNL provides the Static IP with cheap prices ,
Once You get a Static IP from bsnl do port forwarding with that static ip
Related
I have my own servers and have hosted a few services (game servers, web servers, ...), and use to host these on a publicly accessible dynamic IP using DuckDNS.
I have recently moved to a rural area and use a satellite service for my internet that does not support publicly accessible IP address.
I would really like to host these things again, but the only way I can think of doing that, is to have an IP somewhere in the cloud and route that back into my network. I have been messing around in Azure but I can't seem to get what I want working. I am not stuck on Azure, just happens to be the one I am message about with.
I have pfSense as my router, so I can setup a VPN client on that and pretty much keep that alive indefinitely, so here is what I am thinking and I hope someone can point my in the right direction, or if you like, poke holes in the idea.
I configure a VPN client on pfSense to be an WAN interface
create a VPN gateway in the cloud
connect pfSense VPN client to the VPN gateway
create a static external IP in the cloud
route traffic from the external ip through the VPN back to my pfSense server and into my internal network
once I get the traffic coming into pfSense , I can route to computers / VMs on my internal network.
This way, I do not need a publicly accessible IP from my ISP, I can connect to the Azure and use its external IP and route back through the VPN to my internal network.
If this was real hardware, I would have had this built in 30 minutes, seems this virtual world is messing me up.
Any ideas on how to configure this or maybe another solution?
I am struggling with the whole Azure setup and have watch hours of videos about each of the bit in Azure, but I am lacking some key bits of knowledge to bring this together.
If you know what you are doing with pfSense...
cloudfanatic.net
$2.99 US a month for a VPS running pfSense. They will spin up a VPS with pfSense on it at no extra charge. Open an account, send support an email.
Gives you a static permanent IP. Shared 1GB Internet link. No data limits. I see between 150 and 500Mbps. Perfectly fine for what I use it for.
Wireguard on that pfSense, people connect in, etc...
I've been using it for about 6+ months. Been very impressed.
Chunky
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 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.
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
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.