On 06/ 1/10 10:20 AM, Erik Trimble wrote:
On 6/1/2010 9:19 AM, Shawn Walker wrote:
On 06/ 1/10 05:39 AM, Brandon Hume wrote:
On Mon, 2010-05-31 at 20:22 -0700, lance tan wrote:
When I login to osol from another host in the LAN, obviously, the
DNS server couldn't reverse resolve the IP inside t
>Shawn - just change the "hosts" line of /etc/nsswitch.conf to be:
>hosts: files dns
I wonder why this is not the default setting. I had to apply exactly this
change in order to just surf the web.
--
This message posted from opensolaris.org
___
openso
On 6/1/2010 9:19 AM, Shawn Walker wrote:
On 06/ 1/10 05:39 AM, Brandon Hume wrote:
On Mon, 2010-05-31 at 20:22 -0700, lance tan wrote:
When I login to osol from another host in the LAN, obviously, the
DNS server couldn't reverse resolve the IP inside the LAN. But there
is no way to disable DNS
On 06/ 1/10 05:39 AM, Brandon Hume wrote:
On Mon, 2010-05-31 at 20:22 -0700, lance tan wrote:
When I login to osol from another host in the LAN, obviously, the DNS server
couldn't reverse resolve the IP inside the LAN. But there is no way to disable
DNS reverse lookup by SunSSH.
No, but you
On Mon, 31 May 2010 20:22:39 PDT, lance tan wrote:
> I am using DNS. My DNS server is my Wireless Router, actually it is just
a
> proxy, it forwards DNS messages to ISP's DNS server. When I login to
osol
> from another host in the LAN, obviously, the DNS server couldn't reverse
> resolve the IP in
On Mon, 2010-05-31 at 20:22 -0700, lance tan wrote:
> When I login to osol from another host in the LAN, obviously, the DNS server
> couldn't reverse resolve the IP inside the LAN. But there is no way to
> disable DNS reverse lookup by SunSSH.
No, but you can trick it. Toss the IPs in question
I am using DNS. My DNS server is my Wireless Router, actually it is just a
proxy, it forwards DNS messages to ISP's DNS server. When I login to osol from
another host in the LAN, obviously, the DNS server couldn't reverse resolve the
IP inside the LAN. But there is no way to disable DNS reverse
Exactly!
UseDNS is the parameter for OpenSSH on Linux, it is not recognized by SunSSH.
"VerifyReverseMapping" is the one for here, but it doesn't take effect at all.
There is a bug.
--
This message posted from opensolaris.org
___
opensolaris-discuss
> Add UseDNS no to /etc/ssh/sshd_config - that should
> turn off DNS lookups
That put my b125 server in maintenance mode after svcadm restart network/ssh
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discus
- "lance tan" skrev:
> I had exactly the same problem. My workaround is start the DNS server
> service. No any configuration, just used the default. After then,
> there is no any outgoing DNS query packet any more, and the login time
> reduced to less than one second. Don't know exactly why,
On Monday 31 May 2010 04:10 AM, lance tan wrote:
I had exactly the same problem. My workaround is start the DNS server service.
No any configuration, just used the default. After then, there is no any
outgoing DNS query packet any more, and the login time reduced to less than one
second. Don'
I had exactly the same problem. My workaround is start the DNS server service.
No any configuration, just used the default. After then, there is no any
outgoing DNS query packet any more, and the login time reduced to less than one
second. Don't know exactly why, seems reverse dns lookup goes in
gu99roax wrote:
>Now I know how it works! So the line
>hosts: file dns
That should be "files" not "file". - In case the typo is sitting in the file
itself & not on the forum.
Tim
--
This message posted from opensolaris.org
___
opensolaris-discuss m
On Mon, 26 Apr 2010 14:41:33 PDT, Robin Axelsson
wrote:
>> the workaround doesn't have to be to have a reverse mapping for
>> the client IP address but to set it up so that you get an immediate
>> response from the system that there is not such reverse, without a
>> delay.
>
>
> And I presume th
> the workaround doesn't have to be to have a reverse mapping for
> the client IP address but to set it up so that you get an immediate
> response from the system that there is not such reverse, without a
> delay.
And I presume that this is what is done when adding the IP-address and name in
the
On Mon, 26 Apr 2010, Jan Pechanec wrote:
>>But for example
>>$ nslookup www.google.com
>>works fine without delay, so the DNS resolution must be fine right?
>
> hi Robin, as mentioned before, not necessarily. name->ip
>resolution is configured by the "hosts" keyword in nsswitch.conf,
>ip->
On Sat, 24 Apr 2010, Robin Axelsson wrote:
>But seriously, why do I need a (Fully Qualified) Domain Name for every
>computer I want to run an SSH server on? That's outright ridiculous!
you don't. The problem is that the server is trying to reverse
the _client_ address and it times out.
On Sat, 24 Apr 2010, Robin Axelsson wrote:
>But for example
>$ nslookup www.google.com
>works fine without delay, so the DNS resolution must be fine right?
hi Robin, as mentioned before, not necessarily. name->ip
resolution is configured by the "hosts" keyword in nsswitch.conf,
ip->name
On Sat, 24 Apr 2010, Robin Axelsson wrote:
>But the server doesn't have any DNS associated with it and I don't want
>it to. I don't understand what to check. There used to be a UseDNS
>parameter in the /etc/ssh/sshd_conf file but it seems to be removed in
>the OpenSolaris version of ssh.
On Sat, 24 Apr 2010, Robin Axelsson wrote:
hi Robin,
>debug1: set_newkeys: setting new keys for 'in' mode
>debug3: aes-128-ctr NID found
>debug1: SSH2_MSG_NEWKEYS received
>debug1: done: ssh_kex2.
>debug1: send SSH2_MSG_SERVICE_REQUEST
>debug2: service_accept: ssh-userauth
>debug1: got SS
On 2010-04-25 14:03, Edward Ned Harvey wrote:
From: opensolaris-discuss-boun...@opensolaris.org [mailto:opensolaris-
discuss-boun...@opensolaris.org] On Behalf Of Robin Axelsson
When I try to ssh to my server, it takes a long time before it asks for
a password (about a minute), and takes a long
On 2010-04-25 02:50, ken wrote:
On 04/24/2010 08:32 PM Robin Axelsson wrote:
But seriously, why do I need a (Fully Qualified) Domain Name for
every computer I want to run an SSH server on? That's outright
ridiculous!
I want to run SSHd on a server without a domain name. Under normal
circum
> From: opensolaris-discuss-boun...@opensolaris.org [mailto:opensolaris-
> discuss-boun...@opensolaris.org] On Behalf Of Robin Axelsson
>
> When I try to ssh to my server, it takes a long time before it asks for
> a password (about a minute), and takes a long time to connect after the
> password i
On Sun, 25 Apr 2010 07:50:25 +1000, James Lever wrote:
> On 25/04/2010, at 7:44 AM, Robin Axelsson wrote:
> But for example
> $ nslookup www.google.com [1]
> works fine without delay, so the DNS resolution must be fine right?
>
> ensure you can both ping, nslookup and dig. There are two different
But seriously, why do I need a (Fully Qualified) Domain Name for every computer
I want to run an SSH server on? That's outright ridiculous!
I want to run SSHd on a server without a domain name. Under normal
circumstances a 'UseDNS no' entry in the /etc/ssh/sshd_config would fix that
problem but
On 25/04/2010, at 9:08 AM, Robin Axelsson
wrote:
ping and nslookup work fine. I don't know how a properly working dig
is supposed to behave, but at least there are no error messages.
Here's the output from dig:
You really should learn to RTFM when asking for help. (try 'man dig'
for
ping and nslookup work fine. I don't know how a properly working dig is
supposed to behave, but at least there are no error messages. Here's the output
from dig:
-
$ dig
; <<>> DiG 9.6.1-P3 <<>>
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id:
On 25/04/2010, at 7:44 AM, Robin Axelsson wrote:
> But for example
> $ nslookup www.google.com
> works fine without delay, so the DNS resolution must be fine right?
ensure you can both ping, nslookup and dig. There are two different resolution
mechanisms in play so you want to test both.
chee
But for example
$ nslookup www.google.com
works fine without delay, so the DNS resolution must be fine right?
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
On Sun, Apr 25, 2010 at 07:18:43AM +1000, James Lever wrote:
>
> On 25/04/2010, at 6:51 AM, Robin Axelsson wrote:
>
> > But the server doesn't have any DNS associated with it and I don't want it
> > to. I don't understand what to check. There used to be a UseDNS parameter
> > in the /etc/ssh/ss
On 25/04/2010, at 6:51 AM, Robin Axelsson wrote:
> But the server doesn't have any DNS associated with it and I don't want it
> to. I don't understand what to check. There used to be a UseDNS parameter in
> the /etc/ssh/sshd_conf file but it seems to be removed in the OpenSolaris
> version of
But the server doesn't have any DNS associated with it and I don't want it to.
I don't understand what to check. There used to be a UseDNS parameter in the
/etc/ssh/sshd_conf file but it seems to be removed in the OpenSolaris version
of ssh.
--
This message posted from opensolaris.org
_
On 25/04/2010, at 1:07 AM, Robin Axelsson wrote:
> What is wrong? Any help would be much appreciated.
Check your DNS configuration.
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
When I try to ssh to my server, it takes a long time before it asks for a
password (about a minute), and takes a long time to connect after the password
is entered. It has the same behaviour when I log in remotely using F-Secure ssh
or on the server using terminal. The only change from the defau
34 matches
Mail list logo
