Please remember to reply to the mailing list, not the original sender: http://gnudip2.sourceforge.net/#mailinglist
+++++++++ > (For example to have it only work for tinydns!! Seriously.). They should i take this personal? have there been others wanting to do so (cuz, it makes alot of sense)? > are of course free to take the code and do that if they wish, but > they will have to do it without me > > > 2. The semantics of the "secondary MX" button are > > unclear. When I first tried to use it, I expected that > > by entering a FQDN in the MX box and clicking on the > > secondary button, that the entered FQDN would be > > listed as the secondary MX. Instead, I went from > > this: > > > > host 300 IN MX 100 mx-main.example.com. > > > > To this: > > > > host 300 IN MX 200 mx-main.example.com. > > host 300 IN MX 100 mx-back.example.com. > > > > As you can see, the priorities in the MX records are > > reversed. > > Yes. There is a problem with the priorities. I am sure I had this > right to start with!!! > > I made a "fix" for this in the GUI that must have screwed it up. the tinydns backend gets this right... please inform me, when you change that -- GnuDIP Mailing List http://gnudip2.sourceforge.net/#mailinglist
