ownCloud Routing
-
Do you see now how your boss injecting a non-goal as a requirement was going to cause problems? His goal should have been ease of use, instead of decided, without understanding, what the solution was going to be and because of that, it was never going to get fixed. We had to avoid his proximate solution so that we could arrive at the real one.
It's what is called "getting stuck in the weeds". It's very important to take stock and figure out the goal, then separate out what we might think is the solution and not get so mired down working on that that we forget what the actual goal is.
-
@alex.olynyk said:
@scottalanmiller cant get e-mail working
Okay, we can work on that next. That will be unrelated to the IP address issue.
What is email doing and not doing currently?
-
-
Again, you never setup email correctly.
First you had authentication enabled and SSL. But had told it to use port 25.
Now, it is very clear that it says that it cannot resolve the name.
-
Disabled auth
-
nslookup seems good...
nslookup mail.roseradiology.com Server: 127.0.1.1 Address: 127.0.1.1#53 Non-authoritative answer: mail.roseradiology.com canonical name = roseradiology.com. Name: roseradiology.com Address: 72.52.167.28 -
So my first guess is that DNS is not working on the ownCloud box and that's why it can't look it up.
-
Run the same command that I just ran from the ownCloud server and see what it returns.
-
-
@alex.olynyk said:
LOL, you have to add that in manually to your local DNS at each site because you are overriding the domain
-
Unless he added a wildcard to his local DNS it should still attempt to find stuff externally for items not listed locally.
-
Can you find anything by DNS on the owncloud box?
-
@JaredBusch said:
Unless he added a wildcard to his local DNS it should still attempt to find stuff externally for items not listed locally.
That's actually a really good idea...
To fix the mail lookup problem for mail.reoseradiology.com, just ad another A entry for mail.roseradiology.com to point to 72.52.167.28
Edit: If the IP is the same as www.roseradiology.com, you can just make it a CNAME and point mail.roseradiology.com to www.roseradiology.com
-
@dafyre said:
@JaredBusch said:
Unless he added a wildcard to his local DNS it should still attempt to find stuff externally for items not listed locally.
That's actually a really good idea...
To fix the mail lookup problem for mail.reoseradiology.com, just ad another A entry for mail.roseradiology.com to point to 72.52.167.28
Edit: If the IP is the same as www.roseradiology.com, you can just make it a CNAME and point mail.roseradiology.com to www.roseradiology.com
this worked. thank you
-
@JaredBusch I can ping google just fine from the owncloud box. Probably doesnt matter at this point cause adding the DNS entries works for a few minutes but then mail and the website stops working. My boss is putting the project on hold for a couple weeks until he can speak with the consultant.
-
@alex.olynyk said:
@JaredBusch I can ping google just fine from the owncloud box. Probably doesnt matter at this point cause adding the DNS entries works for a few minutes but then mail and the website stops working. My boss is putting the project on hold for a couple weeks until he can speak with the consultant.
Sure, as soon as you have it all figured out.
-
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?
-
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,
