# DNS problem looking up A record for my domain **URL:** \ **Category:** Help\ **Created:** [February 7, 2022, 9:32pm UTC](https://community.letsencrypt.org/t/dns-problem-looking-up-a-record-for-my-domain/171561 "2022-02-07T21:32:55Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![vdastpak](https://avatars.discourse-cdn.com/v4/letter/v/f4b2a3/32.png) [@vdastpak](https://community.letsencrypt.org/u/vdastpak)\ **Post date:** [February 7, 2022, 9:32pm UTC](https://community.letsencrypt.org/t/dns-problem-looking-up-a-record-for-my-domain/171561/1 "2022-02-07T21:32:55Z")
Hi, Running certbot either from the command line or in a postbuild EB hook fails. I have successfully verified my domain records using DNSSpy and DNSViz, and [check-your-website.server-daten.de](http://check-your-website.server-daten.de). Please help. My domain is: [baazii.com](http://baazii.com) I ran this command: sudo certbot -n -d [bazzii.com](http://bazzii.com) --nginx --agree-tos It produced this output: Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator nginx, Installer nginx Requesting a certificate for [bazzii.com](http://bazzii.com) Performing the following challenges: http-01 challenge for [bazzii.com](http://bazzii.com) Waiting for verification... Challenge failed for domain [bazzii.com](http://bazzii.com) http-01 challenge for [bazzii.com](http://bazzii.com) Cleaning up challenges Some challenges have failed. IMPORTANT NOTES: - The following errors were reported by the server: My web server is (include version): Node.js 12 running on 64bit The operating system my web server runs on is (include version): Amazon Linux 2/5.4.10 My hosting provider, if applicable, is: AWS Elastic BeanStalk 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): AWS Beanstalk The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot): certbot 1.11.0 ---
**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\ **Post date:** [February 7, 2022, 9:44pm UTC](https://community.letsencrypt.org/t/dns-problem-looking-up-a-record-for-my-domain/171561/2 "2022-02-07T21:44:07Z")
If you are sure your authoritative DNS are working, try again later. If you are not sure, ask their support or maybe change them. There's a list somewhere on the forum (I'd say top3 are `cloudflare`, `he`, and `1984.is`) ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [February 7, 2022, 9:47pm UTC](https://community.letsencrypt.org/t/dns-problem-looking-up-a-record-for-my-domain/171561/3 "2022-02-07T21:47:50Z")
> [@vdastpak](#): > > I have successfully verified my domain records using (…) DNSViz (…) Interesting! Which domain did you analyse? As I just analised `bazzii.com` and it was the first analysis on DNSViz ([bazzii.com | DNSViz](https://dnsviz.net/d/bazzii.com/dnssec/)): no previous analysis exists.. Also, your thread title states: > DNS problem looking up **A** record for my domain The actual error message states: > [@vdastpak](#): > > SERVFAIL > looking up **AAAA** for [bazzii.com](http://bazzii.com) Not sure how to mis those three extra "A"'s though 🙄 Anyway, it's a wonder the A resource record didn't produce an error.. Or maybe IPv6 (AAAA) is prefered, because all your authoriative DNS servers seem to be malfunctioning. See the DNSViz report I linked above. ---
**Author:** ![vdastpak](https://avatars.discourse-cdn.com/v4/letter/v/f4b2a3/32.png) [@vdastpak](https://community.letsencrypt.org/u/vdastpak)\ **Post date:** [February 7, 2022, 9:57pm UTC](https://community.letsencrypt.org/t/dns-problem-looking-up-a-record-for-my-domain/171561/4 "2022-02-07T21:57:34Z")
> [@vdastpak](#): > > Detail: DNS problem: SERVFAIL looking up A for [bazzii.com](http://bazzii.com) - the > domain's nameservers may be malfunctioning; DNS problem: SERVFAIL > looking up AAAA for [bazzii.com](http://bazzii.com) - the domain's nameservers may be > malfunctioning @Osiris, thanks for looking into this. The error is for both the A and AAAA records: Detail: > [@vdastpak](#): > > DNS problem: SERVFAIL looking up A for [bazzii.com](http://bazzii.com) - the > domain's nameservers may be malfunctioning And this is the DNSViz report, updated 42 minutes ago: [baazii.com | DNSViz](https://dnsviz.net/d/baazii.com/dnssec/) ---
**Author:** ![vdastpak](https://avatars.discourse-cdn.com/v4/letter/v/f4b2a3/32.png) [@vdastpak](https://community.letsencrypt.org/u/vdastpak)\ **Post date:** [February 7, 2022, 10:03pm UTC](https://community.letsencrypt.org/t/dns-problem-looking-up-a-record-for-my-domain/171561/5 "2022-02-07T22:03:55Z")
Thanks @9peppe. As far as I can tell my DNS server (Route 53) is working fine. I'll try later, thanks. ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [February 7, 2022, 10:10pm UTC](https://community.letsencrypt.org/t/dns-problem-looking-up-a-record-for-my-domain/171561/6 "2022-02-07T22:10:08Z")
> [@vdastpak](#): > > And this is the DNSViz report, updated 42 minutes ago: [baazii.com | DNSViz](https://dnsviz.net/d/baazii.com/dnssec/) That's not the same hostname as from the error messages.. ---
**Author:** ![vdastpak](https://avatars.discourse-cdn.com/v4/letter/v/f4b2a3/32.png) [@vdastpak](https://community.letsencrypt.org/u/vdastpak)\ **Post date:** [February 7, 2022, 10:21pm UTC](https://community.letsencrypt.org/t/dns-problem-looking-up-a-record-for-my-domain/171561/7 "2022-02-07T22:21:28Z")
Thank you @Osiris ! I must be blind! Had been banging my head against the wall all day 🤕 Everything is working now! Thanks a lot! ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [February 7, 2022, 10:29pm UTC](https://community.letsencrypt.org/t/dns-problem-looking-up-a-record-for-my-domain/171561/8 "2022-02-07T22:29:49Z")
> [@vdastpak](#): > > My domain is: > [baazii.com](http://baazii.com) > [@vdastpak](#): > > Requesting a certificate for [bazzii.com](http://bazzii.com) Was it a spelling/TYPO problem? ---
**Author:** ![vdastpak](https://avatars.discourse-cdn.com/v4/letter/v/f4b2a3/32.png) [@vdastpak](https://community.letsencrypt.org/u/vdastpak)\ **Post date:** [February 7, 2022, 10:33pm UTC](https://community.letsencrypt.org/t/dns-problem-looking-up-a-record-for-my-domain/171561/9 "2022-02-07T22:33:13Z")
Yes @rg305. I had _bazzii_ instead of _baazii_ for my certbot domain argument! ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [March 9, 2022, 10:33pm UTC](https://community.letsencrypt.org/t/dns-problem-looking-up-a-record-for-my-domain/171561/10 "2022-03-09T22:33:54Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.