Tag Info

New answers tagged

0

Don't individually add each EC2 instance's IP address to your inbound security group. Instead allow inbound traffic from the security group of the EC2 instances. Then any EC2 instance which uses that security group will be permitted access from the same rule. Generally speaking, auto-scaling groups are best used behind Elastic Load Balancers if outside ...


2

This means that a new inbound rule needs to be applied to the security group for RDS that allows this new EC2 instance to connect to RDS via port 5432 (postgresql). Rather than using public IPs for your security group rules, I suggest using private IPs. Run both EC2 and RDS in the same VPC, then allow the entire VPC subnet IP range containing your ...


1

The @edvinas.me answer is correct. You must create a cloudfront distribution for your bucket. When you create the cloudfront distribution set the alternate Domain Names option to *.example.com. Then use the cloudfront url like d3lt3rsz2leycm.cloudfront.net. Now you can to add a wildcard subdomain like this: *.example.com. CNAME ...


1

First, use nslookup to query your name servers (listed in the Route53 management console when you select your zone) directly. You do it like this: nslookup my.query.com ns-????.awsdns-??.??? If this query doesn't give you the right results, the issue is between the AWS console and Amazon's servers, so you should contact them. If this looks OK (like I ...


0

Yes, as of Nov 2014 you can do this, here is how: http://neonos.net/white-labeled-dns-name-servers-on-amazon-route-53-with-delegation-sets/


1

This is possible, except surprisingly no one has made an article about it, even Amazon has not documented it well enough. See my answer here: http://serverfault.com/a/649714/56596


2

I have done this, please read my article before you actually do this here: http://neonos.net/wp-admin/post.php?post=30 The functionality has been programmed by Amazon in Nov 2014, however it has not been implemented in the web based console, hopefully they will do this soon. There is also no documentation or any articles that I could find on this topic. ...


0

Turns out that problem I was having was due to the fact that I deleted my original hosted zone and created a new one. Different name servers were used in the new hosted zone than were assigned to my domain. To fix the issue I had to assign the name server that were set when I created the new hosted zone to the domain. After a short wait everything started ...


0

It appears that I had some other errors in my starshine.org zone file which was causing my starshine.org name server to give me the SERVFAIL responses. I guess it was also giving cached responses from the secondaries and the errors weren't obvious in my logs. What did work was installing the nslint package (Debian) ... running it and walking over each ...


1

It looks like you're trying to set up a zone transfer which you can't do, as ChrisV said. To do a delegation for a sub domain you need only create NS records for the sub in the parent's zone. So in starshine.org's zonefile: aws IN NS ns-1494.awsdns-58.org. aws IN NS ns-773.awsdns-32.net. aws IN NS ns-1751.awsdns-26.co.uk. aws IN ...



Top 50 recent answers are included