As a coworker showed me. I have got my mail server MX record all messed up. I cannot find where the double domain is set in Linux Redhat's interface or within the zone text.
If anyone can point me in the right direction, I'd appreicate it.

; <<>> DiG 9.2.1 <<>> mydomain.com mx
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18037
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;mydomain.com. IN MX

;; ANSWER SECTION:
mydomain.com. 76347 IN MX 1 mail.mydomain.com.mydomain.com.

;; AUTHORITY SECTION:
mydomain.com. 28114 IN NS ns2.mydomain.com.
mydomain.com. 28114 IN NS ns1.mydomain.com.

;; ADDITIONAL SECTION:
ns1.mydomain.com. 162747 IN A 63.226.xxx.xx
ns2.mydomain.com. 162747 IN A 63.226.xxx.xx

(The numbers and names have been changed to protect the clueless)

Oh yeah. where is DiG getting it's info? I have changed this recored a dozen ways and it is not changing the DiG output. I figure it's cached some where. Any way to make it refresh or do I have to wait?

Whatever name server he's doing the dig against probably has the information cached; however, if you're doing a dig on your own server and getting the same results, then you probably forgot to restart named after making changes. You'll need to kill -HUP the pid of named in order for it to load the changes. Oh, and make sure that you increment the zone serial number. Most folks use a format like this: yyyymmddnn where nn = the number of changes you have made today. ex: 2003121904 would mean the last change you made was the fourth change on Dec 19, 2003. If you don't increment the serial, named will ignore it (and thus not load the new data).