Incoming mail problem and LAN connection problem

[Lavien]

Well that is very odd. Because then with a dig -t NS on your domainname, then I should always get the NS records, even if your nameservers are not working or are offline.
And this is not the case at the moment.
I would suggest to contact your domain name registrar and have them kick the nameservers again.

It is very strange. I will try. Thanks for your advice

 

[zEitEr]

I would suggest to contact your domain name registrar and have them kick the nameservers again.

The domain is registered, but nameservers are not accessible: https://www.dnsinspect.com/metiselektrik.com/10846119 https://www.dnsinspect.com/elektrikakademi.com/10846120

Starting Nmap 7.92 ( https://nmap.org ) at 2025-06-25 01:46 +07
Nmap scan report for elektrik***demi.com (95.70.***.170)
Host is up (0.047s latency).
Not shown: 987 filtered tcp ports (no-response)
PORT     STATE SERVICE
21/tcp   open  ftp
22/tcp   open  ssh
25/tcp   open  smtp
80/tcp   open  http
110/tcp  open  pop3
143/tcp  open  imap
443/tcp  open  https
465/tcp  open  smtps
587/tcp  open  submission
993/tcp  open  imaps
995/tcp  open  pop3s
2222/tcp open  EtherNetIP-1
5000/tcp open  upnp

Nmap done: 1 IP address (1 host up) scanned in 5.05 seconds

Starting Nmap 7.92 ( https://nmap.org ) at 2025-06-25 01:50 +07
Nmap scan report for elektrik***demi.com (95.70.147.170)
Host is up (0.048s latency).
Not shown: 996 open|filtered udp ports (no-response)
PORT     STATE  SERVICE
21/udp   closed ftp
80/udp   closed http
443/udp  closed https
5000/udp closed upnp

Nmap done: 1 IP address (1 host up) scanned in 24.24 seconds

 

[Lavien]

The domain is registered, but nameservers are not accessible: https://www.dnsinspect.com/metiselektrik.com/10846119 https://www.dnsinspect.com/elektrikakademi.com/10846120

Starting Nmap 7.92 ( https://nmap.org ) at 2025-06-25 01:46 +07
Nmap scan report for elektrik***demi.com (95.70.***.170)
Host is up (0.047s latency).
Not shown: 987 filtered tcp ports (no-response)
PORT     STATE SERVICE
21/tcp   open  ftp
22/tcp   open  ssh
25/tcp   open  smtp
80/tcp   open  http
110/tcp  open  pop3
143/tcp  open  imap
443/tcp  open  https
465/tcp  open  smtps
587/tcp  open  submission
993/tcp  open  imaps
995/tcp  open  pop3s
2222/tcp open  EtherNetIP-1
5000/tcp open  upnp

Nmap done: 1 IP address (1 host up) scanned in 5.05 seconds

Starting Nmap 7.92 ( https://nmap.org ) at 2025-06-25 01:50 +07
Nmap scan report for elektrik***demi.com (95.70.147.170)
Host is up (0.048s latency).
Not shown: 996 open|filtered udp ports (no-response)
PORT     STATE  SERVICE
21/udp   closed ftp
80/udp   closed http
443/udp  closed https
5000/udp closed upnp

Nmap done: 1 IP address (1 host up) scanned in 24.24 seconds

I think I still need to change something on server conf files

 

[DrWizzle]

Looks to me like DNS issue still playing up. Port 53 missing from port list open above which is important for the nameserver setup and DNS functions of the server, unless you are relying on a 3rd party for your DNS like your domain registrar. Regarding Nameservers, check if there;s a misconfiguration? Post up your DNS record on DA for your main domain that's also used for NS. Check the glue records at the registrar also. Just a note, some (not all) require 2 nameservers minimum WITH 2 unique IP A records, Some registrars you can get away with 1 IP address for the 2 nameservers. Just trying to collab with the other guys here in giving you ideas on what and where to check.

 

[Lavien]

Looks to me like DNS issue still playing up. Port 53 missing from port list open above which is important for the nameserver setup and DNS functions of the server, unless you are relying on a 3rd party for your DNS like your domain registrar. Regarding Nameservers, check if there;s a misconfiguration? Post up your DNS record on DA for your main domain that's also used for NS. Check the glue records at the registrar also. Just a note, some (not all) require 2 nameservers minimum WITH 2 unique IP A records, Some registrars you can get away with 1 IP address for the 2 nameservers. Just trying to collab with the other guys here in giving you ideas on what and where to check.

Unfortunately I have double checked all of them and everything looks fine. I think my main problem is something blocking my port 53 from outside connections but couldn't find the reason up to now

 

[Lavien]

Now my website is working. I can connect port 53 via telnet but if I use port checker sites they say port is closed. I talked with my ISP and they said we can make PTR registers for your domain. They did and my web site start working. But autossl does not work for now. Also intodns gives same errors for DNS.

 

[Richard G]

I talked with my ISP and they said we can make PTR registers for your domain.

Yes, but they created the wrong one. They created PTR record for elektrikakademi.com. name while it should have been for your hostname so the server.metiselektrik.com name. Unless you changed your hostname again, but I guess not.

I can connect port 53 via telnet

Yes locally maybe, but externally the port is still closed. I presume you created a port forward to port 53 on your local server ip.
As long as that port 53 is not opened, the autossl function is also not able to work.