Solved

DNS error spamcop IP address and DYNDNS

Posted on 2009-07-16
10
581 Views
Last Modified: 2012-05-07
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?  
0
Comment
Question by:fireguy1125
  • 6
  • 4
10 Comments
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 24870591
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
 
LVL 1

Author Comment

by:fireguy1125
ID: 24870697
Alan - sent you e-mail with screenshots.  thanks
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 24870974
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
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 24871081
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
 
LVL 1

Author Comment

by:fireguy1125
ID: 24871164
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
Highfive + Dolby Voice = No More Audio Complaints!

Poor audio quality is one of the top reasons people don’t use video conferencing. Get the crispest, clearest audio powered by Dolby Voice in every meeting. Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.

 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 24871611
Can you lose DynDNS and go back to your Domains DNS servers - would be a lot easier to manage?
0
 
LVL 1

Author Comment

by:fireguy1125
ID: 24871657
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
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 24871909
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
 
LVL 1

Author Comment

by:fireguy1125
ID: 24878578
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
 
LVL 76

Accepted Solution

by:
Alan Hardisty earned 500 total points
ID: 24880094
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

Featured Post

What Is Threat Intelligence?

Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

Join & Write a Comment

Suggested Solutions

Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
In this video we show how to create a Distribution Group in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >>…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now