D
drkrawuttke
hi there.
i have a webserver under www.example.net which has a prope
a-name-entry.
i have a mailserver example.net which only has an mx-entry.
now there are people complaning that they cannot reach my mailserve
because the host example.net doesn´t deliver an ip-address whe
using nslookup. so their mailserver is not able to send mail to m
domain although an mx-entry exists.
they say, that mailtransmission goes in two steps:
1. mailserver checks for valid domain by looking for ip-address i
a-name-entry.
2. mailserver sends out mail using mx-entry
if step 1 leads to an error step 2 isn´t even tried.
can anyone of you verify that?
next thing is that they told me, the simplest solution would be addin
the hostheader example.net to my webserver. this would lead t
example.net being resolved by dns.
can anyone verify that
-
drkrawuttk
i have a webserver under www.example.net which has a prope
a-name-entry.
i have a mailserver example.net which only has an mx-entry.
now there are people complaning that they cannot reach my mailserve
because the host example.net doesn´t deliver an ip-address whe
using nslookup. so their mailserver is not able to send mail to m
domain although an mx-entry exists.
they say, that mailtransmission goes in two steps:
1. mailserver checks for valid domain by looking for ip-address i
a-name-entry.
2. mailserver sends out mail using mx-entry
if step 1 leads to an error step 2 isn´t even tried.
can anyone of you verify that?
next thing is that they told me, the simplest solution would be addin
the hostheader example.net to my webserver. this would lead t
example.net being resolved by dns.
can anyone verify that
-
drkrawuttk