In general, this is yet another reason I use my own router behind the ISP supplied one. However as others has said: Yes, use your own DHCP and DNS server in conjunction.
@szaimen, @KarlF12: looked into this a little more and don’t think that is the issue. I can access my DNS URL on another port within my home WiFi to view my Plex site just fine. Also, I can view my admin login page on port 8443 through my DNS on my local network. However, when I go to my base DNS which usually brings up my Nextcloud page it doesn’t connect. If this was truly a network issue the other sites wouldn’t work. This still leads me to believe that it’s something in how Nextcloud is setup that is not allowing me to access that base DNS URL. Is there anything else I need to configure, I don’t think Pi-Hole and dnsmasq are needed, if they were… I wouldn’t be able to access Plex using my DNS URL like I can today. It must be something else…
I was just answering your question. What I gave you is the proper solution to it.
Put it in your computer’s hosts file and point it to your Nextcloud LAN IP. If that works then you need to implement the DNS fix. If not then you have some other problem.
1 Like
Put what in my computer’s hosts file? Point what to my Nextcloud LAN IP?
I don’t think I can do this given the configuration limitations of my router. It won’t let me change my primary DNS server.
How do you install bind on a Nextcloud server?
I still don’t understand… Why can I access https://my.dns.org:32400/ and https://my.dns.org:8008/ but not https://my.dns.org on my home network?
Okay… those are ALL questions about other advanced topics well outside the scope of Nextcloud. You’re going to have to do some reading and learning.
Try running: nslookup your.nextcloud.domain
If it returns a public IP instead of a LAN IP, then your router is doing what’s called hairpin routing, e.g. routing a packet from its LAN to WAN interface and then back in and applying NAT both ways. This can be prone to all sorts of trouble and really depends on whether the router does it all correctly.
Most firewalls don’t allow it by default, and as a general practice, I would never set one up that way on purpose. Running split horizon DNS resolves it by bypassing the router entirely and sending LAN connections directly to the LAN IP.
2 Likes
Excactly.
And in yout etc/hosts file (both linux and windows shares this file, so search for it. The /etc/hosts is the direct path in linux) add but do NOT, as in NEVER, delete the 127.0.0.1 pointer and leave everything eventually already in your hosts file as is. Just add as a new line:
192.168.0.2 my.dns.org
Save.
Swap above IP with the actual LAN IP of your nextcloud, and the Domain name your nextcloud url, without protocol or resource.
example:
dont:
https://my.cloud.org/apps/dashboard
do:
my.cloud.org
Yes, this returns my DNS name along with my public IP.
Won’t this just change it so that when I type my.dns.org it goes to my private IP? If I was able to get to Nextcloud on my private IP I wouldn’t be having this issue.
What does this entail? Is this something that I need to configure on my router? My Xfinity router doesn’t allow you to mess with things that much.
I’ve already explained what it does in fair detail. You’ll have to decide how to implement it if your router isn’t capable. It would involve running a DNS server of your choice on something else. Maybe this isn’t something you want to tackle, but it’s a common issue and common solution.
Honestly between this and other similar topics you’ve posted about weird access issues, I think your router may just not be up to the task.
2 Likes
Yes, for that particular device only. However if you brings that device with you and out of your LAN from time to time, your only option is a local DNS server with a local DHCP server.