I've got a Django application deployed on an Ubuntu 16.04 EC2 instance using nginx and gunicorn.
Unfortunately, after a successful deployment with my public IP, updating my A record with the public IP yielded a
404 Bad Request error at my domain--even after waiting a long while to make sure DNS changes propagated. Accessing the application by the public IP continues to work. I did contact my name server host, to confirm if I correctly set my A record settings: they said the DNS change appeared successful, but could not help as it appeared it was an issue on AWS's side.
Is there a specific reason why utilizing my public IP in my A record is not working correctly and is not pointing to my application?
Thank you for anyone who might be able to help me get my domain to successfully point to my deployed django project. At present, the accessing the application via the public IP still works fine, the A record appears to be updated, but any attempts to load the domain (not the direct IP), renders a 400 Bad Request error.