dig -t txt output variation

WBrown at e1b.org WBrown at e1b.org
Fri Mar 9 20:20:30 UTC 2012

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 me to look at the original post...  The owner of the domain 
needs to reconcile the two records (including included records) and verify 
all allowed servers are listed.  It's more of an email/spam filtering 
issue than a BIND problem.

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 addressee. If you are not the addressee (or the 
employee or agent responsible to deliver it to the addressee), or if this 
message has been addressed to you in error, you are hereby notified that 
you may not copy, forward, disclose or use any part of this message or any 
attachments. Please notify the sender immediately by return e-mail or 
telephone and delete this message from your system.

More information about the bind-users mailing list