New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to switch between 'DNAME' and 'FULL' clones #169

Closed
mdklapwijk opened this Issue Jan 8, 2015 · 5 comments

Comments

Projects
None yet
2 participants
@mdklapwijk

mdklapwijk commented Jan 8, 2015

Currently fmDNS creates a zone with a DNAME record for each clone of a domain. This is not always desirable, because for example you're not able to receive email on those clones (CNAME/DNAME in MX is NO!).

The functionality I'm looking for is to be able to set a global mode to (dis)allow the use of DNAME for cloning. And furthermore the ability to override this behaviour on a per clone basis.

I think a lot of the core functionality (FULL/DNAME output) is already in place, since the code already switches to FULL-output once you add a MX record to the clone...

@mdklapwijk

This comment has been minimized.

mdklapwijk commented Jan 8, 2015

P.S. At this moment as a workaround I add an A record 'clone' to the clones so it generates a full config for the clone.

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Jan 8, 2015

Interesting point and thank you for bringing it up. I'll look into how this could be down by adding a checkbox to the fmDNS settings page and then another one in the zone config page. I should be able to get this out with 2.0.

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Jan 10, 2015

Aside from mx records, what other scenarios would somebody not want to use a dname? I can't think of any and perhaps just checking for defined mx records and if they exist then don't use a dname otherwise use a dname.

@mdklapwijk

This comment has been minimized.

mdklapwijk commented Jan 10, 2015

Automatic checking would be a nice feature, but would result in almost never using DNAME. In most situations you (read I) want to receive email on the main TLD and the county TLDs the company is active in (or only home country TLD). So all other country TLDs which are only used for redirection to the main TLD would be perfectly fine as a DNAME.

Here is an (really old) piece on another reason not to use DNAME:

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Jan 15, 2015

A global setting and a per-zone override are now available to allow/disallow automatic DNAME usage for cloned zones. This will be available in 2.0-beta1 and later.

@WillyXJ WillyXJ closed this Jan 15, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment