Forum Moderators: open

Message Too Old, No Replies

Website IP does not match logs

         

chipe

3:23 am on Jan 30, 2014 (gmt 0)

10+ Year Member



I have a server with two IP addresses on its NIC: ...100 and ...200

I have the DNS server pointing at ...200

When I ping website.com, I get the IP address ...200

In IIS7, I have the website binded to http for 'All Unassigned'.

When I look at the logs, all requests show only the IP of ...100

How can this be? (website was already set up by someone else)


The problem comes into play when instead of binding to 'All Unassigned', I bind website.com to ...200

As soon as I bind it to ...200, it no longer works (because somehow it is tied to ...100)

brotherhood of LAN

3:26 am on Jan 30, 2014 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Welcome to the forums. What web server are you using, Apache? Setting it up to listen to *:80 means it will bind to all interfaces.

I see you've tried to bind it to your *.*.*.200... try by editing the apache .conf file for your site if you've not already tried that.

dstiles

9:28 pm on Jan 30, 2014 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



I've always avoided "all unassigned" as it's too easy to get things confused and in any case if there is more than one IP it will confuse itself.

First, ensure that your web site is set up properly in DNS. Specifically (in my opinion) it should be set up for both www and non-www versions of the domain to point to (in your case) 200.

Then, in IIS manager, set up a record for the URL you want to use (say, www) using port 80 and select the 200 IP. Point the record to the relevant web site folder.

Set up a similar record for non-www using the same IP but instead of pointing it to the web folder point it to http://www.example.com and make sure it's a permanent redirect; that means that if someone uses the non-www URL it will still get the web site but search engines will not get two copies of it (they're little tinkers for that!).

Make sure there are no other records in IIS for the same domain.

Restart the IIS server.

If it still fails, look at [intodns.com...] - put your domain name (only) into it and look at the results. Make sure it shows the DNS servers you expect and ensure there are not two conflicting DNS entries (both DNS servers (more if relevant) should have exactly the same entries).

If you are looking at the site in a web browser, refresh the URL. Some sites and browsers have a long-ish cache and need to be prodded.

lucy24

10:06 pm on Jan 30, 2014 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



What web server are you using, Apache?

I hope not, since this is the IIS forum :(

brotherhood of LAN

10:08 pm on Jan 30, 2014 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



I must've skipped the OP mentioning IIS, or maybe the post got moved ;o)

Thankfully dstiles provides a more relevant answer.