> On Feb 28, 2017, at 7:05 PM, Voytek <li...@sbt.net.au> wrote: > > dig -t MX surfacetreatment.be > > ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.47.rc1.el6_8.4 <<>> -t MX > surfacetreatment.be > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 25122 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 > > ;; QUESTION SECTION: > ;surfacetreatment.be. IN MX > > ;; Query time: 226 msec > ;; SERVER: 45.65.12.7#53(45.65.12.7) > ;; WHEN: Wed Mar 1 10:53:22 2017 > ;; MSG SIZE rcvd: 37
That resolver is having problems that I don't see: $ dig +nocd -t mx surfacetreatment.be ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23879 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 2 ;surfacetreatment.be. IN MX surfacetreatment.be. MX 10 remote.surfacetreatment.be. surfacetreatment.be. NS ns4.skynet.be. surfacetreatment.be. NS ns1.skynet.be. surfacetreatment.be. NS ns3.skynet.be. surfacetreatment.be. NS ns2.skynet.be. And posttls-finger connects to the domain: $ posttls-finger -l may -Lsummary -c surfacetreatment.be posttls-finger: Untrusted TLS connection established to remote.surfacetreatment.be[91.183.126.148]:25: TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits) The problem may be on your end. The report from dnsviz.net also shows no problems (ignore the errors for a non-responding root namerver): http://dnsviz.net/d/surfacetreatment.be/dnssec/ -- Viktor.
