Incoming mail problem and LAN connection problem

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
 
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


Code:
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


Code:
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
 
The domain is registered, but nameservers are not accessible: https://www.dnsinspect.com/metiselektrik.com/10846119 https://www.dnsinspect.com/elektrikakademi.com/10846120


Code:
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


Code:
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
 
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.
 
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
 
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.
 
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.
 
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.


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.
ISPs are fickle creatures at the best of times, but it seems strange an ISP would block port 53, especially when they issue a static IP which almost always gets used with some sort of DNS application. I hope @Lavien is able to resolve this as it seems to have been a complete headache for the chap/chapette. I know my ISP doesn't block any ports, but on the other hand, I rent a static IP (just for testing bits on DA before putting them on a production server) and i've asked my ISP if I can have them create an rDNS record for me but they refuse saying "they cant". It's a shame as without it, i'm unable to host my own email without getting flagged by Spamhaus every week.
 
but it seems strange an ISP would block port 53
From one side yes. From the other side no. Seems our ISP also has this blocked incoming for security reasons. Because they can't be sure their customers configure it the correct way and then it might be abused for DDOS or other kind of attacks. So after years of having it open, they decided to close it.
On the other hand, only very few of our ISP's (rather small ones) would give the service to give you a custom PTR record. Mostly those who do that, also do not have port 53 closed.

I also hope @Lavien is able to resolve it, otherwise it might be better to use an alternative solution and get a cheap VPS for example with Contabo or another cheap but good VPS provider and run the server from there. More people are doing that.
 
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.


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.
I can connect it from outside of my server network. You can also try
 
From one side yes. From the other side no. Seems our ISP also has this blocked incoming for security reasons. Because they can't be sure their customers configure it the correct way and then it might be abused for DDOS or other kind of attacks. So after years of having it open, they decided to close it.
On the other hand, only very few of our ISP's (rather small ones) would give the service to give you a custom PTR record. Mostly those who do that, also do not have port 53 closed.

I also hope @Lavien is able to resolve it, otherwise it might be better to use an alternative solution and get a cheap VPS for example with Contabo or another cheap but good VPS provider and run the server from there. More people are doing that.
Thanks for your thoughts. I think I will end up with my own home server dream if things will go like this.
 
From one side yes. From the other side no. Seems our ISP also has this blocked incoming for security reasons. Because they can't be sure their customers configure it the correct way and then it might be abused for DDOS or other kind of attacks. So after years of having it open, they decided to close it.
On the other hand, only very few of our ISP's (rather small ones) would give the service to give you a custom PTR record. Mostly those who do that, also do not have port 53 closed.

I also hope @Lavien is able to resolve it, otherwise it might be better to use an alternative solution and get a cheap VPS for example with Contabo or another cheap but good VPS provider and run the server from there. More people are doing that.
I would also second Contabo for their VPS solutions. Very reasonably priced and if it's not a huge site he's hosting, probably get setup comfortably for around 5-10 Euro a month. I've used them on many an occasion for different projects and Directadmin works literally out of the box on their servers, with very little faffing about. I also like their rDNS setup as it's so simple to match up to the server for PTR records and email validation. Not sure what the latency would be for him though if he's in Türkiye but if it's a small enough site it shouldn't matter. Hetzner are also a very good cheap provider
 
I would also second Contabo for their VPS solutions. Very reasonably priced and if it's not a huge site he's hosting, probably get setup comfortably for around 5-10 Euro a month. I've used them on many an occasion for different projects and Directadmin works literally out of the box on their servers, with very little faffing about. I also like their rDNS setup as it's so simple to match up to the server for PTR records and email validation. Not sure what the latency would be for him though if he's in Türkiye but if it's a small enough site it shouldn't matter. Hetzner are also a very good cheap provider
I will try it. Thanks for your advice. Really appreciated
 
I will try it. Thanks for your advice. Really appreciated
No worries, I've just checked (out of morbid curiosity), and they've got a fantastic deal on at the moment that would be ideal for 1 or 2 sites. I've used this server before for the DirectAdmin Personal Plus licence, and it runs very smoothly.


Best of luck!
1750971284841.png
 
No worries, I've just checked (out of morbid curiosity), and they've got a fantastic deal on at the moment that would be ideal for 1 or 2 sites. I've used this server before for the DirectAdmin Personal Plus licence, and it runs very smoothly.


Best of luck!
View attachment 9098
Is there any link that means you redirected me to contabo for making some benefits for you?
 
Is there any link that means you redirected me to contabo for making some benefits for you?
No, i'm not affiliated with them in any way, shape or form so I don't benefit in any way from them. I'm simply a customer of theirs from time to time when I need a quick cheap VPS for a project. I just shared the link for the product I showed in the screenshot for your quick reference.
 
Is there any link that means you redirected me to contabo for making some benefits for you?
I also mentioned them before in post #69 as you could see. Because they are just a cheap and good VPS provider. I just said "or another good cheap vps provider" because I don't really want to benefit them against maybe other good ones.

@DrWizzle is right and we also used them once a while. Having a VPS now there to run our 2nd DNS server.
We had a full DA license running on a bit more expensive VPS from them, but you have to be a bit lucky too. They are very good and easy configurable, but mind that those prices have to come from somewhere. And that comes from overselling.
So even on our 2nd DNS vps, we notice that it's going way slower as it should be. However, for 2nd DNS that is no issue.
We had to move the full license DA server because for about the first 9-12 montsh it went great and then speed went down often and it was not doable anymore so we rented a server at Hetzner.

We also had a VPS for a hobby server with a forum and that worked great until the admin stopped the forum a year later. ;)

So Contabo is cheap and surely good usable, but be aware that due to overselling sometimes (or long) the working speed of your system can go down. Just something to keep in mind. Does not happen always, as said, lot of people are happy with them too.

I can connect it from outside of my server network. You can also try
From where outside? I tried this afternoon and no way port 53 was open.
At this point, I can not find hostname or domain name via my server and telnetting to port 53 on your ip is also still not possible, tried just now again.
 
I'm not recommend to use the contabo, it's very bad services, Low price come with many many issued.
Digitalocean or OVHCloud is good to start.

Or use colocation service with your own server. this gonna be low price than VPS, when you already have high spec self server.
 
Back
Top