Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:www.feppesscanner.in
I ran this command:sudo certbot --apache
It produced this output: Which names would you like to activate https for ?
1:feppesscanner.in
2:www.feppesscanner.in
My web server is (include version):
The operating system my web server runs on is (include version): Ubuntu
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
I'm not sure what your question is. The thread title suggests there is a DNS issue with the www subdomain, which is confirmed by sites like https://dnsviz.net/d/www.feppesscanner.in/dnssec/: the www subdomain doesn't exist ("NXDOMAIN").
You'd want to add an A record for the www subdomain in your DNS providers zone editor.
You already have a certificate for feppesscanner.in. Unfortunately you haven't provided the version of Certbot used, but make sure that you don't end up with two separate certificates with just one hostname, but with a single one with both hostnames.