Re: How to Setup Reverse DNS on LAN?

2004-01-26 Thread Stephane Bortzmeyer
On Tue, Dec 09, 2003 at 05:50:25AM -0800,
 Drew Tomlinson <[EMAIL PROTECTED]> wrote 
 a message of 33 lines which said:

> When connecting via ssh to my FBSD boxes, it takes over a minute
> before the connection is established.  Searching the archives
> suggests that this is due to a failed reverse DNS lookup that must
> time out before connecting.

Probably.

> But 192.168.1.3 does not:
> 
> blacksheep> host 192.168.1.3
> Host not found, try again.

On FreeBSD 5.1, it appears, speaking both from the man page and from
an actual test, that host does not use /etc/hosts at all. It would be
nice to have a command which uses getaddrinfo() but host does not.

ping would be a better test:

~ % ping localhost
PING fetiche (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.253 ms

The name 'fetiche' was found in /etc/hosts.



___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: How to Setup Reverse DNS on LAN?

2003-12-10 Thread Drew Tomlinson
- Original Message -
From: "Stephane Bortzmeyer" <[EMAIL PROTECTED]>
Sent: Tuesday, December 09, 2003 9:40 AM


> On Tue, Dec 09, 2003 at 05:50:25AM -0800,
>  Drew Tomlinson <[EMAIL PROTECTED]> wrote
>  a message of 33 lines which said:
>
> > When connecting via ssh to my FBSD boxes, it takes over a minute
> > before the connection is established.  Searching the archives
> > suggests that this is due to a failed reverse DNS lookup that must
> > time out before connecting.
>
> Probably.
>
> > But 192.168.1.3 does not:
> >
> > blacksheep> host 192.168.1.3
> > Host not found, try again.
>
> On FreeBSD 5.1, it appears, speaking both from the man page and from
> an actual test, that host does not use /etc/hosts at all. It would be
> nice to have a command which uses getaddrinfo() but host does not.

I'm using 4.9.  Sorry, I forgot to specify.

> ping would be a better test:
>
> ~ % ping localhost
> PING fetiche (127.0.0.1): 56 data bytes
> 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.253 ms
>
> The name 'fetiche' was found in /etc/hosts.

I'm not sure what I'm looking for here.  The machine that runs the ssh
client is a Win XP box named 'bigdaddy'.  That resolves on the Win XP box:

C:\Documents and Settings\tomlinson_dr>ping localhost

Pinging bigdaddy [127.0.0.1] with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

The FBSD box running sshd also resolves:

blacksheep# ping localhost
PING localhost (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.519 ms

So what do I need to do?  As I understand it, their needs to be an entry for
the client machine in /etc/hosts which I have.

Thanks,

Drew



___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: How to Setup Reverse DNS on LAN?

2003-12-09 Thread Drew Tomlinson
- Original Message - 
From: "Jason Stewart" <[EMAIL PROTECTED]>
Sent: Tuesday, December 09, 2003 6:21 AM


> On 09/12/03 05:50 -0800, Drew Tomlinson wrote:
> > When connecting via ssh to my FBSD boxes, it takes over a minute
before the
> > connection is established.  Searching the archives suggests that
this is due
> > to a failed reverse DNS lookup that must time out before connecting.
> > Suggestions include adding the hosts to the local host file which
I've done.
> > However this does not seem to provide reverse DNS resolution which
appears
> > required.
> 
> > Short of setting up named, is there a way to solve my problem?
>
> Are you using privilege separation? If you are, the ssh daemon is not
> looking for hosts in /etc. It will be looking somewhere else for the
> /etc/hosts file. Are you using sshd from the base?

Thanks for your reply.  AFAIK, I'm using sshd from the base system with
defaults.  How can I check?

Also, I use courier-imap.  With desktop machines physically attached to
my LAN, I don't have the IMAP clients using SSL and I get no delay
connecting.  However I have a laptop that I bring home from work on
occasion and it is configured to use SSL.  When I use it with a wireless
card on my home LAN, I seem to get similar delays when using it's IMAP
client.  Might the two be related?

Thanks for your help!

Drew

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: How to Setup Reverse DNS on LAN?

2003-12-09 Thread Jason Stewart
On 09/12/03 05:50 -0800, Drew Tomlinson wrote:
> When connecting via ssh to my FBSD boxes, it takes over a minute before the
> connection is established.  Searching the archives suggests that this is due
> to a failed reverse DNS lookup that must time out before connecting.
> Suggestions include adding the hosts to the local host file which I've done.
> However this does not seem to provide reverse DNS resolution which appears
> required.

> Short of setting up named, is there a way to solve my problem?

Are you using privilege separation? If you are, the ssh daemon is not
looking for hosts in /etc. It will be looking somewhere else for the
/etc/hosts file. Are you using sshd from the base?

Jason
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


How to Setup Reverse DNS on LAN?

2003-12-09 Thread Drew Tomlinson
When connecting via ssh to my FBSD boxes, it takes over a minute before the
connection is established.  Searching the archives suggests that this is due
to a failed reverse DNS lookup that must time out before connecting.
Suggestions include adding the hosts to the local host file which I've done.
However this does not seem to provide reverse DNS resolution which appears
required.

For example, I have a Win XP machine at 192.168.1.3 named 'bigdaddy' and a
FBSD box at 192.168.1.2 named 'blacksheep'.  blacksheep contains a line in
/etc/hosts:

192.168.1.3 bigdaddy  bigdaddy.mykitchentable.net

Using the 'host' command, I see that 'bigdaddy' gets resolved:

blacksheep> host bigdaddy
bigdaddy.mykitchentable.net has address 192.168.1.3

But 192.168.1.3 does not:

blacksheep> host 192.168.1.3
Host not found, try again.

Short of setting up named, is there a way to solve my problem?

Thanks,

Drew

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"