This question may be covered in another thread, but I am not sure what to use as a search term to find it, but what I am needing to do is get my client removed from blacklists after a machine of there's was unknowingly to them sending out spam. The machine has since been reformatted and patched.
I am just not wanting to cause a DNS loop or downtime to my client, but I want to set this up so we can be removed from the remaining blacklists. The remaining blocking are FIVETEN sites. I had our ISP set the reverse record on their end to point correctly for our public IP to point back to our domain name. What FIVETEN is saying now is:
"Also, none of those names have an A record pointing to the original xxx.xxx.xxx.xxx. That needs to be fixed" (xxx.xxx.xxx.xxx being our public IP).
I believe I can do this from our host and just point the * wildcard record to our DNS server's public IP, but what I am concerned about is that we are not serving our own website. Currently if people type www.domainname.com
or just domainname.com, they get our website because the website/hosting company is using a * wildcard for all traffic that I haven't set a custom DNS on their end for. I am forarding three custom names including our mail traffic. What I think I need to do is point all traffic from the host to our own server via our public IP and then just set A records in our server's DNS to point the www traffic back to the web host. I am not 100% familiar with A records, but if I want this to work correctly what is the and easiest way to preserve what is in place now with people typing just our domainname or www.domainname?