Thanks for the suggestions, Jon... I must confess, I know very little about DNS (as you can tell). That's the main reason I use GoDaddy's admin tool and default parked nameservers as my DNS servers.
In the A records, I did have a Host name "mail" that "Points To 66.79.46.138" (my only IP). I say I "did have" because I figured it was unnecessary at least and harmful at best, so I removed the "mail" subdomain from the A records completely. Correct this to do? Also, in the MX records, I did have an entry for "Host @ Goes to mail.whitestonemedia.com", which based on what's happening in my DNS and your comments, I thought would be wrong, too, since it's a wildcard entry for the domain, so I removed that entry... right thing to do? Now in the MX records, there is "Host mail Goes To mail.whitestonemedia.com" "Host smtp Goes To mail.whitestonemedia.com" "Host pop Goes To mail.whitestonemedia.com" I don't use smtp and pop in the domain name to access my mail, only mail.whitestonemedia.com, but figured it wouldn't hurt to have those in there for reference... so would this seem correct? One other thing...I have no access to Reverse DNS records or settings through GoDaddy. I actually had to call my ISP who assigned my IP to get them to change their rDNS settings from their domain to mine. I did that so my rDNS would match and would help me get off some email blacklists. Perhaps my ISP got the rDNS wrong when I called them and that's why it's showing up as "mail.whitestonemedia.com"? But why would these settings, if incorrect, only affect only one customer? Why not all people trying to access my websites? Enough questions for now. Thanks for your help! Rick -----Original Message----- From: Jon Clausen [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 28, 2006 1:19 AM To: CF-Talk Subject: Re: OT: DNS Problems... Rick, A couple of things to check (I'm giving you some examples using IIS so you might need to find something equivalent in GoDaddy's DNS admin if you haven't done any of your DNS work on the server side): You may have created a reverse-pointer record when you were modifying your DNS. To fix, you may need to change the DNS record again. If there is a box that says something like "Update Associated Pointer Record, make sure that is checked. ( You may want to do the same with the mail record you changed as well). If you have visibility to the Reverse Lookup Zones on the server, you may also want to look in your Reverse Lookup Zones for the subnet of IP's on the server for any conflicting records between the two. You can always nuke the records and recreate if you start seeing conflicts. Another thing to check is whether you have any of the sites on the server (especially the mail domain) set up with a blank Host Header value (or possibly a blank (wildcard domain) mail or A record in the GoDaddy admin). If you have more than one, it can cause these types of issues (as I've found out the hard way). Lastly, have your client open a Windows Terminal (or Network Utility on a Mac) and either "tracert yoursite.com" or Traceroute>yoursite.com respectively. You can see if any of the hops that are being made are giving you any clues to where the DNS problem is occurring. (Note - this will probably only be helpful if your server has more than one IP assigned, but even so, it might give you some information) I would also suggest contacting GoDaddy's support team, they may be able to find the problem faster than you can. HTH, Jon ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:261843 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
