Re: AXFR from Bind oddities

> The record as written by axfr-get
> :djgusa.com:16:Zv\075spf1\040include\072spf.messaging.microsoft.com\040include\072cmail1.com\040include\072sid.listrak.co
>    m\040-all:86400
> 
> The record as written by dig axfr
> djgusa.com.     86400   IN  TXT "v=spf1
> include:spf.messaging.microsoft.com include:cmail1.com
> include:sid.listrak.com -all"
> 
> The record from axfr-get shows (ignore the dbl quotes)
>  "v=spf1" as "v\075spf1", that is correct. So where does the "Z"
> character come from?

RFC 1035, Section 3.3: "<character-string> is a single length octet
followed by that number of characters. <character-string> is treated
as binary information, and can be up to 256 characters in length
(including the length octet)"

axfr-get output a "generic type 16" RR (:), not a TXT RR (').

Content is encoded as a RR <character-string>:
- first byte (Z) is the string length (90 bytes);
- next 90 bytes are the (binary representation of the) string value,
   where all non-alphanumeric chars are "\octal encoded".

-- 
Tullio Andreatta

Disclaimer: "Please treat this email message in a reasonable way, or we
     might get angry" ( http://www.goldmark.org/jeff/stupid-disclaimers )