Question about DNS
-
I am aware of this, I want it to be internal only for the time being, but still use the domain files.gemequipment.com
-
If i do this, does gemequipment.com still resolve to the external site?
-
@Donahue said in Question about DNS:
If i do this, does gemequipment.com still resolve to the external site?
It would as it's a different fqdn.
-
And file.gemequipment.com would point to your internal Nextcloud installation.
-
@Donahue said in Question about DNS:
I am aware of this, I want it to be internal only for the time being, but still use the domain files.gemequipment.com
Then yes, you can do it.
-
@Donahue said in Question about DNS:
If i do this, does gemequipment.com still resolve to the external site?
Not unless you set that up manually. Once you take over the domain and overlay your own stuff onto it, that's it. You have to do everything manually.
-
@DustinB3403 said in Question about DNS:
@Donahue said in Question about DNS:
If i do this, does gemequipment.com still resolve to the external site?
It would as it's a different fqdn.
But it would not continue to do so. It would need to again, as he would be filing an SOA for that domain internally. So the existing DNS infrastructure, the public one, would no longer be usable for it.
-
@scottalanmiller said in Question about DNS:
@DustinB3403 said in Question about DNS:
@Donahue said in Question about DNS:
If i do this, does gemequipment.com still resolve to the external site?
It would as it's a different fqdn.
But it would not continue to do so. It would need to again, as he would be filing an SOA for that domain internally. So the existing DNS infrastructure, the public one, would no longer be usable for it.
Exactly.
Basically - if you do this - you'll need/want to duplicate all of the current records on the DNS server.
Why would you want to do this on your external domainname if not for external use?
Just setup file.ad-domain.com and point the users there.
-
Dash is correct, there isn't really a reason to desire to do this. It'll be a mess. The one reason that normally exists for this is external access, not internal. Doing it for internal users doesn't really make any sense.
-
Do you or do you not already have domain.com in your local DNS?
-
@JaredBusch said in Question about DNS:
Do you or do you not already have domain.com in your local DNS?
no.
and to answer the other questions, I do want to have this external at some point, but maybe I am going about this the wrong way.
-
@Donahue said in Question about DNS:
Our external web domain is gemequipment.com. That site is hosted somewhere else, and ATM I have nothing to do with it. Can I do something with internal DNS to point files.gemequipment.com to an internal server, specifically a nextcloud instance? I am still using AD DNS.
What's your internal DNS domain name?
If you can get access to your external DNS, you can set an internal IP there. It'll only work if that IP address is reachable from the users' computer, and the public will know the internal IP of that hostname...
-
internal domain is gem.local. I want to eventually setup all of this for external access, but at the moment, we have zero external facing services, this would probably be the first.
-
@Donahue said in Question about DNS:
internal domain is gem.local. I want to eventually setup all of this for external access, but at the moment, we have zero external facing services, this would probably be the first.
You can do both.
Nextcloud is not tied to a single domain name. you simply put both in the config file.
So for now, set it up as files.domain.local in your internal DNS.
-
Then there's no reason to make files.gemequipment.com. Just stick with files.gem.local until you're ready to make that public. Then once you make it public, you can get whoever controls your external DNS to add files along with it's public IP.
