First off, the zone editing capabilities are a bit limited. For example, it’s not possible to add an MX record for another host such as
somehost.domain.tld. IN A 1.2.3.4
somehost.domain.tld. IN MX somehost
Not necessarily something that is common to need to do, but there’s really no reason I shouldn’t be able to add that.
It’d also be nice if there were TXT records for SPF in the default zone templates, or at least the capability of editing the default template.
For example, say I wanted to have in my default zone a backup MX at weight 50 for another server, to service backup MX for all domains configured on a box. Or perhaps I wanted a lower weight MX to function as a mail filtering gateway… There are a lot of things that would be handily accomplished by some increased flexability with the DNS system.
[QUOTE=nbright;10212]First off, the zone editing capabilities are a bit limited. For example, it’s not possible to add an MX record for another host such as
somehost.domain.tld. IN A 1.2.3.4
somehost.domain.tld. IN MX somehost
Not necessarily something that is common to need to do, but there’s really no reason I shouldn’t be able to add that.[/quote]
I’m not actually sure what you mean here. I just tried this on one of our boxes running InterWorx 2.1.3, and I did the following:
3.) Also, I tried adding an MX record to a completely different domain: mail.otherdom.com MX 20
All 3 steps worked fine. If that’s not what you’re trying to do, could you give us some more information about what you did and what error message you got?
You’ll be happy to know that DNS templates are in v.3.0. We allow for one DNS template per reseller, plus one DNS template for the master NodeWorx user (i.e., for accounts not under a reseller). Oh, and SPF and SRV record types were added too.
