I have a slackware 10.2 box with SSHD running on port 22 using tcp_wrapper. The problem is that I can't connect to it if I write in a domainname instead of an IP in hosts.allow. Is this a common problem?
Tried both .exampledomain.com and exampledomain.com
No difference.
And as my domain is on a dynamic ip I don't want to add it with the ip in the host file. I have the box at work so I can check the exact error message in /var/logs/system tomorrow..

I can both ping and browse the web at the box so my dns server is resolving adresses correctly for that.

Any ideas ?

Is the host name in your hosts.allow on the server the same as the host name in the /etc/hosts on the client? Perhaps the client is not sending the correct domain so it's being denied by the server.

regards
...drkstr

The client is behind a NAT:ed lan and the domain is registered to the clients external ip. I don't know if the computer is sending computername.exampledomain.com or just exampledomain.com so thats why i tried .exampledomain.com in hosts.allow

According to 'man 5 hosts_access' you should be able to use sshd : exampledomain.com or sshd : .exampledomain.com in the /etc/hosts.allow file.

http://linuxhelp.blogspot.com/2005/1...ure-linux.html

You say your domain is on a dynamic IP address; are you using dnsdyn? If you are, have you tried exampledomain.dnsdyn.net in the hosts.allow file?

From the client box, go to
http://www.displaymyhostname.com/
Does it show the DNS set host name or your ISP assigned host name? Mine shows the ISP's host name for my computer since I have not set up a full DNS server on my Slackbox. When I go to the same site from a box behind a correctly configured network, it displays the correct host.domain.

Could this be what's causing your problem?

regards,
...drkstr

It just shows the clients external ip. So this is the problem. Found this here at LQ.

"You can change your /etc/ssh/sshd_config to not do reverse dns lookup, It could also be that your NAT has no reverse record."

Although this solves the problem I know it's not a good idea. I'm not using Dyndns but a similar service where I have bought a domainname.

DNS setup like this at domain provider.
exampledomain.com points to clients external ip (A record)
*.exampledomain.com points to exampledomain.com (CNAME)

Seems like the clients ISP needs to enable reverse dns to the clients ip for it to work ? Or has this something to do with the clients domainproviders dns ?

Well I am by no means an expert on DNS, but I think you have to properly configure a DNS server on your clients network (with BIND and all that nice stuff). Is your client behind another Linux router? I never bothered doing it on my newtwork since I'm not really hosting anything profesional. I just use domain forwarding like you have set up. I hear this can be a bit of a chore, but might be nice to have.

regards,
...drkstr