DNS error spamcop IP address and DYNDNS

a query of our public IP address on spamcop.net shows that we have a DNS error it says:

"68.x.x.x is mail.company.org but mail.company.org is 204.x.x.x instead of 68.x.x.x"

I believe this to be an issue with the way our DNS is setup:

our 68.x.x.x is our public IP with our ISP.  It is NATed for everything, web, e-mail, etc.  Internally we have a Windows 2003 DNS server for our network, with domain forwarders setup to point to our ISP DNS servers (167.x.x.x).

We have Custom DNS service hosted on DynDNS.  Where the following are listed:

company.org           Type A     68.x.x.x.x
company.org           Type MX   5 company.org
mail.company.org    WebHop   https://outlook.company.org/exchange

The 204.x.x.x address is that of the DNS servers at DynDNS, and apparently they dont' match up to DNS servers of our 68.x.x.x IP.

How can we fix this so our DNS is correct?  There is currently NO problem, e-mails are sent and received fine, it just that some anti-spam servers may delay our e-mails as a result of the IP address differences for the mail.company.org name.  I believe that we kept DynDNS for our DNS incase we ever have the need to switch ISPs that we can keep the same DNS.  I'm assuming some changes will need to be made on the server end to somehow point to DynDNS (204.x.x.x) as opposed to our ISP's DNS (167.x.x.x)

What modifications should be made and to what in order to resolve this issue?  
LVL 1
fireguy1125Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Alan HardistyCo-OwnerCommented:
Can you email me your domain and IP details so that I can understand clearly what your problem is and provide you with the correct action to take.  You will find me email address details cryptically in my profile.
Are you not able to fix your IP address? - it makes life much easier.
Thanks
Alan
0
fireguy1125Author Commented:
Alan - sent you e-mail with screenshots.  thanks
0
Alan HardistyCo-OwnerCommented:
Thanks Greg.
If I do an nslookup on mail.yourcompany.com I get 204.13.xxx.xxx
Your MX record (A record) is currently just set as yourdomain.com - if you add a CNAME record to your DNS called MAIL and point this to yourdomain.com then this should clear up the Spamcop issue.
Do you have access to your DNS settings?
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

Alan HardistyCo-OwnerCommented:
Also - according to Spamcop - you have been sending them spam within the last 24 hours.
This is the only Blacklist I can find you on - so I would not be unduly worried.
0
fireguy1125Author Commented:
I attempted to do that on DynDNS but it gives me an error saying:

CNAME cannot be created with label that is equal to zone name or in use for another record type
0
Alan HardistyCo-OwnerCommented:
Can you lose DynDNS and go back to your Domains DNS servers - would be a lot easier to manage?
0
fireguy1125Author Commented:
I wouldn't know where to begin to make this a smooth transition?  As you can see by the screenshots I e-mailed you there are several hosts configured in DynDNS as well as some webhops.
0
Alan HardistyCo-OwnerCommented:
Yes - could be interesting - can you call DynDNS to get advice?  I don't want to screw things up for you but you need to setup mail.yourdompany.com to be your MX CNAME not just yourcompany.com
0
fireguy1125Author Commented:
Ok, so further investigation...we are using DynDNS as a webhop, so that way any inquiries to mail.company.org get automatically forwarded to https://outlook.company.org/exchange.  We did this for simplicity of accessing OWA.  Since the webhop is done at DynDNS, their servers resolve during an NSLOOKUP.

It seems the only way of getting around this is somehow configuring it on our e-mail server end, changing the https://outlook.company.org/exchange to http://mail.company.org/, that way we can eliminate the use of DynDNS as the web hop, and instead put in an A record for the 68.x.x.x IP.  -How does that sound? Any ideas how to do this?
0
Alan HardistyCo-OwnerCommented:
Have a read through this document which details what to do internally and then you can lose the DynDNS settings.
http://technet.microsoft.com/en-us/library/aa998359.aspx 
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.