• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 505
  • Last Modified:

Exchange server resolving to the wrong IP

I have a single Exchange 2003 SP2 server on a Windows 2003 server.  When I ping the email server name from a workstation I get the correct IP but when I ping the email server from the server itself It resolves to the wrong address.  I have cleared the dns cache but this does not seem to help. I think this is causing my queue to back up. I can send to some people externally but some of the mail never leaves the queue and i get a 5.1.3 error.
0
gzitlaw
Asked:
gzitlaw
  • 10
  • 10
2 Solutions
 
tenaj-207Commented:
Check the host file.  c:\windows\system32\drivers\etc\hosts

You could even add an entry for your exchange server for example
192.168.0.2      ExchangeServer

Where does your Exchange server resolve to?  Make sure it's the same as the hosts.
0
 
gzitlawAuthor Commented:
tenaj,

Thanks for the quick reply.  hosts file is good and there is an the entry is correct for my exchange server but when i ping the exchange server from my workstation it resolves the exchange server to the correct IP, but when I ping the exchange server on the exchagne server it resolves to the IP of the SAN that I have my mail store on which is a completely different IP.  I have my exchange box on an HP blade and my store is on an ISCSI SAN if that helps any. I'm wondering if my internal DNS is screwed.  
0
 
tenaj-207Commented:
Normal operating procedures would have you point the Exchange server towards the same DNS server that the clients are pointing at.  

Are you saying that your Exchange server is pointing towards itself for DNS?  If so then I'd switch it to the DNS server that is doing DNS for your clients.

Another thing to check is if you have a second NIC that might have a static IP address assigned to it.


0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
gzitlawAuthor Commented:
Tenaj,

My exchange box is a domain controller (i know this is a no no per MS, but i inherited this setup), and when i ping it  from a command prompt on the exchange server it resolves to the wrong address (the address of my SAN).  I have two NICS one for my LAN and the other one for ISCSI.  I know I am missing something simple I just am to tired to see it.  Thanks for all the help.
0
 
tenaj-207Commented:
Run nslookup from the command line?  The output should be;
Default Server: FQDN
Address: Server IP address

Also run ping -a IPADDRESS.  The first line should be the name of your exchange server.  This makes sure that reverse DNS is set right.

Check your DNS settings.  Open the DNS Manager and expand ServerName > Forward lookup zone > domain.local.  Organize the IP addresses by clicking on the Data field at the top of the screen and then look for the IP address of your server and make sure it's not matching up with the wrong server.
0
 
gzitlawAuthor Commented:
tenaj,

I did the ping -a to my exchange server and it came up and resovled to the wrong server name.  it should be resolving to XXXexch02 but is resolving to XXXexch01.  I checked dns and the server name and the ip matches up correctly, but there is one other curious thing I have duplicate A records that show like this:

(same as parent folder)            Host (A)                       X.X.X.X Server IP
XXXexch02                               Host (A)                       X.X.X.X Server IP

The IP is the same for both records.  Is there such a thing as phantom DNS records??
0
 
tenaj-207Commented:
Right click on the parent folder on the left which should be domainname.local choose properties and go to the Name Servers tab.  In here make sure the FQDN is XXXexch02.  If not then change it to that, probably something like, XXXexch02.DomainName.local.
0
 
gzitlawAuthor Commented:
They are all set correctly.  I also looked at the SOA and it shows the exch02 server.  I still have a couple emails stuck in my outbound queue.  They used to zip right out but they seem to be slow.
0
 
tenaj-207Commented:
Are you using SBS 2003 or Server 2003 standard with Exchange 2003 standard?

The reason I ask is because changes with SBS is supposed to be done with wizards.
0
 
gzitlawAuthor Commented:
Server 2003 SP2
Exchange 2003 SP2
0
 
tenaj-207Commented:
In DNS check your reverse lookup zones using the same method you used on the Forward lookup zones.
0
 
gzitlawAuthor Commented:
exch02 show in the reverse lookup as having my external IP address.  Shouldn't this be an internal IP?
0
 
tenaj-207Commented:
Yes.  Your reverse lookup should say 192.168.1.x subnet (or whatever your internal subnet is).  In that reverse lookup there should only be IP addresses with 192.168.1.1-154.  If you have another in there that could be causing the problem.
0
 
tenaj-207Commented:
Also have you tried clearing your arp cache? At a command line run;

netsh interface ip delete arpcache
0
 
gzitlawAuthor Commented:
I cleared the arp cache and i went to mxtoolbox and did the test and the reverse dns works fine.  I still have a couple emails stuck in the queue.
0
 
tenaj-207Commented:
Your DNS reverse lookup (internal lookup) is different than reverse DNS (external lookup) that you check at mxtoolbox.  Did you fix the IP address in the DNS reverse lookup zone?
0
 
gzitlawAuthor Commented:
How should my Outbound security be set on my smtp virtual server?  I think some of my outgoing issues are related to one of my users having a spamming like malware that may have got us greylisted by some of our customers email servers.  
0
 
gzitlawAuthor Commented:
yes my reverse nameservers now look like my forward name servers
0
 
tenaj-207Commented:
Sounds like DNS is fine.  Look at your NIC's.  Make sure that the only DNS entry is for the primary IP address for XXXexch02.  Both NIC's should have that for their DNS setting, and only that, no secondary DNS IP address.
0
 
gzitlawAuthor Commented:
Tenaj-207,

I ended up getting my ISP to change my external as I was getting greylisted by the individual customers we were trying to send too.  I would have almost rather gotten blacklisted.  Thanks for all your help in my time of need.  
0

Featured Post

[Webinar] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

  • 10
  • 10
Tackle projects and never again get stuck behind a technical roadblock.
Join Now