search

mail-in-a-box / mailinabox

Mail-in-a-Box helps individuals take back control of their email by defining a one-click, easy-to-deploy SMTP+everything else server: a mail server in a box.
https://mailinabox.email/
Creative Commons Zero v1.0 Universal
13.98k stars 1.44k forks source link

Add a checkbox for external DNS usage. #404

Open cooperaj opened 9 years ago

cooperaj commented 9 years ago

Adding a checkbox to the external DNS page that says "Yes I've done this" or something of that ilk would mean that you could squash the error/warning messages on the status page.

apeman76 commented 9 years ago

Would love to see this aswell

itslukej commented 8 years ago

Would like to see this, I mainly use mailinabox for the mail itself.. not the dns. Perhaps a option when adding the domain to use the nameservers/dns?

bronson commented 8 years ago

I don't quite see the point to this... The first day you set up your external DNS, sure, you get a bunch of warnings. After that, it should be quiet, no?

(unless you're changing your settings a lot, which seems weird)

itslukej commented 8 years ago

@bronson: Some of us don't use mailinabox for the external DNS

bronson commented 8 years ago

@itslukej I hear it, that's why I'm trying to fix #649.

I'm just trying to understand what happens without this checkbox. It seems like you get one email with a bunch of warnings that you can ignore, then things are quiet? Or is it worse than that?

cooperaj commented 8 years ago

No, it's more that when using external dns, every visit to the status page tells you you've configured everything wrong and it's all broken. Therefore masking anything that might actually be broken since you ignore it all.

A tick box to turn off those checks would make the status page a while lot more meaningful.

On Sat, 1 Oct 2016, 16:12 Scott Bronson, notifications@github.com wrote:

@itslukej https://github.com/itslukej I hear it, that's why I'm trying to fix #649 https://github.com/mail-in-a-box/mailinabox/issues/649.

I'm just trying to understand what happens without this checkbox. It seems like you get one email with a bunch of warnings that you can ignore, then things are quiet? Or is it worse than that?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/mail-in-a-box/mailinabox/issues/404#issuecomment-250917412, or mute the thread https://github.com/notifications/unsubscribe-auth/AAYbUhC46oi90w_xzzT7xS3Texa58mZkks5qvnhugaJpZM4EjbPw .

bronson commented 8 years ago

It's mostly warnings, isn't it? At least, it is on my page, but no doubt we have different configurations.

Personally, I don't mind the warnings because they're mostly correct -- yes it WOULD be better if I added the DKIM keys. :) I would not be happy to see a page full of errors of course.

Just trying to picture how this issue would be implemented... What would this checkbox do? Silence all DNS-related errors, or just some of them? Silence the warnings too? Maybe it would just prevent DNS checks from being performed at all?

itslukej commented 8 years ago

687 Might be a good fix for this, allowing you to select if you want to use DNS with each domain.

bronson commented 8 years ago

I'd like to fix this but I still don't see what the checkbox should do. Prevent all DNS status checks from being run? Or just prevent any status check that emits an error? And maybe suppress status checks that result in warnings as well?

biermeester commented 8 years ago

I'm using an external DNS server, and I see the following 'errors' that are not errors:

For my Miab server: box.{mydomain}.{tld}

✖ The DNSSEC 'DS' record for {mydomain}.{tld} is incorrect. See further details below.

? Nameserver glue records (ns1.box.{mydomain}.{tld} and ns2.box.{mydomain}.{tld}) should be configured at your domain name registrar as having the IP address of this box ({box ip address}). They currently report addresses of [Not Set]/[Not Set]. If you have set up External DNS, this may be OK.

For every other domain that my box is handling email for:

{somedomain}.{tld}

✖ This domain's DNSSEC DS record is incorrect. The chain of trust is broken between the public DNS system and this machine's DNS server. It may take several hours for public DNS to update after a change. If you did not recently make a change, you must resolve this immediately by following the instructions provided by your domain name registrar and provide to them this information:

✖ The nameservers set on this domain are incorrect. They are currently {external DNS1}; {external DNS2}; {external DNS3}. Use your domain name registrar's control panel to set the nameservers to ns1.box.{mydomain}.{tld}; ns2.box.{mydomain}.{tld}.

✖ This domain should resolve to your box's IP address (A {box ip address}) if you would like the box to serve webmail or a website on this domain. The domain currently resolves to {some ip address} in public DNS. It may take several hours for public DNS to update after a change. This problem may result from other issues listed here.

www.{somedomain}.{tld}

✖ This domain should resolve to your box's IP address (A {box ip address}) if you would like the box to serve webmail or a website on this domain. The domain currently resolves to {some ip address} in public DNS. It may take several hours for public DNS to update after a change. This problem may result from other issues listed here.

Those last two 'errors' are not really the result of using an external DNS server, of course. But I would not really consider them errors either.

Anyway, these are the 'errors' I think we could do without when explicitly opting for an external DNS server.

hraban commented 6 years ago

In addition, mailinabox doesn't detect external DNSSEC properly. I've set it up through cloudflare and my registrar; external DNSSEC validation tools say it's OK, but miab says the config is wrong. It expects its own keys in there, apparently.

It adds noise to the status page, which obscures real errors.

(see also #615)

stsievert commented 3 years ago

:+1: I'm a new MIAB user, and am ignorant on DNS. I had to set up MIAB with external DNS because my personal website is setup through gitlab pages. It took me a couple hours to use DNSSEC with MIAB. Specifically, I took these steps:

  1. I enabled DNSSEC through Cloudflare, but then canceled it after a couple hours because the warning message said "resolve this issue immediately".
  2. This weekend, I decided to sit down and figure it out. I eventually filed an issue on Cloudflare's community forum asking how to use the DS record MIAB recommends with Cloudflare's DNSSEC (https://community.cloudflare.com/t/adding-ds-record-to-cloudflare-domain/242500).
  3. Their response is the only reason I'm okay with the red check mark about DNSSEC on the status check page.

Customizing the status page warnings for an external DNS would have saved me a couple hours this weekend.