[dns-operations] 2600::a1 (ns1-auth.sprintlink.net)
wpk at isc.org
Thu Feb 16 19:21:48 UTC 2017
W dniu 16.02.2017 o 20:05, Jim Popovitch pisze:
> On Thu, Feb 16, 2017 at 1:56 PM, David C Lawrence <tale at akamai.com> wrote:
>> Jim Popovitch writes:
>>> ~$ dig MX ups.com @ns1-auth.sprintlink.net
>>> ;; WARNING: recursion requested but not available
>>> I'm not always in the loop on things like this, how common is that?
>> Extremely. By default dig asks for recursive resolution, and it has
>> no sense whether the target @server is a resolver or authoritative
>> server. Most authoritative servers are properly not configured to
>> allow recursion, so when the answer comes back without the recursion
>> available flag set dig just makes a note of that.
>> You can use dig +norec to turn off the recursion desired flag in the
>> query, and that will make the warning go away.
> The issue is less about the norec, and more about the sprintlink NS
> servers (listed as the auth NS servers for ups.com) not returning RRs.
$ dig MX ups.com @ns1-auth.sprintlink.net |grep -A2 ";; ANSWER"
;; ANSWER SECTION:
ups.com. 300 IN MX 10 email-vip.ups.com.
ups.com. 300 IN MX 10 email2-vip.ups.com.
It is returning RRs
More information about the dns-operations