I had a call this morning from a customer who wanted me to come down because their mail server was broken. They had experienced an ISP outage, which subsequently was fixed, but their mail server wasn't getting anything still.
I was actually ready to go out the door when I thought to just double check reality, and that check kept me sitting right here:
$ dig +short xyz.com mx
10 mail.xyz.com.xyz.com.
20 mail2.xyz.com.xyz.com.
Ooops.. that certainly can't be right. I told the client that his MX records were munged, but he came back with a screen from the DNS providers tools that seemed to show them correctly. It looked something like this:
MX Records |
---|
mail.xyz.com |
mail2.xyz.com |
I told him to try taking out the ".xyz.com", but he said the tool told him that was invalid.. at which point I smiled to myself and knew what he had to do.
Do you know what he needed to do to fix this?
Got something to add? Send me email.
More Articles by Anthony Lawrence © 2011-04-28 Anthony Lawrence
Educate the children and it won't be necessary to punish the men. (Pythagoras)
Printer Friendly Version
Lazy DNS Copyright © October 2007 Tony Lawrence
Have you tried Searching this site?
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more.
Contact us
Printer Friendly Version