[exim] dig and backslash - was Re: DKIM signing with the i= …

Top Page
Delete this message
Reply to this message
Author: Andrew C Aitchison
Date:  
To: Jasen Betts
CC: exim-users
Old-Topics: Re: [exim] DKIM signing with the i= (Identity) tag/header
Subject: [exim] dig and backslash - was Re: DKIM signing with the i= (Identity) tag/header
On Wed, 23 Nov 2016, Jasen Betts wrote:

>> The output of dig should have one backslash in there, the actual record
>> should have none indeed.
>
> dig txt 20120113._domainkey.gmail.com 8.8.4.4 | grep ^20120113
> 20120113._domainkey.gmail.com. 281 IN    TXT    "k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA1Kd87/UeJjenpabgbFwh+eBCsSTrqmwIYYvywlbhbqoo2DymndFkbjOVIPIldNs/m40KF+yzMn1skyoxcTUGCQs8g3FgD2Ap3ZB5DekAo5wMmk4wimDO+U8QzI3SD0" "7y2+07wlNWwIt8svnxgdxGkVbbhzY8i+RQ9DpSVpPbF7ykQxtKXkv/ahW3KjViiAH+ghvvIhkx4xYSIc9oSwVmAl5OctMEeWUwg8Istjqz8BZeTWbf41fbNhte7Y+YqZOwq1Sd0DbvYAD9NOZK9vlfuac0598HY+vtSBczUiKERHv1yRbcaQtZFh5wtiRrN04BLUTD21MycBX5jYchHjPY/wIDAQAB"

>
> No backslashes. Am I doing something wrong.
>
> I, too seem to recall backslashes from dig in the past, but I can't
> provoke them today.


On a Scientific Linux (Red Hat) 6 machine I *do* see the back-slash:
# dig -v
DiG 9.8.2rc1-RedHat-9.8.2-0.47.rc1.el6_8.3

# dig txt 20120113._domainkey.gmail.com 8.8.4.4

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.47.rc1.el6_8.3 <<>> txt
20120113._domainkey.gmail.com 8.8.4.4
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1277
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;20120113._domainkey.gmail.com. IN      TXT


;; ANSWER SECTION:
20120113._domainkey.gmail.com. 300 IN   TXT     "k=rsa\; 
p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA1Kd87/UeJjenpabgbFwh+eBCsSTrqmwIYYvywlbhbqoo2DymndFkbjOVIPIldNs/m40KF+yzMn1skyoxcTUGCQs8g3FgD2Ap3ZB5DekAo5wMmk4wimDO+U8QzI3SD0" 
"7y2+07wlNWwIt8svnxgdxGkVbbhzY8i+RQ9DpSVpPbF7ykQxtKXkv/ahW3KjViiAH+ghvvIhkx4xYSIc9oSwVmAl5OctMEeWUwg8Istjqz8BZeTWbf41fbNhte7Y+YqZOwq1Sd0DbvYAD9NOZK9vlfuac0598HY+vtSBczUiKERHv1yRbcaQtZFh5wtiRrN04BLUTD21MycBX5jYchHjPY/wIDAQAB"


;; Query time: 25 msec
;; SERVER: 194.168.4.100#53(194.168.4.100)
;; WHEN: Wed Nov 23 12:08:02 2016
;; MSG SIZE rcvd: 462

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 34630
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;8.8.4.4.                       IN      TXT


;; AUTHORITY SECTION:
.                       9434    IN      SOA     a.root-servers.net. 
nstld.verisign-grs.com. 2016112201 1800 900 604800 86400


;; Query time: 12 msec
;; SERVER: 194.168.4.100#53(194.168.4.100)
;; WHEN: Wed Nov 23 12:08:02 2016
;; MSG SIZE rcvd: 100


This is on a Scientific Linux (Red Hat) 6 machine;
I also get the "\;" on a machine using a completely different 
nameserver, running
     Ubuntu 14.04.5 LTS, Trusty Tahr
with
# dig -v
DiG 9.9.5-3ubuntu0.10-Ubuntu


...

Are we using different nameservers or is it just that
I have old versions of dig ... ?

--
Andrew C Aitchison