Last night, it appeared to me that nslookup was resolving the name
graphiteops.com to IP address 72.52.4.95.
Today however it is no longer doing that, reporting instead:
% 127.0.0.1
Address:127.0.0.1#53
Non-authoritative answer:
graphiteops.com canonical name = graphiteops.com.
On Sep 14, 2011, at 4:35 PM, Ronald F. Guilmette wrote:
Is there a rule that says how a resolver should behave in cases where
there is both an A record and also a CNAME record for the same FQDN?
Which one should take precedence, the A or the CNAME?
RFC 1034, Section 3.6.2: If a CNAME RR is
In message 7d9b265c-36bf-40c1-9012-ac0a96fb8...@sackheads.org, you wrote:
On Sep 14, 2011, at 4:35 PM, Ronald F. Guilmette wrote:
Is there a rule that says how a resolver should behave in cases where
there is both an A record and also a CNAME record for the same FQDN?
Which one should take
On Sep 14, 2011, at 2:27 PM, Ronald F. Guilmette wrote:
The second part however seems to go more to my question, which is What is
the resolver supposed to do when some knucklehead breaks the rules and puts
a CNAME in with some other stuff?
Depends on which query one issued. The very next
Sigh: your mail server is blacklisting email from mac.com.
Begin forwarded message:
From: postmas...@mac.com
Date: September 14, 2011 2:53:05 PM PDT
To: cswi...@mac.com
Subject: Delivery Notification: Delivery has failed
This report relates to a message you sent with the following header
On 9/14/2011 5:52 PM, Chuck Swiger wrote:
On Sep 14, 2011, at 2:27 PM, Ronald F. Guilmette wrote:
The second part however seems to go more to my question, which is What is
the resolver supposed to do when some knucklehead breaks the rules and puts
a CNAME in with some other stuff?
Depends on
In message cf550bd6-ba85-4cb3-8b03-e4e1b0829...@mac.com, you wrote:
Sigh: your mail server is blacklisting email from mac.com.
Yes. Sorry about that. Too much spam from there and no indication
that anybody there gives a damn that that they gush spam. (If you
find anybody who does care,
7 matches
Mail list logo
