allow from <somedyndns.domain> wont work

[mberni]

Hi !

We'd like to allow an external worker admin-access to our site.

To achieve this, we tried this:

<Directory "/home/myweb/mydir">
        AllowOverride None
        Options FollowSymLinks
        Order deny,allow
        Deny from all
        Allow from 10.10
        Allow from external.dyndns.org
</Directory>

Local access works fine (i.e. 10.10.x.x), but the access from the dyndns-entry fails.

If i use the temporarily IP instead, everything is fine.

I guess the reason is, because reverse-dns does not deliver external.dyndns.org for the matching ip.

Is there a way to use a dyndns-entry in such a way?

Any suggestions are welcome.

 

[RhythmAce]

The problem with this type of setup is that the allow directive looks at the referer. That is unless he clicks on a link from a web page at external.dyndns.org it won't work. Using a browser just shows his current ip address which would resolve to his isp. Another solution is to use a remote administration tool such as webmin (linux only) or a remote desktop such as vnc. If you have a webpage that he uses, you may want to use a user/password authentication rather than the allow, deny directives.

 

[feherke]

Hi

The problem with this type of setup is that the allow directive looks at the referer.

What ??? And why ?

http://httpd.apache.org/docs/2.0/mod/mod_access.html#allow

Feherke.

http://rootshell.be/~feherke/

 

[RhythmAce]

His question was why does it work with the ip but not with the domain name. I explained why. I did not get into env vars or agent types because this was not what he was trying to do. I gave him some other solutions and I stand by everything I said. Gimme a star ;-)

 

[mberni]

Thanks for your contributions, both of you

I have got now plenty of stuff to read, but it pretty much looks like i will do that with a vpn-client or such ...

The setenvif-thing doesn't look appropriate to me.