[juneau-lug] is army.mil breaking SPF or RFCs? James?

  • From: "Myron Davis" <myrond@xxxxxxxxxxx>
  • To: juneau-lug@xxxxxxxxxxxxx
  • Date: Tue, 13 Sep 2005 14:35:09 -0800 (AKDT)

Check out the following:

#dig txt us.army.mil @ns01.army.mil
; <<>> DiG 9.3.1 <<>> txt us.army.mil @ns01.army.mil
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 14171
;; flags: qr aa ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;us.army.mil.                   IN      TXT

;; Query time: 68 msec
;; SERVER: 140.153.43.44#53(140.153.43.44)
;; WHEN: Tue Sep 13 14:26:05 2005
;; MSG SIZE  rcvd: 29

What is up with the status: REFUSED line?  Are they allowed to do that?

This appears to be breaking SPF implementations since yesterday.. if they
don't like people quering TXT records why wouldn't they just respond with
something like this instead?  (just making up a response)

; <<>> DiG 9.3.1 <<>> txt us.army.mil @ns01.army.mil
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52334
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;us.army.mil.                   IN      TXT

;; AUTHORITY SECTION:
us.army.mil.            56   IN      SOA     ns01.army.mil.
root.us.army.mil. 2005070501 28800 7200 604800 56

;; Query time: 152 msec
;; SERVER: 140.153.43.44#53(140.153.43.44)
;; WHEN: Tue Sep 13 14:28:10 2005
;; MSG SIZE  rcvd: 74

Maybe James has some idea.. this is a change that has occurred in the last
few days.  I have no idea who to send the message to but they are
potentially breaking sending to mail servers implementing SPF records
properly with this change of behavior.

-Myron


------------------------------------
This is the Juneau-LUG mailing list.
To unsubscribe, send an e-mail to juneau-lug-request@xxxxxxxxxxxxx with the 
word unsubscribe in the subject header.

Other related posts: