ownCloud Routing
-
could it be the A record i created on my public DNS?
-
@alex.olynyk said:
If i deleted the DNS entries and zone I created, flushed DNS on the server and workstations, rebooted computers, but some computers still cant get to mail or the website
what else can i check to see where the issue lay?
Why did you do that?
-
@alex.olynyk said:
could it be the A record i created on my public DNS?
Only if it is an incorrect one,
-
@scottalanmiller mail and website stopped working, boss told me to undo what i did, is there an easy way to rebuild DNS on a DC?
-
@scottalanmiller said:
@alex.olynyk said:
If i deleted the DNS entries and zone I created, flushed DNS on the server and workstations, rebooted computers, but some computers still cant get to mail or the website
what else can i check to see where the issue lay?
Why did you do that?
Because he has no idea what he is doing. His boss obviously is exacerbating things.
Their entire network setup sounds like a cobbled together mess. He has mentioned wanting to merge domains and such, but that is really not the problem. Many companies have multiple domains and have no issues.
The problem is that this is not being properly managed. Likely it was never managed and just continually had random fires put out with cobbled together fixes that resolved the symptom but not the problem.
-
@alex.olynyk said:
@scottalanmiller mail and website stopped working, boss told me to undo what i did, is there an easy way to rebuild DNS on a DC?
And instead of thinking about the cause of the problem, you simply started deleting things?
You just completely reinforced the entire point of my last post.
-
@alex.olynyk said:
@scottalanmiller mail and website stopped working, boss told me to undo what i did, is there an easy way to rebuild DNS on a DC?
They stopped working because they weren't entered into the DNS properly?
No, there isn't an automatic build/rebuild DNS function.
-
@alex.olynyk said:
boss told me to undo what i did, is there an easy way to rebuild DNS on a DC?
Same person who screwed things up getting us here. I think the weak link has been found.
-
@dafyre said:
Oy... this will be fun to fix...
At each site, you will have to set up a DNS Forward lookup zone... for roseradiology.com
You will have 3 entries under neath it.
The . and the www entries (A Records) should point to the Public IP address of the roseradiology.com web site.
Then make a new entry called owncloud and set it to the internal IP address of your owncloud instance.
this is how i entered it
-
You need to remove the entire lookup zone to back it out.
-
I wonder why the web site & email quit working. That is strange. However, @scottalanmiller is right. If you remove the whole roseradiology.com from your Windows DNS, it will fix the problem, and return owncloud to a non-working state.
-
@dafyre said:
I wonder why the web site & email quit working.
If they had just done the first step of troubleshooting, we'd have known and have had this fixed in a split second.
-
Usually when I am just creating a couple of hosts to redirect internally like this I create a forward lookup zone for the whole host. e.g. i create ownlcoud.external.tld forwardzone then make the @ record the internal host. That way everything for just host.external.tld still uses the public records
-
would it help if i created the DNS FLZ and 3 entries again and posting the output of nslookup again for mail.roseradiology.com and roseradiology.com
-
Your email was likely a simple autodiscover record. The website also, a simple A record.
What you were told is not some magic formula. DNS is a really basic thing.
You want to see how easy?
Here is a site with email hosted on Office 365 (i.e. external). Their domain is a standard .local and they even have ownCloud. Everything works perfectly.
Internal DNS for domain.local
Internal DNS for domain.com
External DNS for domain.com
-
@alex.olynyk said:
would it help if i created the DNS FLZ and 3 entries again and posting the output of nslookup again for mail.roseradiology.com and roseradiology.com
figures its a medical place. they always have the worst security.
-
@brianlittlejohn said:
Usually when I am just creating a couple of hosts to redirect internally like this I create a forward lookup zone for the whole host. e.g. i create ownlcoud.external.tld forwardzone then make the @ record the internal host. That way everything for just host.external.tld still uses the public records
That's brilliant! Wish I had thought of that a long time ago!
-
@dafyre said:
@brianlittlejohn said:
Usually when I am just creating a couple of hosts to redirect internally like this I create a forward lookup zone for the whole host. e.g. i create ownlcoud.external.tld forwardzone then make the @ record the internal host. That way everything for just host.external.tld still uses the public records
That's brilliant! Wish I had thought of that a long time ago!
I do not do this because it is just as easy to correctly setup the domain.com and then I can continue to use new subdomains without added an entire lookup zone.
Both ways easily work though.
-
Those are both interesting approaches - and they also both allow for the fastest local connections.
I would have considered doing this with a DMZ and making all the traffic flow through the firewall - but then I'm most likely reducing my connection speed to whatever the firewall can handle.
But it has the advantage that all remote hosts use the same IP to get there. -
is there a way to notify a new user that we have created an OC account for them?
