Hello,
I did some more testing and confirmed that the .home was being sent to the
dhcp client (my laptop) by the dhcp server on my router. The Windows OS then
appended that dns suffix when doing a dns lookup on any unqualified domain
names.
Actually I was able to confirm Windows order of
On 23/10/19 8:04 am, Sean Warner wrote:
Hello,
Thank you for answering Uwe. Your response gave me some good pointers.
I don’t think a “default domain” entry is coming from my Windows
laptop. It’s Windows 7 Home Premium and that version knows nothing
about domains. I googled that and also to
On Tue, Oct 22, 2019 at 10:04:37PM +0100, Sean Warner wrote:
>
> I don't think a "default domain" entry is coming from my Windows laptop.
> It's Windows 7 Home Premium and that version knows nothing about domains. I
> googled that and also to see if Chrome maybe adds in a .home if a domain is
>
Hello,
Thank you for answering Uwe. Your response gave me some good pointers.
I don't think a "default domain" entry is coming from my Windows laptop.
It's Windows 7 Home Premium and that version knows nothing about domains. I
googled that and also to see if Chrome maybe adds in a .home if
Hi,
The reason for this is a “default domain” entry in the Windows 7 laptop
configuration, so it is sent by the client in the case of a missing domain. It
was not added by dnsmasq, but by the Windows client.
On the other hand, this still resolves, because you seem to also have a “domain
