• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

Daily Tests - DIG PTR

Started by Plymouth, December 31, 2015, 11:52:09 AM

Previous topic - Next topic

Plymouth

Was wondering if i need to use the same domain to run the daily tests

For the traceroute test i used ipv6.google.com and submitted the results and passed
for the dig aaaa i used ipv6.google.com, submitted the results and failed
the second time dig aaaa i used he.net, submitted the results and passed
for the dig ptr i tried the above ipv6 addresses for the domains and it dont matter which one i use they all fail

dig aaaa he.net

; <<>> DiG 9.9.5-3ubuntu0.6-Ubuntu <<>> aaaa he.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35833
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 9

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;he.net.                                IN      AAAA

;; ANSWER SECTION:
he.net.                 21631   IN      AAAA    2001:470:0:76::2

;; AUTHORITY SECTION:
he.net.                 8686    IN      NS      ns5.he.net.
he.net.                 8686    IN      NS      ns3.he.net.
he.net.                 8686    IN      NS      ns4.he.net.
he.net.                 8686    IN      NS      ns1.he.net.
he.net.                 8686    IN      NS      ns2.he.net.

;; ADDITIONAL SECTION:
ns1.he.net.             75136   IN      A       216.218.130.2
ns2.he.net.             69349   IN      A       216.218.131.2
ns2.he.net.             14833   IN      AAAA    2001:470:200::2
ns3.he.net.             28032   IN      A       216.218.132.2
ns3.he.net.             14833   IN      AAAA    2001:470:300::2
ns4.he.net.             77790   IN      A       216.66.1.2
ns4.he.net.             142786  IN      AAAA    2001:470:400::2
ns5.he.net.             28033   IN      A       216.66.80.18

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Jan 01 08:44:55 NZDT 2016
;; MSG SIZE  rcvd: 317


dig -x 2001:470:0:76::2

; <<>> DiG 9.9.5-3ubuntu0.6-Ubuntu <<>> -x 2001:470:0:76::2
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48143
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 6, ADDITIONAL: 13

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.6.7.0.0.0.0.0.0.0.7.4.0.1.0.0.2.ip6.arpa. IN PTR

;; ANSWER SECTION:
2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.6.7.0.0.0.0.0.0.0.7.4.0.1.0.0.2.ip6.arpa. 84362IN PTR he.net.

;; AUTHORITY SECTION:
ip6.arpa.               168779  IN      NS      d.ip6-servers.arpa.
ip6.arpa.               168779  IN      NS      c.ip6-servers.arpa.
ip6.arpa.               168779  IN      NS      e.ip6-servers.arpa.
ip6.arpa.               168779  IN      NS      b.ip6-servers.arpa.
ip6.arpa.               168779  IN      NS      a.ip6-servers.arpa.
ip6.arpa.               168779  IN      NS      f.ip6-servers.arpa.

;; ADDITIONAL SECTION:
a.ip6-servers.arpa.     168779  IN      A       199.212.0.73
a.ip6-servers.arpa.     168779  IN      AAAA    2001:500:13::73
b.ip6-servers.arpa.     168779  IN      A       199.253.182.182
b.ip6-servers.arpa.     168779  IN      AAAA    2001:500:86::86
c.ip6-servers.arpa.     168779  IN      A       196.216.169.11
c.ip6-servers.arpa.     168779  IN      AAAA    2001:43f8:110::11
d.ip6-servers.arpa.     168779  IN      A       200.7.86.53
d.ip6-servers.arpa.     168779  IN      AAAA    2001:13c7:7012::53
e.ip6-servers.arpa.     168779  IN      A       202.12.29.59
e.ip6-servers.arpa.     168779  IN      AAAA    2001:dc0:2001:a:4608::59
f.ip6-servers.arpa.     168779  IN      A       193.0.9.2
f.ip6-servers.arpa.     168779  IN      AAAA    2001:67c:e0::2

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Jan 01 08:48:02 NZDT 2016
;; MSG SIZE  rcvd: 493


So i submit the above output into dig ptr daily test and get

Summary of user's dig query
IPv6 Address: 2001:470:0:76::2
Status: NOERROR
Reverse ip6.arpa:
2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.6.7.0.0.0.0.0.0.0.7.4.0.1.0.0.2.ip6.arpa.
Validating user's dig query
Result: Fail
Reason: Record mismatch


Am i doing something wrong ive tried with diffent domains and get the same results everytime  ???

kcochran

Bug in that dig output.  Note the TTL running into the record class.  (84362IN on the -x query).

As to hostnames, try to use ones which might not result in geographically specific IPs depending on where you're doing your query.  We run the same query on this side and compare results.  If you're querying a major site like Google, you'll tend to get an IP for a facility near you, and we'd get one near us.  Those two facilities might not always be the same.

Plymouth

Quote from: kcochran on December 31, 2015, 12:08:14 PM
Bug in that dig output.  Note the TTL running into the record class.  (84362IN on the -x query).

As to hostnames, try to use ones which might not result in geographically specific IPs depending on where you're doing your query.  We run the same query on this side and compare results.  If you're querying a major site like Google, you'll tend to get an IP for a facility near you, and we'd get one near us.  Those two facilities might not always be the same.


Did not see that, i spaced them out resubmitted and passed. Thanks for that