www.kylethinks.com fails to resolve. I followed the instructions outlined in Example: Setting up a static website in s3, but my www.kylethinks.com bucket does not correctly redirect to kylethinks.com. If I access kylethinks.com directly it works.
The problem appears to be related to name servers. Here are the results when I run a dig into www.kylethinks.com I see the following NS entries:
kylethinks.com. 172800 IN NS ns-146.awsdns-18.com.
kylethinks.com. 172800 IN NS ns-855.awsdns-42.net.
kylethinks.com. 172800 IN NS ns-1542.awsdns-00.co.uk.
kylethinks.com. 172800 IN NS ns-1531.awsdns-63.org.
However, the NS entries AWS originally provided when I set up www.kylethinks.com are as follows:
My question is: do I want the NS entries for www.kylethinks.com to match those for kylethinks.com, or do I need to restore the NS entries for www.kylethinks.com back to the AWS-provided defaults?
www.kylethinks.comfails to resolve. I followed the instructions outlined in Example: Setting up a static website in s3, but mywww.kylethinks.combucket does not correctly redirect tokylethinks.com. If I accesskylethinks.comdirectly it works.The problem appears to be related to name servers. Here are the results when I run a
digintowww.kylethinks.comI see the following NS entries:However, the NS entries AWS originally provided when I set up
www.kylethinks.comare as follows:ns-340.awsdns-42.com. ns-847.awsdns-41.net. ns-1492.awsdns-58.org. ns-1584.awsdns-06.co.uk.
My question is: do I want the NS entries for
www.kylethinks.comto match those forkylethinks.com, or do I need to restore the NS entries forwww.kylethinks.comback to the AWS-provided defaults?