fireguy1125
asked on
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?
"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?
ASKER
Alan - sent you e-mail with screenshots. thanks
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?
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?
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.
This is the only Blacklist I can find you on - so I would not be unduly worried.
ASKER
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
CNAME cannot be created with label that is equal to zone name or in use for another record type
Can you lose DynDNS and go back to your Domains DNS servers - would be a lot easier to manage?
ASKER
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.
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
ASKER
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?
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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Are you not able to fix your IP address? - it makes life much easier.
Thanks
Alan