Gmail Help
Sign in
Google Help
- Help Center
- Community
- Gmail
- Privacy Policy
- Terms of Service
- Submit feedback
Send feedback on…
This help content & information
General Help Center experience
- Help Center
- Community
- New to integrated Gmail
Gmail
Stay on top of the new way to organize a space. Learn more about in-line threading.
-
#1
Hi Folks.
First of all, sorry for my English. I have a little Problem with my new root-server with Plesk Onyx. I’m hosting multiple domains on my server (just one IP-Adress). When I check these Domains with MXToolbox, I always got the same Warnings:
– Name Servers are on the Same Subnet
– SOA Expire Value out of recommended range
– Reverse DNS does not match SMTP Banner
I think the first and second warning is no problem. But I´m not sure about the third. A.E. every time I write mails to a outlook.com or gmx account, the mails marked as spam. I really want to get rid of this third but I don’t know, what to do. My PTR points to the FQDN of my server. Is there anyone who can give me a hand?
Regards
René
-
#2
1. check server hostname and confirm its pinging correctly to server ip
2. Check reverse dns of the ip and confirm it is having reverse dns matching to the above Server hostname.
3. In Plesk >> Tools and Settings >> Mail Server settings , make sure you have selected the correct ip as outgoing mail server ip.
4. Make sure you have Mail Server having proper SSL Cert having Server hostname (This can be set in Plesk >> SSL certificates >> Mail server (Letsencrypt)
Normally these should help you to fix it. If you can get me the ip we may be able to check it more but it is good to have a sysadmin to check that if you have no idea on the plesk settings
-
#3
Hi Sumesh.
Thanks for your help. I checked all these points already and all of them are working correctly. I still get these Warnings from MXToolbox. The IP of the server is 81.169.137.242 maybe you see something I don´t see. Thanks for your help!
-
#4
Can you got to Server Settings and change the server hostname to the www version from the plesk interface ? Rdns is showing “www.sfb-server.de.” and telnet is showing
sfb-server.de.
Server hostname and Rdns should be matching.
[[email protected] ~]# telnet 81.169.137.242 25
Trying 81.169.137.242…
Connected to 81.169.137.242.
Escape character is ‘^]’.
220 sfb-server.de ESMTP Postfix (Ubuntu)
[[email protected] ~]# host 81.169.137.242
242.137.169.81.in-addr.arpa domain name pointer www.sfb-server.de.
[[email protected] ~]#
-
#5
Seems you changed the hostname and that fixed I hope . I just revisited that and can see the hostname is fixed and is with www . Can you please confirm
Last edited: Jul 5, 2018
-
#6
Hello Sumesh.
Thanks for your advise. This solved the problem with the smtp banner. But i still get another problem. When I send mails to outlook.com or gmx they always marked as spam. Any suggestions on this?
-
#7
If you are not sending any bulk mails, then submit a whitelist request and that should fix it . It will take some time to pick up the change in dns and rdns made and that may have caused this.
-
#8
Perfect! Thank you so much!
-
#9
You are always welcome
-
#10
Hi everyone please can anyone help me?
I have recently setup a Plesk Onyx Server on a Windows Server 2016 Virtual Machine environment.
I have got 2 domains running on the server which will be each hosting a website and also sending and receiving emails.
I am able to to sent email to outlook.com, gmail.com, hotmail.co.uk, and also my other email domain but when i send i email to a number of private domain names, i get this message:
MailEnable: Message could not be delivered to some recipients.
The following recipient(s) could not be reached:
Recipient: [SMTP:*****@thelegal.group]
Reason: Remote SMTP Server Returned: 550 5.7.0 Your server IP address [removed for this purpose] is missing a reverse DNS entry. See Check IP Reverse DNS | Spam Auditor Blog for more information. Protection provided by MagicSpam 2.0.18-1 MagicSpam: Anti-Spam Protection Software for Email Servers
however the domains i am trying to send emails to, to test the server, i can receive emails from them domains.
if i require a reverse DNS how do I set this up.
please can you help me?
thanks
26 March 2010
VPS & Dedicated, Web Infrastructure
1,510 Views
Question: What does the following error mean:
WARNING: Not all of your nameservers are in different subnets
Answer: If you are receiving this error, it means that the nameservers for your domain are both originating from the same server (or two servers within the same subnet). Generally speaking, this is actually just a warning and not an error. Your server may still function just fine.
To be in full compliance with networking standards, however, you will need to host one nameserver at a different location, or at least on a different subnet. In other words, your domain registrar will require two IP addresses for your nameservers. You can have one on your actual server and have the other hosted on a separate server.
Some web hosting providers will offer remote nameserver hosting as part of their unmanaged dedicated server offerings. If they do not, there are other DNS hosting services that may offer what you need. As a last resort, you can configure your server to use two distinct IP addresses for each nameserver even if they actually both originate from the same place, although this is not ideal.
Image Source: Wikimedia Commons
Check Also
Server colocation
Server colocation is an incredible good choice for people as well as small businesses who …
Generally speaking, when a computer needs to do name resolution it will first try DNS and then try NetBIOS. Considering the current situation, he may check the following:
1. Ensure that the TCP/IP NETBIOS Helper service is started and the “Start Type” is set to “Automatic”.
2. NetBIOS protocol uses broadcast to resolve name so the two servers must be in the same subnet for the name to be resolved. From the ipconfig information, it seems that the Windows Server 2008 server and Windows Server 2003 server are in different subnets:
Windows IP Configuration
Host Name . . . . . . . . . . . . : svrweb1
WINS Proxy Enabled. . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.10.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
DNS Servers . . . . . . . . . . . : 66.28.0.45
66.28.0.61
Host Name . . . . . . . . . . . . : SvrBuild
WINS Proxy Enabled. . . . . . . . : No
IPv4 Address. . . . . . . . . . . : 192.168.10.25(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.254.0
DNS Servers . . . . . . . . . . . : 66.28.0.45
66.28.0.61
Are the subnet configuration of the two servers correct? Should they be configured in the same subnet?
If they must be configured in different subnets, it is expected that NETBIOS does not work in such scenario. You may consider the following options:
– Install a DNS server to provide internal name resolution function
– Configure the host file on the Windows Server 2008 server
– Install WINS server to enable NETBIOS name resolution that is across subnets
Laura Zhang – MSFT
-
Marked as answer by
Wednesday, August 5, 2009 10:41 AM
The parent zone is not obligated to provide glue records for a delegation if the delegated-to host names is not under the delegated name. Glue records are only needed if a delegation points to something that the delegation would need to be followed for to be useful.
Since you are delegating gignouser.com to name servers under eu.clouds.host, that is not the case and glue records are thus not required to be returned by the name servers hosting the delegation to gignouser.com — meaning the com TLD DNS servers.
If you look at the delegation of clouds.host you will see that the delegation from the nic.host DNS servers does include glue records.
I do however notice something that may contribute to problems:
You are serving NS RRs with a 0 TTL, for both domains. This can be problematic. If you want to minimize the time that DNS servers cache the delegation data (why you’d want to do that to such an extent I don’t know), then serve it with some small but non-zero TTL. I suggest using a minimum of 10 seconds TTL to give resolvers and proxies a chance to do their thing even if they abide by TTLs internally during the recursive resolution process.
I would fix the TTLs first, and see if the problem goes away. It’s certainly possible that the report tool you are using is being confused by the zero TTLs.
I also notice that it appears that you are running both name servers on the same subnet — specifically, on adjacent IP addresses — which presents a massive single point of failure. If that is the case, strongly consider getting an off-site slave DNS server, especially if you want to serve zone authority data with very short TTLs. While “everything else will be down anyway” is a valid point on the face of it, which error would you rather the users get if your servers are unavailable; “the host name www.gignouser.com was not found” or “the server did not respond”? I would absolutely prefer the latter, even if the end result at that moment is the same in that your web site is unavailable.
