Windows Forum

Ask something
Discussion Locked

Exchange not working since IP change

0 helpful
5 replies

by sturner 2 views

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Recently Verizon screwed us up by changing our public IP scheme. (We added 4 Ip's) and did not give us the new info before they made the cnage over. After figuring out what had happened, we quickly changed the Ip on our Gateway server (Proxy 2.0, ouch!) and sent a request to NetSol to change our DNS entry.

Since that change has happened, my Exchange 5.5 Server no longer sends mail or recieves mail. All outbound messages are in the queue waiting and all people sending get an undeliverable message after about 4 hours or so!

Do I need to wait longer for DNS to propigate (Change was effective yesterday) or is there a setting change that I am missing?

I went into our DNS server and changed Ip's for Exchange already.

Help and thanks!!!!

Email at usmarcor@tampabay.rr.com (I am not getting email at work, haha)

5 replies

by m.r.

If it's a sending issue then your new NetSol reg. shouldn't matter except for destinations that do reverse lookups to verify. Sounds more like you have a problem reaching external DNS. Is there an internal DNS that needs updating? Forwarders? Route info?

by tim.doyle

I think you need to have your ISP also change your MX record on their servers in order for mail to ever get to your server from the internet. If your old MX record pointed whatever.com mail traffic to 100.100.100.100 but your new IP address is now 152.64.24.33 then mail has no way of getting into the system. Logically the reverse direction should be true...if your records are screwed up then you have no prayer in sending mail.

by sturner

We host our own DNS and the MX record was changed. The problem was fixed and it required us to reinstall DNS and IIS on the root server. We had an issue with IIS that was stopping mutliple services including DNS.

This discussion is closed to new replies.