# Getting DNS problem: SERVFAIL looking up

**URL:** <https://community.letsencrypt.org/t/getting-dns-problem-servfail-looking-up/41956>\
**Category:** Help\
**Created:** [September 11, 2017, 8:59am UTC](https://community.letsencrypt.org/t/getting-dns-problem-servfail-looking-up/41956 "2017-09-11T08:59:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Net4all](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/net4all/32/26796_2.png) [@Net4all](https://community.letsencrypt.org/u/Net4all)\
**Post date:** [September 11, 2017, 8:59am UTC](https://community.letsencrypt.org/t/getting-dns-problem-servfail-looking-up/41956/1 "2017-09-11T08:59:15Z")

</div>

Please fill out the fields below so we can help you better.

My domain is: [line28.com](http://line28.com)

I ran this command: certbot --apache -d [line28.com](http://line28.com) -d [www.line28.com](http://www.line28.com)

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log  
Obtaining a new certificate  
Performing the following challenges:  
tls-sni-01 challenge for [line28.com](http://line28.com)  
tls-sni-01 challenge for [www.line28.com](http://www.line28.com)  
Waiting for verification…  
Cleaning up challenges  
Failed authorization procedure. [line28.com](http://line28.com) (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: SERVFAIL looking up A for [line28.com](http://line28.com), [www.line28.com](http://www.line28.com) (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: SERVFAIL looking up A for [www.line28.com](http://www.line28.com)

IMPORTANT NOTES:

- The following errors were reported by the server:

My web server is (include version):  
Apache/2.4.18 (Ubuntu) server built: 2017-07-27T14:34:01

The operating system my web server runs on is (include version):  
DISTRIB\_ID=Ubuntu  
DISTRIB\_RELEASE=16.04  
DISTRIB\_CODENAME=xenial  
DISTRIB\_DESCRIPTION="Ubuntu 16.04.3 LTS"  
NAME="Ubuntu"  
VERSION="16.04.3 LTS (Xenial Xerus)"  
ID=ubuntu  
ID\_LIKE=debian  
PRETTY\_NAME="Ubuntu 16.04.3 LTS"  
VERSION\_ID="16.04"  
HOME\_URL="[http://www.ubuntu.com/](http://www.ubuntu.com/)"  
SUPPORT\_URL="[http://help.ubuntu.com/](http://help.ubuntu.com/)"  
BUG\_REPORT\_URL="[http://bugs.launchpad.net/ubuntu/](http://bugs.launchpad.net/ubuntu/)"  
VERSION\_CODENAME=xenial  
UBUNTU\_CODENAME=xenial

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don’t know):  
yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):  
no

---

<div class="post-metadata">

**Author:** ![sahsanu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sahsanu/32/89984_2.png) [@sahsanu](https://community.letsencrypt.org/u/sahsanu)\
**Post date:** [September 11, 2017, 10:03am UTC](https://community.letsencrypt.org/t/getting-dns-problem-servfail-looking-up/41956/2 "2017-09-11T10:03:22Z")

</div>

Hi @Net4all,

> [@Net4all](#):
>
> DNS problem: SERVFAIL looking up A for [line28.com](http://line28.com),

This SERVFAIL error is because tou have not configured DNSSEC for your domain properly.

> **[DNSSEC Analyzer - line28.com](https://dnssec-analyzer.verisignlabs.com/line28.com)**
>
> The DNSSEC Analyzer from VeriSign Labs is an on-line tool to assist with diagnosing problems with DNSSEC-signed names and zones.

[https://dnssectest.net/line28.com/A](https://dnssectest.net/line28.com/A)

To be able to issue a certificate you need to remove DNSSEC for your domain or better, fix the DNSSEC problems.

Good luck,  
sahsanu

---

<div class="post-metadata">

**Author:** ![Net4all](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/net4all/32/26796_2.png) [@Net4all](https://community.letsencrypt.org/u/Net4all)\
**Post date:** [September 11, 2017, 10:53am UTC](https://community.letsencrypt.org/t/getting-dns-problem-servfail-looking-up/41956/3 "2017-09-11T10:53:22Z")

</div>

Thanks @sahsanu  
True… I had DNSSEC while the DNS servers were at NameSecure but I moved the DNS server to Amazone Route 53 and there did not set the DNSSEC as it is not supported by then for no self registered domains.  
I sent a mail to NameSecure to switch of the DNSSEC. I should be find when this will be done…  
Thanks again,  
Net4all

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [October 11, 2017, 10:53am UTC](https://community.letsencrypt.org/t/getting-dns-problem-servfail-looking-up/41956/4 "2017-10-11T10:53:29Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
