<div>On 28/03/2008, Bob Sterne <<a href="mailto:bob@example.com">bob@example.com</a>> wrote:<blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex"> I had "sshd: .cn" in my server's hosts.deny file, and a dyndns setup on my laptop, with "sshd: <a href="http://myLaptopDyndns.host.name">myLaptopDyndns.host.name</a>" (redacted) in hosts.allow on the server. I thought hosts.allow took precedence over hosts.deny, but when I was in China, it wouldn't let me log in. (I had to log into another machine somewhere else to log into my server to take "sshd: .cn" out and restart sshd, before it would work.) Is hosts.allow supposed to override hosts.deny? Or is the problem that dyndns-type addresses don't "reverse lookup" from the dynamic IP? Thanks -- ubuntu-users mailing list <a href="mailto:ubuntu-users@lists.ubuntu.com">ubuntu-users@lists.ubuntu.com</a> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-users">https://lists.ubuntu.com/mailman/listinfo/ubuntu-users</a> </blockquote></div> Hey, Looks like you got it right - hosts.allow is matched before hotst.deny so it must be something else, perhaps the reverse lookup as you mentioned. Try `man hosts_access`, it lists the access rules for sshd and how to implement them. cheers, Owen.