Oh wow, don't I feel like a moron! Heh. As it turns out, I added the
zone and everything but I never actually changed the nameservers for the
domain on godaddy's end. I couldn't see the problem myself because both
my office and my home networks are both configured to use my own DNS
servers for resolution... so of course all DIG, NSLOOKUP, HOST, etc
attempts by me looked fine.
Well thanks guys, you've been a big help! lol
Stephen Gran wrote:
> On Thu, Jul 17, 2008 at 11:27:20AM -0400, Brandon Phelps said:
>
>> Ah sorry guys. The domain in question is pickhoops.com - my primary
>> domain is dellsports.com. dellsports.com works perfectly, I am able to
>> receive mail from any host. pickhoops.com is the one that doesn't want
>> to cooperate. I have an MX record setup on pickhoops.com with a
>> priority of 10, set to deliver to mail.dellsports.com., which also
>> happens to be on the same box, and is the same MX record dellsports.com
>> uses.
>>
>
> No, you don't:
> steve@vancouver:~$ host -t mx pickhoops.com
> pickhoops.com MX 50 mailwash43.pair.com
> steve@vancouver:~$ host -t mx dellsports.com
> dellsports.com MX 10 mail.dellsports.com
> steve@vancouver:~$ host mailwash43.pair.com
> mailwash43.pair.com A 66.39.2.43
> steve@vancouver:~$ host mail.dellsports.com
> mail.dellsports.com A 209.136.196.42
>
> As suspected, DNS is busted.
>
