How To Force Certbot To Use Domain Name, Not Nameserver?

Server
12

Problem now solved: there needs to be a virtual host directive in the ssl.conf file, eg:

<VirtualHost *:443>
  ServerAdmin info@some.info
  DocumentRoot "/var/www"
  ServerName insurgent.info
  SSLCertificateFile /etc/letsencrypt/live/insurgent.info/fullchain.pem
  SSLCertificateKeyFile /etc/letsencrypt/live/insurgent.info/privkey.pem
  Include /etc/letsencrypt/options-ssl-apache.conf
</VirtualHost>

Note: the last three lines are added as part of the Certbot --apache process, so they will not be present when the VirtualHost directive is first added to ssl.conf.

Making two separate directives for IPv4 and IPv6 does not work and results in a broken configuration for IPv6 connections.

Also, it was necessary to remove all instances of ServerAlias and ServerName from the VirtualHost directives within the httpd.conf file, in addition to commenting-out the global ServerName value (ie: the default httpd.conf value).

These changes finally allowed Certbot --apache to install the certificates and I can now confirm that I have https:// working just as it should, with no browser complaints whatsoever, and no certificate exceptions required, in both Waterfox (a Firefox fork) and Internet Explorer. Thanks to all who made this possible and all on the forum who helped with my enquiry.