Folks,
In a short lapse of time, I am getting different results for Twitter.
Firstly:
; <<>> DiG 9.10.4 <<>> twitter.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44773
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;twitter.com. IN A
;; ANSWER SECTION:
twitter.com. 10 IN A 199.16.156.230
twitter.com. 10 IN A 199.16.156.70
twitter.com. 10 IN A 199.16.156.102
twitter.com. 10 IN A 199.16.156.198
;; Query time: 55 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Oct 21 20:49:13 MUT 2016
;; MSG SIZE rcvd: 104
Then after a couple of minutes:
; <<>> DiG 9.10.4 <<>> twitter.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4648
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;twitter.com. IN A
;; ANSWER SECTION:
twitter.com. 1592 IN A 104.244.42.129
twitter.com. 1592 IN A 104.244.42.193
;; Query time: 104 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Oct 21 21:04:29 MUT 2016
;; MSG SIZE rcvd: 72
That would also explain why notifications from Twitter are landing in my
spam folder.
Received-SPF: temperror (google.com: error in processing during lookup of
b0095f27827ish=hacklog.mu_at_bounce.twitter.com: DNS error)
client-ip=199.16.156.177;
Authentication-Results: mx.google.com;
dkim=temperror (dns failure for signature) header.i=_at_twitter.com;
spf=temperror (google.com: error in processing during lookup of
b0095f27827ish=hacklog.mu_at_bounce.twitter.com: DNS error)
smtp.mailfrom=b0095f27827ish=hacklog.mu_at_bounce.twitter.com
Cheers,
--
Ish Sookun
Received on Fri Oct 21 2016 - 17:13:13 PST