On Wed, Aug 5, 2020 at 1:12 PM Tom H <tomh0665(a)gmail.com> wrote:
On Wed, Aug 5, 2020 at 11:48 AM Ed Greshko
<ed.greshko(a)greshko.com>
wrote:
> On 2020-08-05 17:39, Tom H wrote:
>> On Wed, Aug 5, 2020 at 11:28 AM Ed Greshko <ed.greshko(a)greshko.com>
>> wrote:
>>> On 2020-08-05 17:09, Tom H wrote:
>>>> On Tue, Aug 4, 2020 at 1:32 AM ToddAndMargo via users
>>>> <users(a)lists.fedoraproject.org> wrote:
>>>>> On 2020-08-03 03:40, Tom H wrote:
>>>>>>
>>>>>> "resolvectl query _gateway" will tell you that the
gateway's set
>>>>>> to X ip address, but only if you have "myhostname" in
>>>>> "nsswitch.conf". I think I misunderstand.
>>>>>
>>>>> $ resolvectl query _gateway
>>>>> _gateway: resolve call failed: Could not activate remote peer.
>>>>
>>>> grep myhostname /etc/nsswitch.conf
>>>
>>> In addition, in order for this to work I believe you need to have
>>> systemd-resolved.service running.
>>
>> I don't think so. But I'm now curious; I'll grab a Debian or Devuan
>> ISO later and test myhostname in a VM.
>
> Why wait? :-)
>
> [egreshko@f32g ~]$ resolvectl query _gateway
> _gateway: resolve call failed: Could not activate remote peer.
>
> [egreshko@f32g ~]$ sudo systemctl start systemd-resolved.service
>
> [egreshko@f32g ~]$ resolvectl query _gateway
> _gateway: 192.168.122.1 -- link: enp1s0
> 2001:b030:112f:2::2 -- link: enp1s0
>
> -- Information acquired via protocol DNS in 255.7ms.
> -- Data is authenticated: yes
Sorry. I was focused on "_gateway" and forgot about "resolvectl".
Stupid! Of course that you can't use "resolvectl" if
"resolved-systemd" isn't running. But, no need to install Debian or
Devuan, "getent [a]hosts _gateway" will return the gateway ip address.
I'm being hyper-stupid today/this week.
Hopefully Todd, the OP, realized that you were implying that he might
not have "systemd-resolved" running...