Clayton wrote:
A few years ago I already gave up on using a dynamic ip even for a private server to tinker with. You are facing two problems with a dynamic ip:
- receiving: you have to rely on dyndns to switch fast enough to your current address AND rely on external clients not to cache the dns results too long.
I'm not having any problems at all with it for the webserver side. I've been using this for two years. External client caching has not (to my knowledge) been an issue at all. DynDNS takes care of the switching quite smoothly. I've tested several times right after an IP change and they've caught it right away.
That depends on the dns server that the client is using. Some dns servers from several big ISPs are caching rather aggressively in order to reduce the number of dns queries and they ignore the ttl settings of dyndns.
- sending: if you don't use your isp mailserver as relay you might as well stop here. Most mailservers do not accept mails from clients with dynamic ip. Additionally, your reverse dns record does not match your dyndns name.
Doesn't the Mail Relay take care of that issue? They provide the MX linking direct to my domain name. The actual IP is irrelevant - that is, they take care that my domain and IP match between my machine and them... upstream, from them to the internet... that info should.. as I understand it be relayed invisibly.... maybe time to read more on the DynDNS side of things... and ask them a few questions.
mx records are only for receiving mails. Without some facts I can't tell if the setup will work or not. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org