Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 449
  • Last Modified:

I change my external DNS host and email is not coming through.

this company called XNET was in control of DNS for my companies email.  i talked to them on the phone and they told me that they were basically redirecting all my mail to my exchange box in house.  however, we did not have any billable services from them anymore, so they were not charging us anything.  they asked me if i could move my DNS over to Network Solutions, who we purchased our domain name from.

Yesterday afternoon, I took our DNS from XNET and moved it to NETWORK SOLUTIONS.  As of late yesterday afternoon, no email has been coming through to my exchange box.

According to network solutions, my mail record is configured properly.

Here is what I get when I try to send from my gmail account

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 Requested action not taken: mailbox unavailable (state 14).

If anyone can shed some light, I would appreciate it.  I am on hold right now with tech support to see if they can tell me anything.
0
tomdlgns
Asked:
tomdlgns
1 Solution
 
tomdlgnsAuthor Commented:
the in house exchange box can send mail out.  it has windows server 2003 and exchange 2003
0
 
MikealclCommented:
Recap:

You created DNS records on Netsol( with valid MX )
You changed the authoritative DNS servers for your domain @ netsol
Mail stopped?

If the DNS records are the exact same the only difference I would expect is that XNET could have deleted the DNS records and it takes some time for the authoritative to change over.  I would still expect you to be receiving some mail though, just not all of it.

0
 
tomdlgnsAuthor Commented:
xnet told me they would NOT do anything until i called them a week after the change to verify that everything works.

@ net solu. i created my MX record, which points to my exchange WAN.  tech support from net solu told me that all mail @(companyname).com points to my WAN Exchange box...which it should.

i didnt make any changes on the exchange server.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
tomdlgnsAuthor Commented:
i can resolve my webmail from outside my network, so i know that DNS name has propagated.
0
 
tomdlgnsAuthor Commented:
do i need to change a record on my exchange box?
0
 
Michael WorshamInfrastructure / Solutions ArchitectCommented:
Is it possible to get an export of your DNS zone file for your domain?

Also, do you have a hardware router/firewall in front of your network? Does it's WAN IP address correspond to the same one as your A record in your DNS zone file?

---

Another thing you could try is checking your DNS/MX records via these sites to see if they are correct:

http://www.mxtoolbox.com
http://www.dnsstuff.com
http://www.intodns.com

0
 
tomdlgnsAuthor Commented:
Also, do you have a hardware router/firewall in front of your network? Does it's WAN IP address correspond to the same one as your A record in your DNS zone file?

i do, but i dont know what zone file you are talking about.
0
 
subliferCommented:
Just to add to the above, it can take 24 to 72 hours normally for DNS records to replicate across the internet.
0
 
tomdlgnsAuthor Commented:
ns93.worldnic.com reports the following MX records:

10      mail.companyname.com      x5.x1.x0.xx7      7200
0
 
tomdlgnsAuthor Commented:
is this something on net solu side?  or would a setting on my server need to be changed?
0
 
tomdlgnsAuthor Commented:
i know it can take 24-48 hours to propogate, but according to mxtoolbox.com, my mx record is pointed to net solutions.

0
 
tomdlgnsAuthor Commented:
from mxtools.com it shows my DNS host, but nothing for email host.

10/31/2008 9:17:41 AM Central Standard Time

DNS Host: Network Solutions
Email Host:
0
 
tomdlgnsAuthor Commented:
i am confused right now.

net solutions is telling me they dont actually hos an mx record, they just point to one.

0
 
MikealclCommented:
Sounds like your really missing an mx record.
Was netsol suppose to import your old DNS records for you?

I believe they have a web management tool you can use to add the MX record.
0
 
tomdlgnsAuthor Commented:
thats the thing, i already added the mx record.  and tech support told me it is setup properly.
0
 
MikealclCommented:
"net solutions is telling me they dont actually hos an mx record, they just point to one."
That statement doesn't really make sense.  Do they mean they don't host your exchange?


0
 
tomdlgnsAuthor Commented:
they dont host my exchange, i host it in house.

thats what one tech support agent told me...he said, we dont host any of your mx records, we just point it to the public IP that you want...which is setup correctly in my account profile.
0
 
tomdlgnsAuthor Commented:
can someone tell me that this is NOT a setting on the server side?

i dont think it is, but i would like to rule that out.
0
 
tomdlgnsAuthor Commented:
ok, so i sent an email form my gmail, and it came through my exchange box.  

i then tried to send another email through my gmail and it didnt come through the exchange box.

so does this mean that propagation is still in effect?
0
 
tomdlgnsAuthor Commented:
it seems that every 5th or 6th email will go through from my gmail, off of network, to my exchange email.  but then a handful fail.
0
 
tomdlgnsAuthor Commented:
strange.....every now and then an email comes through from gmail.

i don't understand this.

0
 
tomdlgnsAuthor Commented:
now this is the error i am getting from gmail

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 sorry, mail to that recipient is not accepted (#5.7.1) (state 14).
0
 
tomdlgnsAuthor Commented:
this doesnt seem to be an MX issue any longer.  it seems to be an exchange server issue.
0
 
tomdlgnsAuthor Commented:
ok guys, i figured out the problem....

my symantec mail security on the exchange server was set to only accept mail from XYZ ip address/domain name.

xnet was the only ip/domain name in that filed.  i disabled the mail security and sure enough emails started to come through.

so now all i need to do is enable the mail security and plug in the proper ip/domain name from net solu and everything will be configured properly.

thanks for the input.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

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