Incoming mail problem and LAN connection problem

When I try port checker web sites, it says port 25 is closed but if I connect to VPN with my PC and telnet my server at port 25, it is connecting. Really strange.
 
I don't know how the VPN is setup up. But if port checker says it's closed then mostly it is indeed closed.
And as said, I tried with 2 different servers (1 in Germany and 1 in Finland) and both could not connect.

Only other option I can think of otherwise is that only very little part of internet in the firewall is opened by your ISP.
 
Lavien said:
When I try port checker web sites, it says port 25 is closed but if I connect to VPN with my PC and telnet my server at port 25, it is connecting. Really strange.
Click to expand...

If your server has local IP, then you will need to check the routing and firewall settings. When you connect to the server from your local network, local IP is used. When you use VPN, then public IP address is used. You can not solve routing issues by re-installing DirectAdmin.

Search and read: https://www.google.com/search?q=local+server+behind+nat+is+not+accessible+from+local+network
 
Maybe my main problem is the router given by my ISP. I will try different one for hidden firewall or closed port issues
 
Once again, when you have a server behind NAT, and you try to connect from localnet, you might have various routing issues. You try to connect a public IP from a local IP. A router and/or server might block such requests. And you might need to configure Source based routing on the server or on the router. This is what is coming to my mind, based on what you wrote.

This is my final posting in the thread. I hope you will get the issue fixed. If you have other questions, I will be happy to help you.
 
I will try something different. Is there any documentation for Amazon SES (simple email service) integration to directadmin? I want to send and receive emails through SES without using port 25. Is it possible?
 
Ok. Incoming port 25 problem stems from csf incoming udp ports. I added port 25 and mail receiving problem ended. That was really silly. After that I have a new problem. My DNS port (53) responds when I am in the same network with my server but not responding outside connections. I reinstalled everything but nothing changed. I read some forums but I think their solutions are for older versions of direct admin. For example I have only
include named.conf.*
stuff in my named.conf file. Nothing like include all 53 ports etc.
What can I do for solution.
 
Lavien said:
stems from csf incoming udp ports. I added port 25
Click to expand...
Mail port 25 is TCP not UDP.

Lavien said:
I have only
include named.conf.*
stuff in my named.conf file. Nothing like include all 53 ports etc.
Click to expand...
I really wonder what goes wrong with your installation, did you wait long enough after installing? Because DA installs quickly, but after that you have to wait until you get a message in the message center that all background tasks are finished.
Once you have that message, your named.conf file should look way more filled.

Or are you on a Debian alike system, that might look differently.
 
Richard G said:
Mail port 25 is TCP not UDP.


I really wonder what goes wrong with your installation, did you wait long enough after installing? Because DA installs quickly, but after that you have to wait until you get a message in the message center that all background tasks are finished.
Once you have that message, your named.conf file should look way more filled.

Or are you on a Debian alike system, that might look differently.
Click to expand...
Thanks for your response. Port 25 is something strange but it is solved after adding 25 to udp ports of csf. Anyway I waited till end of da build all procedure. I am using Ubuntu 24.04 running on a raspberry. Should I use different linux distro? I am attaching my named.conf file.
 

Attachments

  • Ekran görüntüsü 2025-06-23 023601.png
    Ekran görüntüsü 2025-06-23 023601.png
    49.5 KB · Views: 7
Lavien said:
Port 25 is something strange but it is solved after adding 25 to udp ports of csf.
Click to expand...

That might prove you have an issue with either NAT or port forwarding. Exim does not use UDP. And if it is true, it might be the reason on why DNS:53 (TCP+UDP) is not available from internet.
 
Lavien said:
Thanks for your response. Port 25 is something strange but it is solved after adding 25 to udp ports of csf. Anyway I waited till end of da build all procedure. I am using Ubuntu 24.04 running on a raspberry. Should I use different linux distro? I am attaching my named.conf file.
Click to expand...
Your named.conf file is unwritable there. Could be 2 reasons, 1 is you're not running nano as root, and 2 you may not have correct permissions set on file.

Have you checked your host? I know companies like Hetzner will block port 25 and only open it with a valid reason from you , like you need it for shared hosting or similar.

If you're running ubuntu 24.04, have you checked your DNS setup? To do this, type in 'resolvectl' at the root prompt and it will give you details of the nameservers your server is using to get it's info from. It may return something like:
Code: 
Global
           Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: stub
  Current DNS Server: 8.8.8.8
         DNS Servers: 8.8.8.8 1.1.1.1
Fallback DNS Servers: 8.8.4.4 1.0.0.1

