What should be the FQDN for a server on the local network?

Question

Domain Name System

Good afternoon, comrades!
Please don't hit stupid questions. The situation is this:
A small test site is being assembled. For this, a virtualization server was built (hostname of the server = vmserver1 ). Basically, it will host machines for internal use (imitation of the corporate infrastructure AD, DNS, DHCP, file share, mail, etc.), but it will probably host a simple test site (let's say the domain name of the site is example.com , and the hostname of the webserver will be webserver1 ).
After reading the article , I came to the conclusion what should be done according to "best practices".
We will divide the test environment into external and internal .
Questions:
1) What should be the FQDN for the virtualization server (as well as the VMs of the internal internal zone)?
I'm guessing these are:
vmserv1.internal.example.com
vm01.internal.example.com
2) What should be the FQDN for the web server?
I assume that they are:
webserver1.external.example.com (or maybe webserver1.example.com)
3) I don’t quite understand what parameters to specify in this case in the resolv.conf file (domain, namespace)

Answer 1

see
FQDN - this is the name of the host in the DNS system, that's all
it can be anything, even microsoft.com or myserver.microsoft.com if your DNS resolves it correctly, they
often make a virtual domain (although it may already have appeared) - .dev, again - if your DNS...
in order not to worry about DNS, you can take a real domain controlled by you and configure everything in it
WHAT NAMES you give to machines - do not care
www0.twoydomen.com, suck.my.dick.ugly.bitch.twoydom com
, as long as you correctly set them up in the required DNS
, it is logical that it would be good to sew some functionality into the names - well, sew up
external unternal mail suckmy... oh..