Public DNS Conflict with GoDaddy

One of my clients has a SBS 2003 running Exchange with @pdslex.com as email extensions.
They are having problems with mail not getting to them from other email users.

Outside users will send email and it comes back right away.  This has been going on for a few weeks that we know of.  Not everyone is blocked, as  a matter of fact most email, probably 95% goes through just fine.
So because of someone's advice from this site on another question I had, I ran the pdslex.com through DNSStuff.com and got this result: http://i55.photobucket.com/albums/g142/chrisdfoley/DNSStuffReport.png (everything else on this report was clear.)

This domain is registered through GoDaddy.  So I went to GoDaddy's site to remove the bad MX listing.  There is no record listed that has a host as the IP address.  Here is the GoDaddy screen: http://i55.photobucket.com/albums/g142/chrisdfoley/GoDaddyDNS.png (the top was cut off but the first section is the A records.)

I have called GoDaddy 3 x's and spoken to 5 different people and they all say the same thing.  It isn't their problem and that bad MX record does not exist.  But according to DNSStuff.com it does.

Can anyone point me in another direction maybe of what I have to do to get this IP removed as a HOST name from an MX listing that does not exist.

FYI, I have 3 other Exchange servers set up exactly the same for other clients and they come back perfect through DNSStuff.com so I'm pretty sure the setup is right.
LuukerAsked:
Who is Participating?
 
LuukerConnect With a Mentor Author Commented:
Problem solved.  Switching to Network Solutions removed the faulty listing.  I have a few other minor things to work out but at least the big ones are fixed.  Everyone, thanks for your input!
0
 
DewFreakCommented:
Luuker - There is a problem in the DNS server.  I have checked it from a couple different angles.  If godaddy will not do anything I would suggest trying to remove your existing MX record and re adding.  Also could try to change to preference to 10 to see if anything shakes loose.



> server 4.2.2.1
Default Server:  vnsc-pri.sys.gtei.net
Address:  4.2.2.1

> set type=mx
> pdslex.com
Server:  vnsc-pri.sys.gtei.net
Address:  4.2.2.1

Non-authoritative answer:
pdslex.com      MX preference = 0, mail exchanger = 74.223.133.174
pdslex.com      MX preference = 0, mail exchanger = mail.pdslex.com
>
0
 
bevhostCommented:
Your domain seems to have two MX records. One is correct and one is wrong.
Since most mails servers try both mx's then you mail comes through when they try the good one.

This one is WRONG (it's not even right for an IP address which shouldn't have a dot on the end)
pdslex.com.             3600    IN      MX      0 74.223.133.174.

This one is CORRECT
pdslex.com.             3600    IN      MX      0 mail.pdslex.com.

If they refuse to fix it, then you may have little choice but to change registrars.  
I had no idea that godaddy was that hopeless.

If you do want to transfer you'll have to unlock it first.
# dig -tany pdslex.com @ns51.domaincontrol.com
 
; <<>> DiG 9.3.3rc2 <<>> -tany pdslex.com @ns51.domaincontrol.com
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17809
;; flags: qr aa rd; QUERY: 1, ANSWER: 7, AUTHORITY: 0, ADDITIONAL: 1
 
;; QUESTION SECTION:
;pdslex.com.                    IN      ANY
 
;; ANSWER SECTION:
pdslex.com.             86400   IN      SOA     ns51.domaincontrol.com. dns.jomax.net. 2008060200 28800 7200 604800 86400
pdslex.com.             3600    IN      MX      0 74.223.133.174.
pdslex.com.             3600    IN      NS      ns51.domaincontrol.com.
pdslex.com.             3600    IN      NS      ns52.domaincontrol.com.
pdslex.com.             3600    IN      TXT     "v=spf1 a mx ptr ~all"
pdslex.com.             3600    IN      A       74.223.133.174
pdslex.com.             3600    IN      MX      0 mail.pdslex.com.
 
;; ADDITIONAL SECTION:
mail.pdslex.com.        3600    IN      A       74.223.133.174
 
