search for: a_host

...g .ssh/config: Host a Hostname a.b.c User userA Host * User userB - `ssh a' should log in to userA at a.b.c, `ssh b.c.d' should log in to userB at b.c.d' - Move the `a' host into an included file to have the following .ssh/config: Host * User userB Include ~/.ssh/a_host - `ssh a' will try to log in to userB at a.b.c instead of userA at a.b.c. Expected result: `ssh a' should log in to userA at a.b.c anyway since there is an User line in its Host definition and that that works when not included. I have read online that the "Host *" should be...

...ile ~/.ssh/known_hosts". And now my problem: The easiest way to sort target hosts, I thought, was to select our domain in ssh_config: # inside Host *.our_domain parameters # outside Host * parameters However, the hostname used is the one written in the command, I suppose: "ssh a_host.our_domain" works fine! But "ssh a_host" does not. Of course we all avoid writing our domain. So I wanted to check whether a domain is provided (a point "." should exist): # inside Host !*.* parameters # outside Host * parameters Unfortunately it doesn't work....

...NS knows nothing about any DNS entries created on the router, either static or from the DHCP server, and doesn't forward requests for its own local domain that it cannot resolve itself (Of course, forwarding for non-local domains works as it should). The effect can be demonstrated: $ ping a_host ping: unknown host a_host Is it possible to configure the internal DNS so that it also forwards local requests that it's unable to resolve itself ? I have read this (https://lists.samba.org/archive/samba-technical/2013-December/096572.html) that says it can't. I've also seen a sim...