Check that a DNS record exists for this domain

I’m developing my web-electron app locally, registered a domain for which I have already a Let’s Encrypt certificate,
(base) marco@meet:~$ sudo /usr/share/jitsi-meet/scripts/install-letsencrypt-cert.sh

This script will:

Need a working DNS record pointing to this machine(for domain meet.my.domain)
Download certbot-auto from https://dl.eff.org to /usr/local/sbin
Install additional dependencies in order to request Let’s Encrypt certificate
If running with jetty serving web content, will stop Jitsi Videobridge
Configure and reload nginx or apache2, whichever is used
Configure the coturn server to use Let’s Encrypt certificate and add required deploy hooks
Add command in weekly cron job to renew certificates regularly

You need to agree to the ACME server’s Subscriber Agreement (https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf)
by providing an email address for important account notifications
Enter your email and press [ENTER]:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for meet.my.domain
Using the webroot path /usr/share/jitsi-meet for all unmatched domains.
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. meet.my.domain (http-01): urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up A for meet.my.domain - check that a DNS record exists for this domain

IMPORTANT NOTES:

The following errors were reported by the server:

Domain: meet.my.domain
Type: None
Detail: DNS problem: NXDOMAIN looking up A for meet.my.domain -
check that a DNS record exists for this domain

I already inserted a A + Dynamic DNS Record for meet.my.domain in the namecheap.com configuration settings where Dynamic DNS Record for my.domain is present.
And I’ve already put in /etc/hosts : xxx.xxx.xxx.xxx meet.my.domain
What else have I do for meet.my.domain ?

Is port 80 open?

(base) marco@meet:~$ sudo ufw status
Status: active

To                         Action      From
--                         ------      ----
2.36.58.214 443/tcp        ALLOW       Anywhere                  
80/tcp                     ALLOW       Anywhere                  
443/tcp                    ALLOW       Anywhere                  
10000/udp                  ALLOW       Anywhere                  
22/tcp                     ALLOW       Anywhere                  
3478/udp                   ALLOW       Anywhere                  
5349/tcp                   ALLOW       Anywhere                  
444                        ALLOW       Anywhere                  
4444                       ALLOW       Anywhere                  
80/tcp (v6)                ALLOW       Anywhere (v6)             
443/tcp (v6)               ALLOW       Anywhere (v6)             
10000/udp (v6)             ALLOW       Anywhere (v6)             
22/tcp (v6)                ALLOW       Anywhere (v6)             
3478/udp (v6)              ALLOW       Anywhere (v6)             
5349/tcp (v6)              ALLOW       Anywhere (v6)             
444 (v6)                   ALLOW       Anywhere (v6)             
4444 (v6)                  ALLOW       Anywhere (v6)

You’re not behind a NAT, right?

I’m developing in a local environment. How to check if I’m behind a NAT?

I checked here: https://www.whatismyip.com/ and the IP shown is the same IP of my ISP. So, I guess, I’m not behind a NAT

Quite likely you’re behind a NAT then. You need to forward port 80 in your router.

But according to the hints found here: StackOverflow: “how-can-i-know-if-my-computer-is-behind-nat” , due to the fact that the local IP address starts with 192.168. I should be behind a NAT.

Yes. According to the official indications: FAQ · Jitsi Meet Handbook I’m behind a NAT. I’m going to follow these guidelines: Self-Hosting Guide - Debian/Ubuntu server · Jitsi Meet Handbook . But a question arises at once: here it talks about videobridge. But I haven’t installed videobridge yet…

Don’t go to that yet. You first need to have that port forwarded. If you don’t know how, search online for your router model.

@Freddie

I found where to make port-forwarding.

But, as you can see, here it says : “The following ports will not be forwarded: 8080,6699,4443,2222,16161,8081,80,80,443,443,81,81,444,444,3000,3000,2000,2000,10000,22,3478,5349,8181,8181,445,445.” Does this cause a problem to Jitsi Configuration?

Port mapping is what you need to be looking at.

This is the Port Mapping already set:

Is this enough and correct or should I modify something?