> $ 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 Nam
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
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
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
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.
>
>
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.INMX1 70.62.90.185"
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:
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 fo
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://
9 matches
Mail list logo
