Linux iad1-shared-b7-18 6.6.49-grsec-jammy+ #10 SMP Thu Sep 12 23:23:08 UTC 2024 x86_64
Apache
: 67.205.6.31 | : 216.73.216.47
Cant Read [ /etc/named.conf ]
8.2.29
fernandoquevedo
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
analog /
examples /
[ HOME SHELL ]
Name
Size
Permission
Action
css
[ DIR ]
drwxr-xr-x
README.examples
394
B
-rw-r--r--
analog_mail.cfg
908
B
-rw-r--r--
big.cfg
11.17
KB
-rw-r--r--
bigbyrep.cfg
16.83
KB
-rw-r--r--
ftplog2commonlog
729
B
-rw-r--r--
maillog2commonlog
5.05
KB
-rw-r--r--
misclogs.cfg
7.74
KB
-rw-r--r--
robotinc.cfg
230
B
-rw-r--r--
searchen.cfg
232
B
-rw-r--r--
statslab.cfg
1.9
KB
-rw-r--r--
typealias.cfg
217
B
-rw-r--r--
virtdoms.cfg
2.11
KB
-rw-r--r--
xferlog.cfg
565
B
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : virtdoms.cfg
# THIS CONFIGURATION FILE IS NOT READY TO USE WITHOUT EDITING! # USE ONLY THE FIRST OR THE SECOND HALF OF THIS FILE! # # There are basically two ways to set up your web server if you are serving # lots of virtual domains. The first, which is usually better if you don't # have many virtual domains, is to log them all to different logfiles. This # method is covered pretty thoroughly in one of the How-To documents, but here # is a summary. # # It's easy to analyse each single domain independently, by just specifying # its logfile. If you want to analyse all the domains together, you will need # commands like LOGFILE domain1.log http://www.domain1.com LOGFILE domain2.log http://www.domain2.com # This will add the prefix for that domain to the filenames in that logfile, # so that the same filename in two domains doesn't get confused. The command SUBDIR http://*/ # or SUBDIR http://*/* # is useful make the Directory Report look better. # # The second way to set up your server is to log all the domains to one # logfile. If you do this, you have to log the virtual domain name on each # line so that you know which domain that line belongs to. You will then # probably need a LOGFORMAT command. For example, if you log the virtual # domain at the beginning of the line, which is otherwise in combined format, # you would want a LOGFORMAT command like LOGFORMAT (%v %S %j %u [%d/%M/%Y:%h:%n:%j] "%j%w%r%wHTTP%j" %c %b "%f" "%B") # You still need to add the prefix for the domain to each filename, and you # can do this by a LOGFILE command like LOGFILE alldomains.log http://www.%v.com # Then you can go ahead and analyse the whole site. As above, you will want # the command SUBDIR http://*/ # or SUBDIR http://*/* # If you want to analyse just one of the domains, say domain1, you need the # command VHOSTINCLUDE domain1 # Alternatively, if you often want to analyse just one of the domains, first # split the logfile into pieces corresponding to each virtual domain. This # avoids the need to pass through the whole logfile each time. # # By Stephen Turner 1999-2001. No warranty for this file. # May be used and redistributed without restriction.
Close
