I am using Webalizer on ubuntu to generate apache access.log reports for my site. Webalizer just gives me the ip address from where my site was accessed. I want the domain names for the ip addresses that are retrieved.
Is there any way to get the domain names? Is there some other tool that I need to use? I tried using Awstats but my server admin told me not to because it changes access rights of various different files. I cannot use google analytics or piwik as well.
I tried nslookup but how can i use nslookup on the access.log file? I don't know how to do this. Can anyone help me out?
If you just want to see the registered domain of one IP address, copy and paste the IP address into the upper right field at arin.net
If you have a bunch of IP addresses to look up, there are other web analytics software products you can use - check out Angelfish Software.
Related
I set up my pi to broadcast it's own "wifi" and I have an Apache server running on it.
I used this tutorial https://learn.adafruit.com/setting-up-a-raspberry-pi-as-a-wifi-access-point
I can currently connect to the network that the pi is broadcasting and go to the ip of the server on my phone and it brings up the webpage, but I want to be able to type in "mydomain.net" and have it bring me to the webpage. Can anyone help me with this or suggest anything?
I want anyone that wants to connect to this local wifi (not worldwide) to be able to enter the website so changing everyone's host file is not going to happen.
you can modify /etc/hosts file on your local machine to point the custom domain name to the IP address of the environment you want to test. The /etc/hosts file contains a mapping of IP addresses to URLs.
Your browser uses entries in the /etc/hosts file to override the IP-address-to-URL mapping returned by a DNS server.
This is only useful for testing DNS (domain name system) changes and the SSL configuration before making a website live.
I've discovered Googlebot indexing my development site (home PC) via its IP address. Surprise. I've changed my .htaccess file to prevent future access, but...
How did Googlebot find me anyway? I made a request to Google to index my live site, but there shouldn't be any links to my IP anywhere on the web.
The only place my IP is listed on my site is in a PHP function that is used to exclude my address from being logged. Can Googlebot (or any bot) harvest IP addresses from raw PHP code?
IP addresses can't likely be harvested from your PHP code because the web server will execute the PHP script and only send the result to the browser.
But there are lots of bots that just scan random IP addresses on port 80 and look for vulnerable software, often using Google's user agent string - did you check if the request's IP address actually belongs to Google? There is even a search engine for IP addresses that have web servers running, you could check if you can find your own host: http://www.shodanhq.com
It is generally a bad idea to let a development server listen on 0.0.0.0, i.e. expose it to the Internet. If you don't need to access it from the outside, let it listen on 127.0.0.1 or you could run into trouble if you don't update it often.
Strange error with an Project using dojo:
if i call : http://localhost/project everything works like expected.
if i call : http://127.0.0.1/project everything works like expected.
if i call : http://192.168.2.1/project i get the following error (ONLY in IE6!):
"Bundle not found, locale.."
Any ideas?
Iam running Zend Server CE with PHP 5.2
if i add: 192.168.2.1 to "hosts" it works (windows)
Sounds like Zend server is performing some kind of virtual site support using the site name as a partial domain.
I can't say 100% if/how it is beacuse I don't use Zend, but I can explain the principle using Apache as an Example.
There are 3 ways in which a web site can be virtually hosted under a single web server application, this applies to most servers on the market today, Apache, IIS, nginx and many others.
It all boils down to one thing, giving one running server application instance the ability to host multiple individual websites.
The 3 methods of seperating sites are as follows:
By IP address : If you have multiple IP addresses (Usually -but not always beacuse you have multiple network interface cards) then you can tell your server application to listen to one IP for one site, another IP for another site and so on. If you browse to one IP you'll get one site, and likewise the other on the other IP.
By Port Number : If your using only one IP address, then you can bind to multiple port numbers, port 80 is generally the default for web servers, but by browsing to an address and pinning the port number on the end (http://mysite.com:99) you'll force the browser to use that port. You can then have multiple websites listening on different ports and select them manually at browse time as required.
By Host Name Header: This is by far the most common way of supporting multiple sites, all web servers that understand the HTTP/1.1 protocol have to obey a header field in the request that contains the host name, when a request comes in for EG: http://mysite,com/ then there will be an entry in the request header that looks like 'Host: mysite.com' the webserver can then use that to say, oh yes.. I know which one that is.. and it then selects and serves the correct website.
The problems start to arise however when you start to use IP addresses that generally cannot be resolved or have no DNS name, because the web server then doesn't know which hostname to tag it to.
As an example in Apache, if you set up a virtual host, then try to browse that server using just the IP address, you'll get the default server, which in many cases won't even be configured to respond correctly or display anything.
To compound this, going up to web application layer, many frameworks also do their own checks on hostnames and other variables passed to them by the web server, and many make decisions on how to operate based on this information.
If you've gotten to the default web application by IP address, then there's a high chance that the framework may get confused at being presented with an IP address as a host name.
As the OP noted, in many cases, you can add a name to your hosts file and use this as a poor man's DNS substitute, the file to modify can be found in the following locations:
c:\windows\system32\drivers\etc\ - on windows
and
/etc/
on Linux/Unix
The file is generally just called 'hosts' and is a plain text file. Adding a line like:
123.456.789.123 myserver
Will tie http://myserver/ to http://123.456.789.123/
If you can, and your doing a lot of web applications it may be worth setting up your own DNS server, most Linux distros will allow you to install 'Bind' and I do also believe there is a version available for windows too.
I'm not going to go into the pro's and cons of private DNS servers here, it's a whole other subject in itself, but if your likely to be doing a lot of additions to your hosts, then in the long run you'll find it a better option.
i'm new at webhosting. I'm trying to set up a small website and i have bought a domain name www.example.com. I have a vps running centos 5 with apache and direct admin. However i am not sure how to make the domain name i bought link to the ip address of my server, so that when someone types www.example.com it takes them to my website.
Also, is it difficult to set up an e-mail address such as me#www.example.com? Thanks for your advice.
When you buy a domain name, you need to tell the registrar which name servers you use. Probably your hosting provider did that for you. He also administers the name servers, but might give you limited permissions to modify your records. Ask him for details.
Hi everyone I'm a new apache tomcat user I have question regarding seting up a domain name I'm kinda confused about that and how do I know what is my current domain name? can I change the domain name ? I looked into the apache documentations but it was not clear
Thank you in advance
Lava
This question sounds a lot like it's asking about domain name registration and DNS hosting rather than anything tomcat specific.
Your current domain name is probably given to you by whoever hosts your server if you're using public address space. If it's a Unix/Linux box you can find out what that is (assuming things are configured sanely) from a shell using
hostname -A
If you only know the IP address you can make a reverse lookup to find a DNS name that probably points back to your server.