Tickets - v6 hostname of tunnel endpoint does not resolve :: SixXS

Ticket ID: SIXXS #2445985
Ticket Status: Resolved

PoP: deham02 - Easynet (Hamburg)

v6 hostname of tunnel endpoint does not resolve

Shadow Hawkins on Monday, 09 August 2010 18:46:37

My tunnel endpoint cl-391.ham-02.de.sixxs.net does not resolve properly: cut from dig +trace cl-391.ham-02.de.sixxs.net

ham-02.de.sixxs.net. 3600 IN NS ns1.sixxs.net. ham-02.de.sixxs.net. 3600 IN NS ns2.sixxs.net. ham-02.de.sixxs.net. 3600 IN NS ns3.sixxs.net. ;; Received 249 bytes from 2a02:898:28::3#53(ns.paphosting.nl) in 14 ms

cut from dig @ns1.sixxs.net cl-391.ham-02.de.sixxs.net aaaa

;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 5405 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

cut from dig @ns2.sixxs.net cl-391.ham-02.de.sixxs.net aaaa

;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 870 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

ns3 shows the same behaviour (status: REFUSED) as ns1. This was tested from 2 hosts from different IPv6 networks and as third host via IPv4.

State change: resolved Locked

Jeroen Massar SixXS Staff

on Monday, 09 August 2010 18:52:13

The state of this ticket has been changed to resolved

v6 hostname of tunnel endpoint does not resolve

Jeroen Massar SixXS Staff

on Monday, 09 August 2010 18:52:49

Resolved. Note that ns2 will sync later and thus will follow automatically.

Please note Posting is only allowed when you are logged in.