On Sat, 2022-12-17 at 10:51 -0800, Samuel Sieb wrote: > I think the point here was to see what different programs say when you > give it an invalid IP address. In general, what happens is that the > program tries to do a DNS lookup which fails and you get an answer like > that, not an explanation that the IP address is invalid. Yep! Dig acts weirdly, too. If you try "dig 127.0.0.631" it tries to resolve it to an IP without complaint (of course there's no answer). If you try "dig -x 127.0.0.631" it resolves it as localhost. That's dig querying whatever F36 is doing internally (probably is systemd-resolved.service): [tim@fluffy ~]$ cat /etc/resolv.conf nameserver 127.0.0.53 options edns0 trust-ad If I make dig query a real DNS server (BIND on CentOS7) it doesn't get answers. -- NB: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the list. The following system info data is generated fresh for each post: uname -rsvp Linux 6.0.10-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Nov 26 16:53:11 UTC 2022 x86_64 _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
