Can't see internally hosted website when inside the network
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Can't see internally hosted website when inside the network
Hello there.
I am creating podcasts that I like to download to my android phone. I host the podcasts on my home webserver and use dyndns for the website when outside the network. However, when I type in my dyndns website from inside my network, it will not work.
I realize i can use the ip address to get to the site, but since I use beyondpod for my podcasts, it's all saved in settings. So what i'd like to be able to do is download the podcasts to my phone from either inside or outside the network.
Being a network kinda guy the first thing that comes to my mind is load up a linux machine and install dnsmasq, and have it do DNS services for the internal network only, and resolve the dynamic address to the server with the podcasts. As a bonus, you can have it provide dns services for any and all fixed IP nodes in your network, and cache all external DNS requests to speed up all of your internet activity.
Even to me that sounds like a lot for a newby to take on. Anyone have a more 'simple to implement' answer?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.