Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

64.6.64.6 won't resolve our domain, while 64.6.65.6 does

$ dig net4you.net mx @64.6.64.6

; <<>> DiG 9.10.3-P4-Ubuntu <<>> net4you.net mx @64.6.64.6
;; global options: +cmd
;; connection timed out; no servers could be reached

--- snip ---

$ dig net4you.net mx @64.6.65.6

; <<>> DiG 9.10.3-P4-Ubuntu <<>> net4you.net mx @64.6.65.6
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14871
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
net4you.net. 14400 IN MX 10 mx1.net4you.net.
net4you.net. 14400 IN MX 20 mx2.net4you.net.

;; Query time: 97 msec
;; SERVER: 64.6.65.6#53(64.6.65.6)
;; WHEN: Tue Oct 18 13:32:53 CEST 2016
;; MSG SIZE rcvd: 80

Comments

  • Hello mweissenbacher. To further assist us in troubleshooting the reported issue, could you a;sp please provide us trace routes to both our Recursive Servers (64.6.64.6 and 64.6.65.6)? Thank you in advance.
  • Sure. Here are the traceroutes to both IP's (as seen from our Authoritative DNS Server).
    traceroute to 64.6.64.6 (64.6.64.6), 30 hops max, 40 byte packets
    1 GW-VIL2.net4you.net (194.177.128.3) 0.333 ms 0.398 ms 0.633 ms
    2 kk02-vil.net4you.net (194.177.149.253) 1.482 ms 1.516 ms 1.548 ms
    3 ix01-klu.net4you.net (194.177.149.250) 10.313 ms 10.546 ms 10.548 ms
    4 cr-04.01-00-04.anx03.vie.at.anexia-it.com (37.252.236.1) 10.618 ms 10.626 ms 10.627 ms
    5 cr-01.0v-08-74.anx25.fra.de.anexia-it.com (37.252.248.14) 23.014 ms 23.019 ms 23.020 ms
    6 xe-1-1-0.r1.bb-fo.fra1.vrsn.net (80.81.192.245) 23.309 ms 23.009 ms 22.988 ms
    7 xe-0-2-0.r2.bb-fo.fra1.vrsn.net (199.16.94.194) 23.246 ms 23.313 ms 23.300 ms
    8 xe-3-3-0.r2.bb-fo.ams1.vrsn.net (199.16.94.181) 30.190 ms 30.325 ms 30.305 ms
    9 xe-2-3-0.r2.bb-fo.lon3.vrsn.net (199.7.62.61) 35.301 ms 35.518 ms 35.503 ms
    10 ae3.r2.edge-fo.lon3.vrsn.net (199.16.95.101) 35.308 ms 34.884 ms 35.158 ms
    11 host-163.lon3.verisign.com (199.7.58.163) 35.148 ms 36.238 ms 36.227 ms
    12 recpubns1.nstld.net (64.6.64.6) 35.464 ms 34.937 ms 34.926 ms

    traceroute to 64.6.65.6 (64.6.65.6), 30 hops max, 40 byte packets
    1 GW-VIL2.net4you.net (194.177.128.3) 0.300 ms 0.369 ms 0.428 ms
    2 kk02-vil.net4you.net (194.177.149.253) 1.190 ms 1.272 ms 1.311 ms
    3 ix01-klu.net4you.net (194.177.149.250) 10.301 ms 10.315 ms 10.355 ms
    4 cr-04.01-00-04.anx03.vie.at.anexia-it.com (37.252.236.1) 10.296 ms 10.296 ms 10.297 ms
    5 cr-01.0v-08-74.anx25.fra.de.anexia-it.com (37.252.248.14) 22.872 ms 22.876 ms 22.876 ms
    6 xe-1-1-0.r1.bb-fo.fra1.vrsn.net (80.81.192.245) 23.044 ms 23.138 ms 23.114 ms
    7 po3.r1.edge-fo.fra1.vrsn.net (199.16.95.113) 23.508 ms 23.459 ms 23.449 ms
    8 host-167.fra1.verisign.com (199.7.71.167) 22.968 ms 23.041 ms bu-ether1.r2.edge-fo.fra1.verisign.com (199.7.71.161) 23.034 ms
    9 recpubns2.nstld.net (64.6.65.6) 23.008 ms 23.005 ms 22.994 ms


    Note that other DNS Queries work without a problem. Even other domains hosted on our Authoritative Servers. Part of the problem could be that the domain net4you.net is DNSSEC enabled. The Verisign DNSSEC Debugger says everything is in perfect health. Google Public DNS have no problem resolving the Domain.
    http://dnssec-debugger.verisignlabs.com/net4you.net
  • Hello mweissenbacher,

    Thank you for providing us with the details. We are reviewing this and will provide you with an update soon.

    Thank you.
  • Hello mweissenbacher,

    We have received confirmation that this issue should be resolved. Do not hesitate to let us know if you notice any other anomalies.

    Thank you.
This discussion has been closed.