dns[12].zoneedit.com at AAAA not responding

[gyufi]

Dear Support Team,

I want to delegate one of my zone to zoneedit, but the registrator is not permit the delegation, because of the failing the nameserver technical check. Your nameservers does not responds at the ipv6 interfaces.

```
➜ ~ host dns1.zoneedit.com
dns1.zoneedit.com has address 31.220.0.12
dns1.zoneedit.com has IPv6 address 2a00:1ca8:2c::1:1686
➜ ~ host -t any -6 qstar.hu dns1.zoneedit.com
;; connection timed out; no servers could be reached
➜ ~ host -t any -6 qstar.hu 2a00:1ca8:2c::1:1686
;; connection timed out; no servers could be reached
```

Do you will resolve this problem?

Thank you very much.

 

[sandy]

I am not familiar with that lookup command: host -t any -6 qstar.hu dns1.zoneedit.com

but I do see this:
dig @dns1.zoneedit.com a qstar.hu

; <<>> DiG 9.8.3-P1 <<>> @dns1.zoneedit.com a qstar.hu
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24231
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 4
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;qstar.hu. IN A

;; ANSWER SECTION:
qstar.hu. 10800 IN A 54.217.205.227

;; AUTHORITY SECTION:
qstar.hu. 10800 IN NS dns2.zoneedit.com.
qstar.hu. 10800 IN NS dns1.zoneedit.com.

;; ADDITIONAL SECTION:
dns1.zoneedit.com. 300 IN A 31.220.0.12
dns1.zoneedit.com. 300 IN AAAA 2a00:1ca8:2c::1:1686
dns2.zoneedit.com. 300 IN A 166.88.18.58
dns2.zoneedit.com. 300 IN AAAA 2607:f358:1:ffc0::11

sandy

 

[gyufi]

Hi sandy,

I am not familiar with that lookup command: host -t any -6 qstar.hu dns1.zoneedit.com

but I do see this:
dig @dns1.zoneedit.com a qstar.hu
sandy

right, then try dig with ipv6 support:

➜ ~ dig -6 @dns1.zoneedit.com a qstar.hu
; <<>> DiG 9.8.3-P1 <<>> -6 @dns1.zoneedit.com a qstar.hu
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

The nameserver not answer on ipv6 interface.

gyufi

 

[sandy]

ahh... it might have to do with your/my current connection for lookup results.
what is your local IPv6 address ?

thanks
sandy

 

[gyufi]

Try it yourself here:
http://www.domain.hu/domain/English/regcheck/

This regcheck has to be all passed and error free to make zone delegation.

 

[sandy]

I see the error but still not sure why it is occurring... that said the domain qstar.hu
is resolving properly it appears.. I have checked on the site other .hu domains we are the dns provider for... same error but all are resolving as expected.

are you observing any resolution errors?

sandy

 

[gyufi]

I dont think that this is a resolution problem.
dns1.zoneedit.com resolve correctly all zones when you request the ipv4 address of dns1.zoneedit.com (31.220.0.12) but if you request via the ipv6 address (2a00:1ca8:2c::1:1686) you dont get any answer. Connection time out. I think that the name servers are not listening on the ipv6 interface on the hosting server.

gyufi

 

[Mark Jeftovic (#fb)]

The nameservers are listening on IPv6 interfaces

$ host -6 qstar.hu dns1.zoneedit.com
Using domain server:
Name: dns1.zoneedit.com
Address: 2a00:1ca8:2c::1:1686#53
Aliases:

qstar.hu has address 54.228.203.27
qstar.hu mail is handled by 5 alt1.aspmx.l.google.com.
qstar.hu mail is handled by 10 aspmx3.googlemail.com.
qstar.hu mail is handled by 1 aspmx.l.google.com.
qstar.hu mail is handled by 10 aspmx2.googlemail.com.
qstar.hu mail is handled by 5 alt2.aspmx.l.google.com.

Can you do a traceroute from where you are to the IPv6 address of either nameserver?

 

[gyufi]

Hi, i got a traceroute from the checker host:

sudo traceroute -6 -T 2A00:1CA8:2C:0:0:0:1:1686 -p 53
traceroute to 2A00:1CA8:2C:0:0:0:1:1686 (2a00:1ca8:2c::1:1686), 30 hops max, 80 byte packets
1 r1.iszt.hu (2a00:e6a0:2:4000::253) 1.409 ms 1.375 ms 1.449 ms
2 bix.retn.net (2001:7f8:35::9002:1) 0.484 ms 0.758 ms 0.483 ms
3 ae1-201.RT.SRV.DRO.NL.retn.net (2a02:2d8:1:a000:232a: 51.743 ms 51.748 ms 51.744 ms
4 GW-Serverius.retn.net (2a02:2d8:1:a000:232a::2) 25.758 ms 25.767 ms 25.755 ms
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

 

[gyufi]

Ok, it seems to be this is an ipv6 routing magic error between the two network somewhere at retn.net . I will resolve this problem another way. Thanks the debugging!