In AWS Route 53 (DNS service) I choose A Record TYPE and then select “alias”, which allows me to paste the following into the VALUE field:
dualstack.2016-fwla-webserver-loadbalance-529850135.us-west-1.elb.amazonaws.com.
I suppose this is similar to CNAME, but how should I do this since I am moving the route53 dns stuff to MIAB DNS??
so i figured out this part about CNAME. But it seems that the box isn’t updating records correctly. I even restarted the nsd service and checked the box.fwla.com.txt & box.fwla.com.txt.signed files as well as the zones directory.
Everything seems fine but when I run dig (even after clearing dns) it doesn’t update. the first time I added the CNAME I omitted the trailing DOT (.)
when i ran dig it added fwla.com at the end of CNAME value.
so, i added the trailing DOT in CNAME as shown below, I checked the zone files and they were updated but dig and other checks showed no update. in addition, when I run localhost dig, it returns No Such Domain (NXDOMAIN).
Please help. this box worked when I used AWS Route53.
www.fwla.com CNAME 2016-fwla-webserver-loadbalance-529850135.us-west-1.elb.amazonaws.com. [delete]
fwla.com CNAME www.fwla.com. [delete]
*.fwla.com CNAME www.fwla.com. [delete]
[solved]
So, it turns out that you MUST delete the CNAME record with the error before adding the fixed CNAME record if they are similar/same or the dns_update.py file will ignore the updated file. In addition, I found out that you can not use *.example.com in a CNAME to redirect to www.example.com - so I just added the redirection to nginx conf file as an IF stantement for both non-www to redirect to www and https://non to https://www
the ssl 443 if statement will also work to send https to http
this drove me bonkers for about 13 hours today.
Hey @uca,
I just wanted to note that you may need to add that nginx change again after updating MIAB.
thanks. I’ll try to remember when update. Also, I ran into a related issue as well that i keep coming back to:
I added the following to my custom DNS. When I used external DNS I don’t think I went to spam Using Amazon SES to send emails. I am now going to Spam with my AWS SES newsletter. I added the DKIM stuff as show below. What is the record indicating that AWS SES is not allowed to send on behalf of fwla.com? or what modification can I make to allow SES to send on fwla.com or box.fwla.com??? There has to be a way to allow this without too many compromises? no?
Domain Name Record Type Value
ses.fwla.com CNAME ec2-52-4-200-199.compute-1.amazonaws.com. [delete]
zbdkgrpi6bj._domainkey.fwla.com CNAME zbdkxw4ontjifneubvmzylhiigrpi6bj.dkim.amazonses.com. [delete]
q7fbkpikr4r3srpe._domainkey.fwla.com CNAME q7fbestqqkpikr4r3srpe.dkim.amazonses.com. [delete]
j7egudqcf4t5mvnqvr._domainkey.fwla.com CNAME j7egmvnqvr.dkim.amazonses.com. [delete]
www.fwla.com CNAME 2016-fwla-webserver-loadbalance-525.us-.elb.amazonaws.com. [delete]
fwla.com TXT v=spf1 mx include:amazonses.com -all [delete]
_amazonses.fwla.com TXT N4IUtq57cuiOqz3vhM=
OBVIOUSLY, I deleted some of the text above for security…even though I don’t know if it matters… LOL.
@uca: I think you’re right in Custom SPF Record, I think we covered this issue there. Let us know if we didn’t.