You're ignoring that ssh has extensive configuration options and could be configured to use an alias. Stephan is probably trying to get a more definitive test to help. On Jun 17, 2015 6:06 AM, "Jacek Cała" <jacek.c...@gmail.com> wrote:
> As stated in the original question 'ssh SERVERNAME' works fine, which > means 'ping SERVERNAME' can also resolve the name ok. > > 2015-06-17 13:44 GMT+01:00 Stephan Beal <sgb...@googlemail.com>: > >> On Tue, Jun 16, 2015 at 5:44 PM, Jacek Cała <jacek.c...@gmail.com> wrote: >> >>> works perfectly fine. It's not urgent for me because I can work using IP >>> but I'd appreciate any hints how it may be solved. >>> >> >> Try: >> >> ping SERVERNAME >> >> If that results in the same error then the problem is your DNS config or >> access to the DNS server. >> >> -- >> ----- stephan beal >> http://wanderinghorse.net/home/stephan/ >> http://gplus.to/sgbeal >> "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of >> those who insist on a perfect world, freedom will have to do." -- Bigby Wolf >> >> _______________________________________________ >> fossil-users mailing list >> fossil-users@lists.fossil-scm.org >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> >> > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
