On 3/9/2012 5:42 PM, Mark Andrews wrote:
In messageblu156-w227d2d615494770d415a40f3...@phx.gbl, M. Meadows writes:
We've noticed that the following command gets a variable result:
dig -t txt exacttarget.com @ns2.exacttarget.com +short
We get 2 results from this. Seems to be somewhat random.
We've noticed that the following command gets a variable result:
dig -t txt exacttarget.com @ns2.exacttarget.com +short
We get 2 results from this. Seems to be somewhat random. They are:
v=spf1 a mx ip4:207.250.79.101 ip4:207.67.98.192/27 ip4:72.18.216.98
include:cust-spf.exacttarget.com
sun-guru wrote on 03/09/2012 01:45:33 PM:
Is this a BIND bug?
Check ARM for RRSet Ordering.
Confidentiality Notice:
This electronic message and any attachments may contain confidential or
privileged information, and is intended only for the individual or entity
identified above as the
Thanks to both of you for your feedback.
I see the rrset ordering explanation in the arm.
Good information.
To: sun-g...@live.com
CC: bind-users@lists.isc.org
Subject: Re: dig -t txt output variation
From: wbr...@e1b.org
Date: Fri, 9 Mar 2012 13:54:47 -0500
sun-guru wrote on 03/09
On 3/9/2012 2:24 PM, M. Meadows wrote:
Thanks to both of you for your feedback.
I see the rrset ordering explanation in the arm.
Good information.
Don't base anything on RRset ordering.
Be sure that the application is able to handle the random order -- you
never know who owns the
Alan wrote on 03/09/2012 02:38:25 PM:
Don't base anything on RRset ordering.
Be sure that the application is able to handle the random order -- you
never know who owns the intermediate caching servers, so you will never
know the order even if you fix it on the authoritative.
That prompted
In message blu156-w227d2d615494770d415a40f3...@phx.gbl, M. Meadows writes:
We've noticed that the following command gets a variable result:
dig -t txt exacttarget.com @ns2.exacttarget.com +short
We get 2 results from this. Seems to be somewhat random. They are:
v=3Dspf1 a mx
7 matches
Mail list logo