;; Query time: 195 msec
;; SERVER: 216.69.185.26#53(216.69.185.26)
;; WHEN: Sat Oct  4 08:37:12 2008
;; MSG SIZE  rcvd: 267

Open in new window

0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
LuukerAuthor Commented:
I removed all the MX records from GD.  I will wait an hour or two and will re-create the record with pref=10 and see what happens.
I'll keep ya' posted on my results!
0
 
LuukerAuthor Commented:
I think their tech support wanted to help, but wasn't sure what they could do.  I thought maybe there was a stale record or something old that just needed to be flushed but they said they couldn't do that, or maybe just wouldn't IDK.
I will change if I have to but I was trying to keep all my domains (29) under the same roof.
I am doing what DewFreak recommended first to see if that helps.  If it doesn't, then the next step is.........don't know yet!
Thanks for the replies guys!!  Super fast!!
0
 
bevhostCommented:
The Good one is gone but the bad one is still there....

; <<>> DiG 9.3.3rc2 <<>> -tany pdslex.com @ns51.domaincontrol.com
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5207
;; flags: qr aa rd; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 0
 
;; QUESTION SECTION:
;pdslex.com.                    IN      ANY
 
;; ANSWER SECTION:
pdslex.com.             86400   IN      SOA     ns51.domaincontrol.com. dns.jomax.net. 2008060200 28800 7200 604800 86400
pdslex.com.             3600    IN      A       74.223.133.174
pdslex.com.             3600    IN      MX      0 74.223.133.174.
pdslex.com.             3600    IN      NS      ns51.domaincontrol.com.
pdslex.com.             3600    IN      NS      ns52.domaincontrol.com.
pdslex.com.             3600    IN      TXT     "v=spf1 a mx ptr ~all"
 
;; Query time: 196 msec
;; SERVER: 216.69.185.26#53(216.69.185.26)
;; WHEN: Sat Oct  4 08

Open in new window

0
 
DewFreakCommented:
Yep - the bad one is still there.  Might have to disable the DNS with godaddy temporarily so it can flush from their servers and house the domain somewhere else.  Maybe now would be a good time to call back to their support and show them that you have removed all MX records and the phatom is still there.
0
 
BrentDevOpsCommented:
Just a suggestion.. try recreating the bad record with the same name but point it to the correct server.
0
 
LuukerAuthor Commented:
When I try to re-create the bad record with the right IP, GoDaddy's site will not let me do it.  I get an error telling me it is incorrect.
I am going to contact support while I have this out.  I can't keep it down for too long.
0
 
BrentDevOpsCommented:
What happens when you use the reset features in the the TDC?
0
 
LuukerAuthor Commented:
Reset features in the TDC?
0
 
DewFreakCommented:
Did you ever get anywhere with support?  
0
 
LuukerAuthor Commented:
No.  They are telling me someone else (another registrar) has to have something listed in their servers because it is not on their (GD) end.
I asked them how that was possible, but they couldn't give me an answer.  They pretty much said it isn't possible, but by admitting it isn't possible they would have to agree it is their fault and they will not accept responsibility.
I feel like I am running in circles with them over this.  Now I am starting to have doubts about their sincerity in this.  Seems like as soon as I ask questions that are a little tougher to answer, they all of a sudden are in a hurry to get off the phone.
Sorry, this isn't a GD bashing forum and I am still trying to solve a problem.  I am going to talk to my boss and see about moving this domain to another registrar.  Does anyone know of a GOOD one??  Seems like I have used GD for so long I don't know who else is out there that is decent.
0
 
LuukerAuthor Commented:
OK.  Domain is set to transfer out to Network Solutions 10/10.  We will see if the transfer removes the bad record.
0
 
DewFreakCommented:
It's not a registrar issue, it's in the DNS but you happen to be using your registrar's DNS services.  There are other DNS providers out there.  No need to do a registrar change.  Let me know man, I could house your zone until you get the bugs out.
0
All Courses

From novice to tech pro — start learning today.