Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm about to configure a dns server in order to get rid of amazon mail sending limits. As private ip's are dynamic, how can i associate host+FQDN with a private ip and make sure the association is always valid although ip's get changed in a lapsus of time. Should the dns server get notificated every time the ip gets changed? And how? Thanks in advanced!

PD: I think using elastic IPs is not a valid solution as AMIs comunicate each other through dynamic private IPs.

share|improve this question

migrated from Aug 12 '11 at 1:41

This question came from our site for professional and enthusiast programmers.

On the AWS network, the public DNS for an amazon elastic IP resolves internally, so you won't be charged for bandwidth since your request won't leave the network. You will be able to assign the same elastic IP to a new server if you need to, and you won't have to change the software that points to the public DNS for the elastic IP since it will resolve appropriately. Knowing this is way it works is this still not a valid solution?

Either way, sending email from an AWS instance is not a good idea. Since many spammers use AWS for spam, most of the AWS public IPs are blacklisted and your emails will never get through. We use DynDNS's Dyn Standard SMTP and haven't had any issues with emails not going through.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.