I'm not sure why this started, but apparently I'm having a DNS problem. Yesterday mail started bouncing with this error: 450 Unable to find obrien-pifer.com
I think the messages eventually get delivered, but not sure. I guess I'll see if this one makes the list.
I checked my domain using http://www.checkdns.net/ and it gives me a couple warnings. One is that there's no MX record, but there is.
I use a smarthost for sending mail.
My DNS records are: http://www.obrien-pifer.com/mydns.txt
Anyone see any problems in my DNS records?
Thanks, James
James Pifer wrote: ...
Anyone see any problems in my DNS records?
Doesn't look right to me:
$ nslookup
set type=mx obrien-pifer.com
Server: 127.0.0.1 Address: 127.0.0.1#53
Non-authoritative answer: *** Can't find obrien-pifer.com: No answer
Authoritative answers can be found from:
$ nslookup
www.obrien-pifer.com
Server: 127.0.0.1 Address: 127.0.0.1#53
Non-authoritative answer: www.obrien-pifer.com canonical name = obrien-pifer.com. Name: obrien-pifer.com Address: 70.62.90.185
Mogens
hi James there is a MX recond for mail.obrien-pifer.com, not for obrien-pifer.com: bash-3.2$ dig obrien-pifer.com any
; <<>> DiG 9.5.1-P1-RedHat-9.5.1-1.P1.fc10 <<>> obrien-pifer.com any ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10894 ;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 4, ADDITIONAL: 4
;; QUESTION SECTION: ;obrien-pifer.com. IN ANY
;; ANSWER SECTION: obrien-pifer.com. 36647 IN A 70.62.90.185 obrien-pifer.com. 36647 IN NS porky.obrien-pifer.com. obrien-pifer.com. 36647 IN NS sammy.obrien-pifer.com. obrien-pifer.com. 36647 IN NS ns1.obrien-pifer.com. obrien-pifer.com. 36647 IN NS ns2.obrien-pifer.com.
;; AUTHORITY SECTION: obrien-pifer.com. 36647 IN NS ns2.obrien-pifer.com. obrien-pifer.com. 36647 IN NS porky.obrien-pifer.com. obrien-pifer.com. 36647 IN NS sammy.obrien-pifer.com. obrien-pifer.com. 36647 IN NS ns1.obrien-pifer.com.
;; ADDITIONAL SECTION: ns1.obrien-pifer.com. 36647 IN A 70.62.90.185 ns2.obrien-pifer.com. 36647 IN A 70.62.90.185 porky.obrien-pifer.com. 36647 IN A 70.62.90.185 sammy.obrien-pifer.com. 36647 IN A 70.62.90.185
;; Query time: 3 msec ;; SERVER: 192.168.159.1#53(192.168.159.1) ;; WHEN: Sat Mar 7 13:53:39 2009 ;; MSG SIZE rcvd: 246
bash-3.2$ dig mail.obrien-pifer.com any
; <<>> DiG 9.5.1-P1-RedHat-9.5.1-1.P1.fc10 <<>> mail.obrien-pifer.com any ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31815 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4
;; QUESTION SECTION: ;mail.obrien-pifer.com. IN ANY
;; ANSWER SECTION: mail.obrien-pifer.com. 38400 IN MX 1 70.62.90.185.obrien-pifer.com.
;; AUTHORITY SECTION: obrien-pifer.com. 36592 IN NS ns1.obrien-pifer.com. obrien-pifer.com. 36592 IN NS ns2.obrien-pifer.com. obrien-pifer.com. 36592 IN NS porky.obrien-pifer.com. obrien-pifer.com. 36592 IN NS sammy.obrien-pifer.com.
;; ADDITIONAL SECTION: ns1.obrien-pifer.com. 36592 IN A 70.62.90.185 ns2.obrien-pifer.com. 36592 IN A 70.62.90.185 porky.obrien-pifer.com. 36592 IN A 70.62.90.185 sammy.obrien-pifer.com. 36592 IN A 70.62.90.185
;; Query time: 140 msec ;; SERVER: 192.168.159.1#53(192.168.159.1) ;; WHEN: Sat Mar 7 13:54:34 2009 ;; MSG SIZE rcvd: 208
bash-3.2$
Br, Louis
On Sat, 2009-03-07 at 08:18 -0500, James Pifer wrote:
I'm not sure why this started, but apparently I'm having a DNS problem. Yesterday mail started bouncing with this error: 450 Unable to find obrien-pifer.com
I think the messages eventually get delivered, but not sure. I guess I'll see if this one makes the list.
I checked my domain using http://www.checkdns.net/ and it gives me a couple warnings. One is that there's no MX record, but there is.
I use a smarthost for sending mail.
My DNS records are: http://www.obrien-pifer.com/mydns.txt
Anyone see any problems in my DNS records?
Thanks, James
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Hi James,
MX-records must point to A-records and not to IP adresses. A "dig -t AXFR obrien-pifer.com @ns1.obrien-pifer.com | grep MX" returns: mail.obrien-pifer.com. 38400 IN MX 1 70.62.90.185.obrien-pifer.com.
Whereas you list "mail.obrien-pifer.com. IN MX 1 70.62.90.185" in your config.
So your setup is invalid because: - you're pointing your one and only MX record directly to an IP - since it is interpreted as host and missing a "." at the end it's expanded to "70.62.90.185.obrien-pifer.com." which doesnt exist - it's a MX record for mail.obrien-pifer.com and not obrien-pifer.com
Your whole definition of the MX record looks goofy to me, dont want to sound like an a.. but you better (re)read some tutorials on setting up DNS. I really wonder if you receive the reply at all.
Regards, Thomas
On Sat, 2009-03-07 at 14:01 +0100, Joebstl Thomas wrote:
Hi James,
MX-records must point to A-records and not to IP adresses. A "dig -t AXFR obrien-pifer.com @ns1.obrien-pifer.com | grep MX" returns: mail.obrien-pifer.com. 38400 IN MX 1 70.62.90.185.obrien-pifer.com.
Whereas you list "mail.obrien-pifer.com. IN MX 1 70.62.90.185" in your config.
So your setup is invalid because:
- you're pointing your one and only MX record directly to an IP
- since it is interpreted as host and missing a "." at the end it's
expanded to "70.62.90.185.obrien-pifer.com." which doesnt exist
- it's a MX record for mail.obrien-pifer.com and not obrien-pifer.com
Your whole definition of the MX record looks goofy to me, dont want to sound like an a.. but you better (re)read some tutorials on setting up DNS. I really wonder if you receive the reply at all.
Regards, Thomas
Thomas,
Can you tell me if it looks better now?
Thanks, James
James Pifer wrote on Sat, 07 Mar 2009 11:07:00 -0500:
Can you tell me if it looks better now?
It's better, but still:
- as the MX is the same as your domain name you do not need an MX - as all your hosts point to the same IP you can just use a wildcard - as I'm sure you don't change your hosts several times a day you can up the TTL to a more reasonable time like 86400 (=a day) - having four ns records all point to the same IP is just, uhm, pointless
Kai
Kai Schaetzl wrote:
- as the MX is the same as your domain name you do not need an MX
It is good to always have an MX.
- having four ns records all point to the same IP is just, uhm, pointless
Can make it easier to separate workloads and move them to different servers later.
//Morten
Kai Schaetzl wrote:
It's better, but still:
- as the MX is the same as your domain name you do not need an MX
- as all your hosts point to the same IP you can just use a wildcard
- as I'm sure you don't change your hosts several times a day you can up
the TTL to a more reasonable time like 86400 (=a day)
- having four ns records all point to the same IP is just, uhm, pointless
worse than pointless, its ugly. in the event your server is down and not responding, a lookup server will try it 4 times as many times as it otherwise would.
the only NS records that should be in your zone are exactly the same as the ones in the registrar for the domain.
$ whois obrien-pifer.com ... Domain Name: OBRIEN-PIFER.COM Registrar: WILD WEST DOMAINS, INC. Whois Server: whois.wildwestdomains.com Referral URL: http://www.wildwestdomains.com Name Server: NS1.OBRIEN-PIFER.COM Name Server: NS2.OBRIEN-PIFER.COM
Server Name: NS1.OBRIEN-PIFER.COM IP Address: 70.62.90.185 Registrar: WILD WEST DOMAINS, INC. Whois Server: whois.wildwestdomains.com Referral URL: http://www.wildwestdomains.com
Server Name: NS2.OBRIEN-PIFER.COM IP Address: 70.62.90.185 Registrar: WILD WEST DOMAINS, INC. Whois Server: whois.wildwestdomains.com Referral URL: http://www.wildwestdomains.com
I'm surprised the registrar let you register two HOST names for the same IP, they aren't supposed to do that.
$ whois obrien-pifer.com ... Domain Name: OBRIEN-PIFER.COM Registrar: WILD WEST DOMAINS, INC. Whois Server: whois.wildwestdomains.com Referral URL: http://www.wildwestdomains.com Name Server: NS1.OBRIEN-PIFER.COM Name Server: NS2.OBRIEN-PIFER.COM
Server Name: NS1.OBRIEN-PIFER.COM IP Address: 70.62.90.185 Registrar: WILD WEST DOMAINS, INC. Whois Server: whois.wildwestdomains.com Referral URL: http://www.wildwestdomains.com
Server Name: NS2.OBRIEN-PIFER.COM IP Address: 70.62.90.185 Registrar: WILD WEST DOMAINS, INC. Whois Server: whois.wildwestdomains.com Referral URL: http://www.wildwestdomains.com
I'm surprised the registrar let you register two HOST names for the same IP, they aren't supposed to do that.
I removed the other two NS records. I also raised the TTL as suggested.
Thanks for all the help.
James