Can't access site

Shrimply

For a few days I've been trying to access https://www.energizer.com and can't. I figured the site was down but its come to my attention that actually the site is fine, I can access it through a proxy.

Its not computer specific, I haven't had any other problems and I've tried resetting the router, anyone got any idea whats going on.

calvinac

Its fine for me and I can able to see the site.

dogmaryxx

Try accessing via the IP address 216.205.158.14

Mr_Oink

dogmaryxx wrote: »

Try accessing via the IP address 216.205.158.14

Won't work in this case as it's a shared host looking for the host header line:

Bad Request (Invalid Hostname)

Mr_Oink

Probably worth opening up a command prompt (Hold down the windows key, press and release 'r', then type 'cmd' into the dialouge). Then ping the host and see if you are getting the correct IP address back for it:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\user1>ping energizer.com

Pinging energizer.com [216.205.158.14] with 32 bytes of data:

This should check the resolution process out - check this first.

Shrimply

Thanks, no I get

Ping request could not find host energizer.com. Please check the name and try again.

Mr_Oink

So you have a dns resolution issue. Can you:
1. ping bbc.co.uk
2. ping google.co.uk
? get results ?

Probably worth flushing the dns by typing this command: ipconfig /flushdns
then check again. If this fails check to see if it is the DNS server you are using with the 'nslookup' command:

This will check you local DNS/Name resolution:

C:\Documents and Settings\user1>nslookup energizer.com
Server: private
Address: private
Address: 216.205.158.14

This will repeat the test but using Googles public DNS servers
C:\Documents and Settings\user1>nslookup energizer.com 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
Name: energizer.com
Address: 216.205.158.14

If the latter works, I'd either ask your DNS provider to fix the issue, or switch you DNS server to google.
Also outside chance that your personal firewall or av/web filter is messing around {bad update???} but troubleshoot the DNS first.
HTH

Lil306

I don't know why but soon as I saw this post I thought of faulty host file.

As a temporary solution, could try the following

1 - Navigate to c:\windows\system32\drivers\etc
2 - Put the file with the name "hosts" (has nothing else) in recycle bin
3 - Restart the computer and try again

If it works, your host file was corrupt and it should be sorted.

Also have you tried simple things like clearing up old temporary internet files and cookies ?

The reason you need to do the cookies / host file is if they're pointing to old website DNS links it can mess it up and give you this type of problem as it's still the old address they're looking at.

weegie.geek

Another TalkTalk or BT customer who's fallen foul of their worthless DNS servers?

Lil306

Wouldn't surprise if it's BT, which DNS servers was it changing was it routing through BT DNS on their hubs or actually changing the computers DNS resolution?

Shrimply

OK Well I'll just post the output so you can see the result

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=54ms TTL=116
Reply from 212.58.224.138: bytes=32 time=52ms TTL=116
Reply from 212.58.224.138: bytes=32 time=59ms TTL=116
Reply from 212.58.224.138: bytes=32 time=50ms TTL=116

Ping statistics for 212.58.224.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 59ms, Average = 53ms

C:\Windows\system32>ping google.co.uk

Pinging google.co.uk [66.102.9.103] with 32 bytes of data:
Reply from 66.102.9.103: bytes=32 time=62ms TTL=53
Reply from 66.102.9.103: bytes=32 time=58ms TTL=53
Reply from 66.102.9.103: bytes=32 time=59ms TTL=53
Reply from 66.102.9.103: bytes=32 time=73ms TTL=53

Ping statistics for 66.102.9.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 73ms, Average = 63ms

C:\Windows\system32>ipconfig/flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

C:\Windows\system32>ping energizer.com
Ping request could not find host energizer.com. Please check the name and try ag
ain.

C:\Windows\system32>nslookup energizer.com
Server: Livebox-BC88
Address: 192.168.1.1

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to Livebox-BC88 timed-out

C:\Windows\system32>nslookup energizer.com 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
Name: energizer.com
Address: 216.205.158.14

So your right regarding the DNS server, we're with Orange, and any contact with them in bout to be futile.