Yes I agree, you can always do that and set Route53 as your dns for some specific AWS functionality. For instance static site hosting on a S3 bucket on your mai

Yes I agree, you can always do that and set Route53 as your dns for some specific AWS functionality. For instance static site hosting on a S3 bucket on your main domain (not www) isn't possible without having your domain in route53. Bigger threat of losing domains is not paying for them.