Hello,
I try to raise my points and continuously test my IPv6 configuration stability with daily tests... and so far it worked very well.
But recently, the Submit an IPv6 DIG AAAA reports: "Sorry, you've already submitted a dig query to the same destination" even if I am absolutely positive that I have not submitted that host.
I wonder is everything OK with this test for others?
There might be some ongoing development in that area, changed verification parser script... or just the my database have some record that always match the verification regular expression query.
Today I tried with:
; <<>> DiG 9.8.0-P4-RedHat-9.8.0-9.P4.fc15 <<>> AAAA www.dailykos.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2491
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;www.dailykos.com. IN AAAA
;; ANSWER SECTION:
www.dailykos.com. 3600 IN AAAA 2001:48c8:1:c::feeb:beef
www.dailykos.com. 3600 IN AAAA 2001:48c8:1:c::feeb:beff
;; AUTHORITY SECTION:
dailykos.com. 170874 IN NS ns.voxel.net.
dailykos.com. 170874 IN NS ns2.voxel.net.
;; ADDITIONAL SECTION:
ns.voxel.net. 1574 IN A 208.122.22.21
ns2.voxel.net. 1574 IN A 208.122.22.22
;; Query time: 42 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sat Sep 10 00:18:32 2011
;; MSG SIZE rcvd: 166
with the same result :(
...any help would be appreciated.
Thank you.
Regards,
Z
Keep in mind that it's tracking the prefix, not the website
So if Site A has 2001:db8:1234:5678::2/64 and Site B has 2001:db8:1234:5678::2/64, you're going to run into problems
Its also possible that the ip is used by multiple sites.
www.foo.bar
ftp.foo2.bar
both point to the same ip.
Hello,
Thank you for helping me... but there is no problems with the IP addresses, duplicates, already submitted values etc.
I have taken information from the http://bgp.he.net/ipv6-progress-report.cgi page and done all tests with a script with listed 300 hosts. I have enough different data/information for the whole Daily test run.
All tests have worked perfect until now... but in the last few days just the IPv6 DIG AAAA fail with all tested data, therefore I have a feeling that the problem is somewhere else - either in the database where the data is stored or with the logic that checks for duplicate entries.
I have tested today with at least 4 different and valid outputs with the same result: "Sorry, you've already submitted a dig query to the same destination" :(
Thank you.
Regards,
Z
You're probably better to send e-mail to ipv6@he.net to get your question answered. Show them an example of a failed dig query and they can investigate.
Thank you. This is a good idea. I'll send a mail right away.
Thank you.
Regards,
Z
QuoteDate: Tue, 15 Nov 2011 02:36:02 -0800
From: Hurricane Electric IPv6 Operations <ipv6@he.net>
To: zoli@polarhome.com
Subject: [#1769495] Acknowledgement from Hurricane Electric Ipv6 Operations
Your message ("Daily tests: Submit an IPv6 DIG AAAA problem") has been assigned the tracking ID [#1769495].
One of our engineers will reply to your email within 24 hours.
...soon it will be 24 days without reply. :(
I am in fact very satisfied with the ipv6 tunnel service - just as a perfectionist, I would like to complete this test and I can not as long every "dig AAAA" output is refused.
Regards,
Z
24 days? I must go do more math quizzes at Khan Academy, because the 15th was only 9 days ago. Also someone replied to that ticket, might want to check your spam folder:
Hi,
Thanks for contacting Hurricane Electric.
Please retest and let us know if you continue to see the issue.
Regards,
Tae Kim
Hurricane Electric
AS6939
Hello,
I am sorry for the pessimistic day calculation... but I haven't got any reply so far.
I continuously retry every day as you can see from the log... and the Daily Dig (AAAA) fails in the past 10 days
Daily Traceroute ; Score: 48 / 100
Daily Dig (AAAA) ; Score: 37 / 100
Daily Whois ; Score: 47 / 100
Daily Dig (PTR) ; Score: 46 / 100
Daily Ping6 ; Score: 48 / 100
Today I tried with:
; <<>> DiG 9.8.0-P4-RedHat-9.8.0-9.P4.fc15 <<>> AAAA ipv6.iu.edu
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59367
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 1
;; QUESTION SECTION:
;ipv6.iu.edu. IN AAAA
;; ANSWER SECTION:
ipv6.iu.edu. 3600 IN AAAA 2001:18e8:2:191::109
ipv6.iu.edu. 3600 IN AAAA 2001:18e8:2:191::108
;; AUTHORITY SECTION:
ipv6.iu.edu. 3600 IN NS dns2.iu.edu.
ipv6.iu.edu. 3600 IN NS dns1.iu.edu.
;; ADDITIONAL SECTION:
dns1.iu.edu. 600 IN AAAA 2001:18e8:3:220::10
;; Query time: 258 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sat Sep 10 01:00:43 2011
;; MSG SIZE rcvd: 151
Thank you for helping me.
Regards,
Z
Hello,
today I tried with:
; <<>> DiG 9.8.0-P4-RedHat-9.8.0-9.P4.fc15 <<>> AAAA www.dumpert.nl
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32231
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 1
;; QUESTION SECTION:
;www.dumpert.nl. IN AAAA
;; ANSWER SECTION:
www.dumpert.nl. 300 IN AAAA 2a00:d00:ff:235:81:23:247:230
;; AUTHORITY SECTION:
dumpert.nl. 84342 IN NS ns2.garnierprojects.nl.
dumpert.nl. 84342 IN NS ns.garnierprojects.nl.
dumpert.nl. 84342 IN NS ns1.garnierprojects.nl.
;; ADDITIONAL SECTION:
ns2.garnierprojects.nl. 1542 IN A 81.23.248.2
;; Query time: 54 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sat Sep 10 00:38:39 2011
;; MSG SIZE rcvd: 145
I would appreciate if somebody responsible would try to submit in my name.
Thank you.
Regards,
Z
Summary of user's dig query
Host name: www.dumpert.nl.
AAAA Record:2a00:d00:ff:235:81:23:247:230
Status: NOERROR
Result: Pass
I don't know how to submit it in your name though...did you get an error when submitting?
Hello,
thank you for testing.
It have worked perfect 37 times... but I guess something got corrupted in the database and now every entry that I submit match with that corrupted record. This is exactly what the error message says: "Sorry, you've already submitted a dig query to the same destination". Like this I am totally stacked with dig AAAA test, until somebody does not delete that corrupted record that match all destinations.
Today, I tried with the same failure.
; <<>> DiG 9.8.0-P4-RedHat-9.8.0-9.P4.fc15 <<>> AAAA sapo.pt
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7591
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 0
;; QUESTION SECTION:
;sapo.pt. IN AAAA
;; ANSWER SECTION:
sapo.pt. 900 IN AAAA 2001:8a0:2104:ff:213:13:146:140
;; AUTHORITY SECTION:
sapo.pt. 18000 IN NS ns2.sapo.pt.
sapo.pt. 18000 IN NS dns02.sapo.pt.
sapo.pt. 18000 IN NS ns.sapo.pt.
sapo.pt. 18000 IN NS dns01.sapo.pt.
;; Query time: 127 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sat Sep 10 00:04:20 2011
;; MSG SIZE rcvd: 128
Regards,
Z
Did you ever reply to the email HE sent you?
Hello,
I have never got that e-mail :(
Should I write again?
Regards,
Z
broquea copied and pasted the email in one of the replies above; if you didn't get that email, I would write again
Hello,
thank you for the suggestion. I have sent a mail again to Hurricane Electric IPv6 Operations - hopefully they can help me this time.
Today I tried to submit:
; <<>> DiG 9.8.0-P4-RedHat-9.8.0-9.P4.fc15 <<>> AAAA ipv6.vt.edu
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54412
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ipv6.vt.edu. IN AAAA
;; ANSWER SECTION:
ipv6.vt.edu. 14400 IN AAAA 2001:468:c80:210f:0:1c6:1a85:8564
;; Query time: 132 msec
;; SERVER: 192.168.10.1#53(192.168.10.1)
;; WHEN: Sat Sep 10 01:04:27 2011
;; MSG SIZE rcvd: 57
...mean while I notices another weird behaviour.
Not all correct whois responses are accepted, but for that it is better to open a new topic.
http://www.tunnelbroker.net/forums/index.php?topic=2154.0 (http://www.tunnelbroker.net/forums/index.php?topic=2154.0)
Thank you.
Regards,
Z
Hi polarhome
I am posting my response here just in case you didn't receive my email again.
There was a minor bug(or a typo) in our test script and it is now corrected.
Please retest and let me know if you continue to see the issue.
Here's my test result:
Summary of user's dig query
Host name: sapo.pt.
AAAA Record:2001:8a0:2104:ff:213:13:146:140
Status: NOERROR
Result: Pass
Summary of user's dig query
Host name: ipv6.vt.edu.
AAAA Record:2001:468:c80:210f:0:1c6:1a85:8564
Status: NOERROR
Result: Pass
Tae
Hello,
thank you very much for the fix.
I confirm, that it works perfect and accepts new submitted data.
Thank you.
Regards,
Z