Link 2 (ens18)
    Current Scopes: DNS
         Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 1.1.1.1
       DNS Servers: 1.1.1.1 8.8.8.8


You can edit these values as follows:

in the /etc/systemd/resolved.conf
Code: 
[Resolve]
DNS=8.8.8.8 1.1.1.1
FallbackDNS=8.8.4.4 1.0.0.1
Then run:
#systemctl restart systemd-resolved

in the /etc/netplan folder look for a file like 50-cloud-init.yaml (Should look something like this):

Code: 
network:
  version: 2
  ethernets:
    ens18:
      addresses:
      - "10.0.29.2/29"
      routes:
      - to: "default"
        via: "10.0.29.1"
      nameservers:
        addresses: [1.1.1.1, 8.8.8.8]
Make sure nameservers are there as they will help.

Any changes to this file, save, then run:
#netplan try
#netplan apply
 
zEitEr said:
That might prove you have an issue with either NAT or port forwarding. Exim does not use UDP. And if it is true, it might be the reason on why DNS:53 (TCP+UDP) is
Click to expand...

DrWizzle said:
Your named.conf file is unwritable there. Could be 2 reasons, 1 is you're not running nano as root, and 2 you may not have correct permissions set on file.

Have you checked your host? I know companies like Hetzner will block port 25 and only open it with a valid reason from you , like you need it for shared hosting or similar.

If you're running ubuntu 24.04, have you checked your DNS setup? To do this, type in 'resolvectl' at the root prompt and it will give you details of the nameservers your server is using to get it's info from. It may return something like:
Code: 
Global
           Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: stub
  Current DNS Server: 8.8.8.8
         DNS Servers: 8.8.8.8 1.1.1.1
Fallback DNS Servers: 8.8.4.4 1.0.0.1

Link 2 (ens18)
    Current Scopes: DNS
         Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 1.1.1.1
       DNS Servers: 1.1.1.1 8.8.8.8


You can edit these values as follows:

in the /etc/systemd/resolved.conf
Code: 
[Resolve]
DNS=8.8.8.8 1.1.1.1
FallbackDNS=8.8.4.4 1.0.0.1
Then run:
#systemctl restart systemd-resolved

in the /etc/netplan folder look for a file like 50-cloud-init.yaml (Should look something like this):

Code: 
network:
  version: 2
  ethernets:
    ens18:
      addresses:
      - "10.0.29.2/29"
      routes:
      - to: "default"
        via: "10.0.29.1"
      nameservers:
        addresses: [1.1.1.1, 8.8.8.8]
Make sure nameservers are there as they will help.

Any changes to this file, save, then run:
#netplan try
#netplan apply
Click to expand...
Ok I will try it. Thanks for your help. what should I write to nameservers side, my own or google's dns?
 
Lavien said:
Ok I will try it. Thanks for your help. what should I write to nameservers side, my own or google's dns?
Click to expand...
For the nameservers, and in my example, i've used 1.1.1.1 and 1.0.0.1 (Cloudflare's DNS and fallback) with 8.8.8.8 and 8.8.4.4 (Googles DNS and fallback). Your nameservers for your server are so that others can find your sites on your server. That's your DNS, but for reaching the outside, Google & Cloudflare's DNS are usually the fastest and best. It's again, down to personal preference, but the steps I mentioned above should give you a pretty solid foundation.
 
zEitEr said:
DirectAdmin would have failed to add the zone into the file, if it was the case.
Click to expand...
I did not login as root while I was taking ss. Therefore it says "unwritable". Is there any configuration for directadmin to login as root while da build all. I thought it aotumatically login as root and make config
 
I have done some stuff but nothing changed. Still getting DNS error on intoDNS. I am attaching images for my situation
 

Attachments

  • 1.png
    1.png
    38.9 KB · Views: 7
  • 2.png
    2.png
    36.2 KB · Views: 6
  • 3.png
    3.png
    152.9 KB · Views: 7
Lavien said:
I have done some stuff but nothing changed. Still getting DNS error on intoDNS. I am attaching images for my situation
Click to expand...
Also looking at 3rd image and looking on https://dnschecker.org/ your server is not reachable, it cannot see any A record, MX or even NS records for elektrikakademi.com. Looking more and more like a DNS issue here, along with a potential firewall issue as I can see port 22 open from the internet, but important ports like 53, essential for DNS is closed and 80 essential for http. Check your firewall first and then when your ports are open, cheack all your server DNS settings. Hope that's a little help, giving you somewhere to start
 
And I have new problems. After these changes, my server cant connect to internet and after I added dhcp4: no dhcp6:: no accept-ra: no I couldnt connect my server locally:D
 
You must log in or register to reply here.
Back
Top