khaled_mct
asked on
backend server can't send mail to internet
Dear all
In our organisation we have 1 domain controller with dns enabled, and on that dns forwader is disabled because i disable root hints.
now i install newly exchange server (backend connect with LAN , Front end connect with internet) now i am able to receive emails, but not be able to send it, what action i will take , so that backend server is able to send an email outside.
thanks
In our organisation we have 1 domain controller with dns enabled, and on that dns forwader is disabled because i disable root hints.
now i install newly exchange server (backend connect with LAN , Front end connect with internet) now i am able to receive emails, but not be able to send it, what action i will take , so that backend server is able to send an email outside.
thanks
The backend can usually send email fine. Unless told otherwise the server will try and send email on its own.
The first thing you should try is a full nslookup and then telnet test:
For example... microsoft.com:
C:\>nslookup
Default Server: server.domain.co.uk
Address: 192.168.1.1
> set type=mx
> microsoft.com
Server: server.domain.co.uk
Address: 192.168.1.1
Non-authoritative answer:
microsoft.com MX preference = 10, mail exchanger = mailc.microsoft.com
microsoft.com MX preference = 10, mail exchanger = maila.microsoft.com
microsoft.com MX preference = 10, mail exchanger = mailb.microsoft.com
maila.microsoft.com internet address = 131.107.1.7
maila.microsoft.com internet address = 131.107.1.6
mailb.microsoft.com internet address = 131.107.3.123
mailb.microsoft.com internet address = 205.248.102.77
mailc.microsoft.com internet address = 205.248.102.78
mailc.microsoft.com internet address = 205.248.102.79
>
When you have the MX server information, see if you can telnet to port 25 of the remote server.
For example (using the above information)
telnet maila.microsoft.com 25
If any part of that test fails, then you have a problem.
If the nslookup fails, then it is your DNS configuration.
If it is the telnet test, then you have a connectivity issue.
Try it from the frontend server as well.
You have mentioned that you have made changes to the DNS on the server.
For name resolution to work you should use either root hints, or forwarders. If you have removed both, then the server may have a DNS problem. DNS forwarders will usually be your ISPs DNS Servers - that is what I do as it provides the best performance. The root hints can be left in place, as with forwarders configured they will not be used.
Simon.
The first thing you should try is a full nslookup and then telnet test:
For example... microsoft.com:
C:\>nslookup
Default Server: server.domain.co.uk
Address: 192.168.1.1
> set type=mx
> microsoft.com
Server: server.domain.co.uk
Address: 192.168.1.1
Non-authoritative answer:
microsoft.com MX preference = 10, mail exchanger = mailc.microsoft.com
microsoft.com MX preference = 10, mail exchanger = maila.microsoft.com
microsoft.com MX preference = 10, mail exchanger = mailb.microsoft.com
maila.microsoft.com internet address = 131.107.1.7
maila.microsoft.com internet address = 131.107.1.6
mailb.microsoft.com internet address = 131.107.3.123
mailb.microsoft.com internet address = 205.248.102.77
mailc.microsoft.com internet address = 205.248.102.78
mailc.microsoft.com internet address = 205.248.102.79
>
When you have the MX server information, see if you can telnet to port 25 of the remote server.
For example (using the above information)
telnet maila.microsoft.com 25
If any part of that test fails, then you have a problem.
If the nslookup fails, then it is your DNS configuration.
If it is the telnet test, then you have a connectivity issue.
Try it from the frontend server as well.
You have mentioned that you have made changes to the DNS on the server.
For name resolution to work you should use either root hints, or forwarders. If you have removed both, then the server may have a DNS problem. DNS forwarders will usually be your ISPs DNS Servers - that is what I do as it provides the best performance. The root hints can be left in place, as with forwarders configured they will not be used.
Simon.
ASKER
ok i fix the error but some time exchange server able to send mail to internet like
((yahoo hotmail and other domain)) and some time
server!!!not able to route mail to internet i check my dns it's ok ..so any other reason or any good way to check exchange server dns work fine to route mail to internet
thanks
((yahoo hotmail and other domain)) and some time
server!!!not able to route mail to internet i check my dns it's ok ..so any other reason or any good way to check exchange server dns work fine to route mail to internet
thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanks you it's all work now just i have problem in hotmail..thw way you was very nice
ASKER
it's good idea to use simple dns plus ok or ???
http://www.simpledns.com/