After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 781415 - 3(NXDOMAIN) 3(NXDOMAIN)
Product: sysadmin
Classification: Infrastructure
Component: DNS
Other All
: Normal normal
: ---
Assigned To: GNOME Sysadmins
GNOME Sysadmins
Depends on:
Reported: 2017-04-17 17:16 UTC by Andrew Conrad
Modified: 2017-04-18 16:43 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Andrew Conrad 2017-04-17 17:16:26 UTC
    `host` results in 2 ip addresses and a 3(NXDOMAIN).

Steps to reproduce:
    Run `host`

Actual results: has address has address
    Host not found: 3(NXDOMAIN)

Expected results:

Date encountered:

Additional information:
    I am not very experienced in debugging DNS issues, but my findings are confirmed by external tools:
    From the text on the linked web page, it appears that the issue could be related to delegation.

    This issue makes it impossible for me to install the flatpak gnome runtime.
Comment 1 Andrea Veri 2017-04-18 10:12:53 UTC
Andrew, those results are misleading and might be related to a misbehaving DNS resolver or to spoofed DNS queries, please consider using a DNSSEC-aware resolver and validator. 

dig +short
Comment 2 Andrew Conrad 2017-04-18 15:19:47 UTC
Thanks for the feedback!

If this exact issue occurs again, I will use that to provide more information, but as it has since been fixed, there is nothing more to do at the moment.
Comment 3 Andrea Veri 2017-04-18 15:25:47 UTC
Even if you provide us additional information if it re-occurs we won't be able to help you further as we don't maintain the DNS resolvers you're using.
Comment 4 Andrew Conrad 2017-04-18 16:43:58 UTC
Oh, this wasn't on your end? Sorry, I thought it had to be, considering it occurred for me on 3 different networks and external DNS checker tools were confirming that there was a problem.

I tried to avoid filing a bug, since I am not as familiar with these issues, but after days of not being able to work with flatpak and no responses on #sysadmin in irc (which is understandable), I went for it. I hope this has not caused too much of a disturbance.

Thank you for your time.