1. .htaccess, domain name access works with numbers, not names
I can't get .htaccess to allow access to only our local
domain using the domain name in the .htaccess file, although it works
if I use the dotted quad (well, triplet, really). I have a theory as
to why this might be, and want to run it out and see if anyone has
solved it.
This works:
<Limit GET>
order deny, allow
deny from all
allow from 13.246.76
</Limit>
This does not work:
<Limit GET>
order deny, allow
deny from all
allow from .xis.xerox.com
</Limit>
(Of course, 13.246.76.* is part of xis.xerox.com).
If I look in the error_log, I note that it says:
access for /gotest failed for beowulf, reason : Client denied by
server configuration
where beowulf is beowulf.xis.xerox.com.
So, it seems to me the problem is that local addresses are not
looked up as FQDN, therefore they don't match the domain, therefore
they fail. If IP address is used, there is no need to go to the
resolver to get domain name, therefore it works.
My theory: SunOS (on which I'm running the server) hooks all
lookups through their YP/NIS service. If it can resolve it based on
YP, it will, and it will probably not be fully qualified. If YP
doesn't have the info, it will roll over to the DNS resolver, which
will return a FQDN. Therefore, allowing the local domain by name will
always fail because local domin host names are returned without domain
qualification.
My question: I've seen other people report similar problems.
Are folks with this problem running SunOS? Is there another, simpler
solution known out there that my searching has missed?
I intend to look at the lookup source later and see if I can
write a test program to figure it out. But, in the meantime, if
anyone can shed light on this, agree or disagree, I would appreciate
it.
1.01 GCS/GO d++ p+ c++ l++ u++ e+ -m+ s++/- n- h !(f)? g+ -w+ t+ r-- y?
"I want to permeate the air you breathe/slide my way under your skin/place
myself behind your eyes/and watch you, watch me, looking in." Katell Keineg
2. Physical != logical for Harddisk, complains fdisk
3. RH 6.0: Stumped by network: works on L4 IPs, but not L3 IPs
4. interface metric
5. htaccess problems with host names, but not IP numbers
6. imagetool
7. Apache .htaccess problem (dbmmanage not working)
8. unique identifier for binary compatibility similar to uname
9. .htaccess restriction by subnet, not domain name
10. "user not found" doing .htaccess authentication
11. 4.2 nic aliasing, multiple IPs, one nic does not work???
12. Masquerading not working for some IPs
13. Multiple IPs Not Working...
by