Thasaidon wrote:In my mailserver I used the mydomain.no-ip.org domain, and I now use my new mydomain.com
I was just wondering if I should use mail.mydomain.com too.
Thasaidon wrote:However, I have a fixed ip, so I manually "activate" my domains each month.
The dyndns client in the 04x series is compliant with the dyndns requirements and will not let a domain expire due to lack of an update or get you marked for abuse due to to many updates. You do however have to enable a cron job for dyndns to accomplish this with a semi-static or static IP. Then it is completely automatic with no manual updates needed.Dyndns will disable static accounts UNLESS they are updated within:
not less than 26 days, and
not more than 30 days.
And they mean it; on their forum are several comments from customers who have been 'caught out' by this. To be fair, they also give examples of dyn DNS clients which can be set for 'periodic' updates; I have not (yet) checked whether the FREESCO client can do this. (It may not matter, anyway; we could run the client they recommend on one of our Linux machines behind FREESCO, and thus keep dyndns happy.)
Island wrote:My guess is that you already knew this - all this - so the only thing I would say is that as I understand it (from the dyndns help files) the RFCs do NOT require that the MX record is a separate name or a separate address. Indeed, they seem to suggest the MX record can be blank (though I have also seen comment that many organisations will - wrongly - reject mail from such domains).
Thasaidon wrote:All my domains and MX record point to the same public IP
Users browsing this forum: No registered users and 1 guest