A records for example.org returning 127.0.0.1!

[dkg@…]

weird, eh?

0 dkg@alice:~$ dig example.org
;; ->>HEADER<<- opcode: QUERY; status: NOERROR; id: 52814
;; Flags: qr aa rd ra; QUERY: 1; ANSWER: 1; AUTHORITY: 1; ADDITIONAL: 0

;; QUESTION SECTION:
;; example.org.        		IN	A

;; ANSWER SECTION:
example.org.        	10800	IN	A	127.0.0.1

;; AUTHORITY SECTION:
example.org.        	10800	IN	NS	example.org.

;; Received 59 B
;; Time 2016-11-13 16:09:49 KST
;; From 31.130.229.6@53(UDP) in 5.8 ms
0 dkg@alice:~$

  --dkg

[rob@…]

I just wanted to update you that we are working on your ticket this morning and I hope to have a resolution for you shortly.

Rob

[rob@…]

After reviewing the relevant RFCs we agree this default behavior of our server is incorrect. We will remove the special zones and allow normal resolution. This is scheduled to be completed after hours today.

Thanks for bringing it to our attention

[rob@…]

We have pushed the changes and removed the statements blocking resolution of example.com, test and invalid.
I will leave this ticket open through tomorrow, in case you see other issues related to this, or believe our fix was not correct.
Thanks again for bringing this to our attention.

Rob

[rob@…]

Having not heard any further issues, I am going to close this ticket. If you have any other questions or comments feel free to re-open this ticket or to create a new one. I hope we have resolved your issue satisfactorily.

Rob aka Alice

[Rick Alfvin]

Milestone renamed