Start Free Trial

asked on

Transferred our domain name to go daddy. Now our owa is no longer workin

Transferred our domain name to Go daddy. changed our mx and dns records (per their instruction). I suspect maybe they are not setup correctly. Can someone please help me ensure the records are correct.

our webmail uses: https://mail.domainname.com/owa and remote

Do I need to use a cname alias? Godaddy seems to have some defaults (should those entries be there: ( email.secureserver.net)

I have the "A record" that calls out domainname.com

HELP!
I have a MX (mail exchanger) record that call out the mail.domainname.com

Please see the pic........The black spot is the correct WAN IP (why is the 184.168.221.35 in there? go daddy had me enter it)
records.jpg

It sounds like you changed your registrar and your DNS? What exactly is not working? Is it not resolving? Changing registrars and DNS should not be problem if you recreated all of your DNS records exactly. You do not need a CNAME, just an A record. MX records should not have anything to do with OWA not resolving.

Can you browse OWA with the localhost on your IIS server?

If you ping your domain name does it resolve to the correct IP for the A Record?

What do you mean by "Godaddy had me enter it"?

Also, you said your MX record is mail.domainname.com and OWA uses mail.domainname.com but you said your A Record is for domainname.com. Do you have an A record for mail.domainname.com that points to the correct IP address?

ASKER

We are getting email. I can no longer get to the https://mail.domainname.com/owa

nor the https:/mail.domain.com/remote

Did you create the A record for mail.domain.com?

If you ping mail.domain.com does it resolve to the same IP address that the A Record has in godaddy?

If so, is that IP address the same one that you have for your OWA server? If you only have one public IP for your OWA server go to www.whatismyip.com and confirm that it is the same IP as your A record in Godaddy.

ASKER

Did my picture of the records not load properly?

ASKER

Did my picture of the records not load properly? Here are the present changes

Yes I can access using the localhost name from the server.
records-2.jpg

ASKER

I can not ping either the domainname.com or the mail.domainname.com

I didn't see the image before but I do now. What happens if you try to browse by the ip address of mail.domain.com?

https://{ipaddress}/owa

just saw the follow up comment, does the ping not resolve?

How long ago did you transfer the registrar?

ASKER CERTIFIED SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Based on what you have shown, domain.com and mail.domain.com will go to different IP addresses.

ASKER

Ok. what I have found it now it works with the WAN IP address / owa or /remote.

I need to get it back to working with the actual mail.domainname.com

How long ago was the move, if you change registrars you will have at least a 48 hour period where DNS and domain name resolution will not work properly. You may just need to be patient and it will work. If you are sure the A record is correct, but pinging does not resolve. Then you either have a DNS server issue or you just need to wait for the transfer to complete. Have you tried this from different networks?

ASKER

Ok why are they going to different IP addresses how do I fix it...Do I add a second A record of

Host - @ WANIP (actual address)

"Do I add a second A record of "

No, if all traffic on that domain name is going to the same server then you only need to change the @ record and it should be the WAN IP address of the server. Do you have a website at a different host for domain.com or www.domain.com?

Also, I am assuming nothing on the OWA server configuration changed during the registrar move. I also assume the OWA worked properly with the domain name before the registrar move. You should have the proper binding of IP and host header in IIS.

How long ago was the transfer to godaddy initiated?

Sorry, misread your last sentence. You are not adding a second A record for @, that is already there with the IP 184... Edit that A record to the one that is blacked out if you want all traffic to go to that IP. Keep the mail.domain.com A record because your MX record points to that.

ASKER

Everything worked properly prior to move.

The 184 ip address has nothing to do with our server it point to a godaddy server somewhere - godaddy had me remove it.

Domainname.com and mail.domainname.com have the same WAN IP (single server)

I currently have to A records:

@ = WAN IP address
Mail = WAN IP address

Do I need an "A host" record of mail = mail.domainname.com

No, A records can only point to IP addresses, not other A records. You should be all set. Just be patient until you can ping mail.domain.com or domain.com and verify it is the same IP you have in godaddy. Then you should be working.

How long ago did you do the transfer to godaddy?

ASKER

We change the records this morning. The transfer completed per go daddy on the 12th.

My goal is to be able to use the https://mail.domainname.com/owa all the phones are set to that for the company.

Here is the current setings for the records please see if I added one to many.

no company website exists - so no issue.....
records--3.jpg

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Remove your images if you are worried about your IP address. It is not blacked out completely.

ASKER

Could an administrator remove the last image please

ASKER

I have noticed that when I try to log in to the remote with the ip address my certificate doesn't work, so I can't get in which makes sense since it is for mail.domainname.com

Will that straighten out when the mail.domainname.com/owa works again????

Yes, the certificate is based on the fully qualified domain name, not the IP address. You have to browse OWA by mail.domainname.com to have it work without the certificate error. It will work once the domain name resolves.

ASKER

Pic for reference of the current mx and dns records the a host records (both) have the WAN IP address of the server. Are both records required
records-4-.jpg

I would leave as is. It will work perfectly fine with both records. No harm done.

ASKER

ok, I will wait and let it work........I will check over Saturday. Thank you to all.

ASKER

I can't say how appreciative I am of the help I received . Ken thank you so much....everything seems to be working this morning.

Great to hear, I checked this thread this morning and I was glad to see you were working. Take care.

ASKER

Thank you Ken.