You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Something else (please give details in the issue description text field)
Please describe the issue.
Hi Everyone!
Foreword: I'm not an expert in this field, so I'm not sure about the network management software. However I think it's Ubuntu's 22.04 default, systemd-networkd.
Last night I noticed something weird on the messages that were written in the terminal after a successful VPN connection.
In particular I noticed that the DNS domain name of the VPN server is XXXX.loccal (with double "c").
See the attached picture:
I asked my sysadmin if there was a typo somewhere in the DNS configuration but he could not find any.
The fact is that if I RDP to a remote client using the stanrdard FQDN url ".local" I manage to access that PC.
Can you explain if this is a bug in the update-systemd-resolved or where should I check for this typo?
Thanks for you time and feedback!
Shocker
Version in use.
No response
Your Linux distribution.
Ubuntu 22.04 LTS
Your systemd version.
systemd 249 (249.11-0ubuntu3.12)
Your network management software.
Something else (please give details in the issue description text field)
Please describe the issue.
Hi Everyone!
Foreword: I'm not an expert in this field, so I'm not sure about the network management software. However I think it's Ubuntu's 22.04 default, systemd-networkd.
Last night I noticed something weird on the messages that were written in the terminal after a successful VPN connection.
In particular I noticed that the DNS domain name of the VPN server is XXXX.loccal (with double "c").
See the attached picture:
I asked my sysadmin if there was a typo somewhere in the DNS configuration but he could not find any.
The fact is that if I RDP to a remote client using the stanrdard FQDN url ".local" I manage to access that PC.
Can you explain if this is a bug in the update-systemd-resolved or where should I check for this typo?
Thanks for you time and feedback!
Shocker
Output of
resolvectl status
.Please refer to the attached jpg
Other helpful details.
No response
I have read and followed relevant documentation.
The text was updated successfully, but these errors were encountered: