cant see this website
mark roberts
We get a 'page load error' and it displays the message: 'Page not
found'
The page resides at this IP address: 91.197.32.195.
If I enter the IP address in my browser I end up seeing the apache
control panel (I think)
Any ideas? I have been accessing this site as a homepage for months.
I asked a friend who is also on Demon and he reported the same
problem.
Other users with other isp's have no trouble...
TIA.
Denis McMahon
> Other users with other isp's have no trouble...
We can't do much to investigate your problem if you don't tell us the
actual website you're trying to access.
All we can do from the information you gave is tell you that yes, if we
point our browsers at that web server, we do indeed see that yes, the
default web page for that server is the cPanel / Apache default web page.
Rgds
Denis McMahon
mark
McMahon <denis.m....@gmail.com> writes
>mark roberts wrote:
>
>> Other users with other isp's have no trouble...
>
>We can't do much to investigate your problem if you don't tell us the
>actual website you're trying to access.
>
http://www.thechosen5.co.uk/
--
Mark Roberts
Peter Ceresole
> >We can't do much to investigate your problem if you don't tell us the
> >actual website you're trying to access.
> >
>
> http://www.thechosen5.co.uk/
Took a few seconds to connect (maybe 5 or 6) but it comes up fine here
at 2300.
--
Peter
mark
Ceresole <pe...@cara.demon.co.uk> writes
>
>Took a few seconds to connect (maybe 5 or 6) but it comes up fine here
>at 2300.
Hmmm. So not specifically Demon then.
Any suggestions?
Neither I or a fellow demon user (lives 25 miles away) can access this
site.
I'm baffled. Always used to be able to look at it..
If I enter the ip in a browser I can see the apache page:
http://91.197.32.195/.
I can ping it.
I can traceroute it:
Traceroute to: 91.197.32.195
IP address: [91.197.32.195]
1: [000.000.1.1] my.router
( 0 ms) ! ( 0 ms) ! ( 0 ms) !
2: [194.159.161.32] anchor-hg-1-lo100.router.demon.net
( 35 ms) ! ( 34 ms) ! ( 33 ms) !
3: [194.217.23.5] anchor-access-4-s2002.router.demon.net
( 36 ms) ! ( 35 ms) ! ( 34 ms) !
4: [194.159.161.94] anchor-inside-4-g6-0-4.router.demon.net
( 35 ms) ! ( 34 ms) ! ( 34 ms) !
5: [194.70.98.174] tele-border-1-g1-0-0.router.demon.net
( 34 ms) ! ( 34 ms) ! ( 35 ms) !
6: [195.66.226.151] linx-gw1.enta.net
( 33 ms) ! ( 36 ms) ! ( 35 ms) !
7: [87.127.246.121] te4-4.telehouse-north.core.enta.net
( 35 ms) ! ( 35 ms) ! ( 33 ms) !
8: [87.127.236.37] te5-3.telehouse-east2.core.enta.net
( 34 ms) ! ( 36 ms) ! ( 35 ms) !
9: [87.127.236.97] te4-4.telehouse-east.core.enta.net
( 34 ms) ! ( 34 ms) ! ( 34 ms) !
10: [78.33.51.30] ge-0-190.rt2.the.synergyworks.co.uk
( 36 ms) ! ( 35 ms) ! ( 34 ms) !
11: [91.197.32.195]
( 35 ms) !E ( 37 ms) !E ( 36 ms) !E
Stopped: destination reached
But it wont find the page :(
What could cause this?
--
Mark Roberts
Peter Ceresole
> If I enter the ip in a browser I can see the apache page:
> http://91.197.32.195/
I get that too. But entering <http://www.thechosen5.co.uk/> takes me
straight there.
--
Peter
mark
<ma...@martem.demon.co.uk> writes
>
>What could cause this?
>
>
Demons DNS servers must have something up with them.
After reading another thread I changed to different dns servers and all
is well....
Who do I tell?
--
Mark Roberts
Peter Ceresole
> Demons DNS servers must have something up with them.
> After reading another thread I changed to different dns servers and all
> is well....
Could be. But they have been working perfectly all day here, and they
also worked on your site at 2300 (and again at 2337).
--
Peter
Denis McMahon
My guess is that the ip is a virtual hosting server, and this was just a
domain hosted on it.
Looks like there's an issue with the DNS somewhere.
If I add the following in my hosts file I can baccess the site:
91.197.32.195 www.thechosen5.co.uk
but relying on the demon dns, I get failure messages:
denis@denis-desktop:~$ host -a www.thechosen5.co.uk
Trying "www.thechosen5.co.uk"
Received 38 bytes from 158.152.1.43#53 in 1000 ms
Trying "www.thechosen5.co.uk"
Host www.thechosen5.co.uk not found: 2(SERVFAIL)
Received 38 bytes from 158.152.1.43#53 in 26 ms
denis@denis-desktop:~$ host -a thechosen5.co.uk
Trying "thechosen5.co.uk"
Received 34 bytes from 158.152.1.43#53 in 996 ms
Trying "thechosen5.co.uk"
Host thechosen5.co.uk not found: 2(SERVFAIL)
Received 34 bytes from 158.152.1.43#53 in 25 ms
denis@denis-desktop:~$
Rgds
Denis McMahon
Denis McMahon
> I can ping it.
> I can traceroute it:
See my other reply - there's a dns problem somewhere.
Rgds
Denis McMahon
mark
Ceresole <pe...@cara.demon.co.uk> writes
I'm fine with the new dns servers but not with the old ones.
This has been gong on for the past couple of evenings.
--
Mark Roberts
mark
McMahon <denis.m....@gmail.com> writes
>mark wrote:
>
>> I can ping it.
>> I can traceroute it:
>
>See my other reply - there's a dns problem somewhere.
>
now.....
--
Mark Roberts
Denis McMahon
denis@denis-desktop:~$ dig thechosen5.co.uk
; <<>> DiG 9.6.1-P1 <<>> thechosen5.co.uk
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 39416
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;thechosen5.co.uk. IN A
;; Query time: 116 msec
;; SERVER: 158.152.1.58#53(158.152.1.58)
;; WHEN: Tue Dec 1 23:46:01 2009
;; MSG SIZE rcvd: 34
denis@denis-desktop:~$ dig www.thechosen5.co.uk
; <<>> DiG 9.6.1-P1 <<>> www.thechosen5.co.uk
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 17464
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.thechosen5.co.uk. IN A
;; Query time: 38 msec
;; SERVER: 158.152.1.58#53(158.152.1.58)
;; WHEN: Tue Dec 1 23:46:14 2009
;; MSG SIZE rcvd: 38
"SERVFAIL means that the domain does exist and the root name servers
have information on this domain, but that the authoritative name servers
are not answering queries for this domain."
So this is pointing at a dns problem.
denis@denis-desktop:~$ whois thechosen5.co.uk
Domain name:
thechosen5.co.uk
Registrant:
Rowan Crossley
Registrant type:
Unknown
Registrant's address:
12 The Crescent
Yorkshire
S75 1JH
United Kingdom
Registrar:
Key-Systems GmbH [Tag = KEY-SYSTEMS-DE]
URL: http://www.Key-Systems.net
Relevant dates:
Registered on: 14-Oct-2008
Renewal date: 14-Oct-2010
Last updated: 14-Oct-2008
Registration status:
Registered until renewal date.
Name servers:
ns1.boltwared.com
ns2.boltwared.com
WHOIS lookup made at 23:48:41 01-Dec-2009
--
This WHOIS information is provided for free by Nominet UK the central
registry
for .uk domain names. This information and the .uk WHOIS are:
Copyright Nominet UK 1996 - 2009.
You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at
http://www.nominet.org.uk/whois, which
includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.
denis@denis-desktop:~$ man host
denis@denis-desktop:~$ host -a thechosen5.co.uk ns1.boltwared.com
Trying "thechosen5.co.uk"
;; connection timed out; no servers could be reached
denis@denis-desktop:~$ host -a thechosen5.co.uk ns2.boltwared.com
Trying "thechosen5.co.uk"
;; connection timed out; no servers could be reached
denis@denis-desktop:~$
Hmm, so the whois server point at dns servers for the domain, but those
dns servers are unreachable?
denis@denis-desktop:~$ host -a ns2.boltwared.com
Trying "ns2.boltwared.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50094
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
;; QUESTION SECTION:
;ns2.boltwared.com. IN ANY
;; ANSWER SECTION:
ns2.boltwared.com. 3600 IN A 68.178.232.99
;; AUTHORITY SECTION:
boltwared.com. 3600 IN NS ns13.domaincontrol.com.
boltwared.com. 3600 IN NS ns14.domaincontrol.com.
Received 103 bytes from 158.152.1.58#53 in 111 ms
denis@denis-desktop:~$ host -a ns1.boltwared.com
Trying "ns1.boltwared.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54463
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
;; QUESTION SECTION:
;ns1.boltwared.com. IN ANY
;; ANSWER SECTION:
ns1.boltwared.com. 3600 IN A 68.178.232.99
;; AUTHORITY SECTION:
boltwared.com. 3600 IN NS ns13.domaincontrol.com.
boltwared.com. 3600 IN NS ns14.domaincontrol.com.
Oh that's VERY BAD PRACTICE - both dns servers are the same ip. Now I'm
starting to detect an oopsy.
Now we try a couple more things:
denis@denis-desktop:~$ ping ns1.boltwared.com
PING ns1.boltwared.com (68.178.232.99) 56(84) bytes of data.
64 bytes from parkwebwin-v02.prod.mesa1.secureserver.net
(68.178.232.99): icmp_seq=1 ttl=106 time=156 ms
64 bytes from parkwebwin-v02.prod.mesa1.secureserver.net
(68.178.232.99): icmp_seq=2 ttl=106 time=155 ms
64 bytes from parkwebwin-v02.prod.mesa1.secureserver.net
(68.178.232.99): icmp_seq=3 ttl=106 time=156 ms
64 bytes from parkwebwin-v02.prod.mesa1.secureserver.net
(68.178.232.99): icmp_seq=4 ttl=106 time=154 ms
64 bytes from parkwebwin-v02.prod.mesa1.secureserver.net
(68.178.232.99): icmp_seq=5 ttl=106 time=155 ms
64 bytes from parkwebwin-v02.prod.mesa1.secureserver.net
(68.178.232.99): icmp_seq=6 ttl=106 time=155 ms
64 bytes from parkwebwin-v02.prod.mesa1.secureserver.net
(68.178.232.99): icmp_seq=7 ttl=106 time=155 ms
64 bytes from parkwebwin-v02.prod.mesa1.secureserver.net
(68.178.232.99): icmp_seq=8 ttl=106 time=156 ms
^C
--- ns1.boltwared.com ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7010ms
rtt min/avg/max/mdev = 154.505/155.834/156.830/0.822 ms
denis@denis-desktop:~$ ping ns2.boltwared.com
PING ns2.boltwared.com (68.178.232.99) 56(84) bytes of data.
64 bytes from parkwebwin-v02.prod.mesa1.secureserver.net
(68.178.232.99): icmp_seq=1 ttl=106 time=156 ms
64 bytes from parkwebwin-v02.prod.mesa1.secureserver.net
(68.178.232.99): icmp_seq=2 ttl=106 time=155 ms
64 bytes from parkwebwin-v02.prod.mesa1.secureserver.net
(68.178.232.99): icmp_seq=3 ttl=106 time=155 ms
64 bytes from parkwebwin-v02.prod.mesa1.secureserver.net
(68.178.232.99): icmp_seq=4 ttl=106 time=156 ms
^C^F
--- ns2.boltwared.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 155.789/156.132/156.622/0.515 ms
denis@denis-desktop:~$ tracert ns1.boltwared.com
The specified type of tracerouting is allowed for superuser only
denis@denis-desktop:~$ sudo tracert ns1.boltwared.com
[sudo] password for denis:
traceroute to ns1.boltwared.com (68.178.232.99), 30 hops max, 60 byte
packets
1 192.168.254.254 (192.168.254.254) 37.952 ms 37.536 ms 36.997 ms
2 194.159.169.245 (194.159.169.245) 26.383 ms * *
3 * * *
4 * * *
5 * * *
6 * ge-6-18.car1.London2.Level3.net (212.187.160.125) 25.550 ms *
7 * ae-32-54.ebr2.London2.Level3.net (4.68.117.126) 27.551 ms *
8 ae-41-41.ebr1.London1.Level3.net (4.69.141.189) 28.386 ms * *
9 * * *
10 * * *
11 * * *
12 * * ae-74-74.ebr4.NewYork1.Level3.net (4.69.134.117) 107.859 ms
13 * ae-3.ebr2.Dallas1.Level3.net (4.69.137.121) 130.236 ms 143.350 ms
14 ae-61-68.ebr1.Dallas1.Level3.net (4.69.146.66) 131.592 ms 142.037
ms 131.745 ms
15 ae-8-8.car1.Phoenix1.Level3.net (4.69.133.29) 360.450 ms 225.249
ms 222.653 ms
16 ae-11-11.car2.Phoenix1.Level3.net (4.69.133.34) 154.394 ms 154.610
ms 153.956 ms
17 THE-GO-DADD.car2.Phoenix1.Level3.net (4.53.106.2) 182.936 ms
160.605 ms 194.516 ms
18 ip-208-109-112-154.ip.secureserver.net (208.109.112.154) 156.124 ms
155.758 ms 155.302 ms
19 * * *
20 * * *
21 * * *
22 * * *
23 ip-64-202-160-153.secureserver.net (64.202.160.153) 166.276 ms * *
24 * * *
25 parkwebwin-v02.prod.mesa1.secureserver.net (68.178.232.99) 157.467
ms 157.846 ms 159.196 ms
denis@denis-desktop:~$ host -a thechosen5.co.uk 68.178.232.99
Trying "thechosen5.co.uk"
;; connection timed out; no servers could be reached
denis@denis-desktop:~$
And .... it seems that the servers pointed at by whois are up and
running, but, and this is the critical bit, they're not responding to
dns enquiries.
So, anyone who has the address cached, or is hitting a cached copy of
the dns entries, will find the site, but anyone who causes a lookup will
hit the broken servers.
The guy that runs the site needs to kick his provider up the rear and
tell them to fix the dns server.
Meanwhile, a temporary fix is to add a line in /etc/hosts (or wherever
windows puts the hosts file) like this:
91.197.32.195 www.thechosen5.co.uk
Look here for help if you don't know where your hosts file is. Be very
careful editing the file, you can break things, so make sure you have a
backup before you start: http://en.wikipedia.org/wiki/Hosts_file
Rgds
Denis McMahon
Peter Ceresole
> Looks like there's an issue with the DNS somewhere.
Maybe there is. I just tried it on a machine that had never had anything
but the Demon DNS servers entered on it, as opposed to one that had
4.2.2.1 added to the DNS server list, and it failed to resolve it. With
the 4.2.2.1 entry, it worked fine.
--
Peter
Denis McMahon
That's only a temporary fix, unless the dns servers for the domain get
fixed.
The reason you've experienced the problem is (I imagine) that the demon
dns servers didn't have the dns for that domain cached, and so needed to
to query the master servers for the domain, which are broken.
As the data expires from other dns caches, they will forget the dns
entry, and will be unable to refresh themselves from the broken server
for the domain.
As of 03:15 ns1/ns2 .boltwared.com are still not responding to dns
queries for (www.)thechosen5.co.uk
Rgds
Denis McMahon
Denis McMahon
It gets curiouser
Looks like the actual problem might be stale data in the demon dns cache
for the boltwared.com nameservers
If I push queries to *.gtld-servers.net I get different ips for
ns1.boltwared.com and ns2.boltwared.com than if I query them via demon's
servers.
If I then query those addresses for (www.)thechosen5.co.uk I get a valid
response.
With demon:
denis@denis-desktop:~$ host -a ns2.boltwared.com
Trying "ns2.boltwared.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49820
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
;; QUESTION SECTION:
;ns2.boltwared.com. IN ANY
;; ANSWER SECTION:
ns2.boltwared.com. 2298 IN A 68.178.232.99
;; AUTHORITY SECTION:
boltwared.com. 2298 IN NS ns13.domaincontrol.com.
boltwared.com. 2298 IN NS ns14.domaincontrol.com.
Received 103 bytes from 158.152.1.58#53 in 25 ms
denis@denis-desktop:~$ host -a ns1.boltwared.com
Trying "ns1.boltwared.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21568
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
;; QUESTION SECTION:
;ns1.boltwared.com. IN ANY
;; ANSWER SECTION:
ns1.boltwared.com. 2298 IN A 68.178.232.99
;; AUTHORITY SECTION:
boltwared.com. 2287 IN NS ns13.domaincontrol.com.
boltwared.com. 2287 IN NS ns14.domaincontrol.com.
Received 103 bytes from 158.152.1.58#53 in 25 ms
denis@denis-desktop:~$ host -a thechosen5.co.uk ns1.boltwared.com
Trying "thechosen5.co.uk"
;; connection timed out; no servers could be reached
denis@denis-desktop:~$ host -a thechosen5.co.uk ns2.boltwared.com
Trying "thechosen5.co.uk"
;; connection timed out; no servers could be reached
denis@denis-desktop:~$
Using f.gtld-servers.net (tried a and d as well, didn't bother trying
all the root servers though) to find the ip for n1/ns2.boltwared.com:
denis@denis-desktop:~$ host -a ns2.boltwared.com f.gtld-servers.net
Trying "ns2.boltwared.com"
Using domain server:
Name: f.gtld-servers.net
Address: 192.35.51.30#53
Aliases:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11041
;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;ns2.boltwared.com. IN ANY
;; ANSWER SECTION:
ns2.boltwared.com. 172800 IN A 91.197.32.196
;; AUTHORITY SECTION:
boltwared.com. 172800 IN NS ns13.domaincontrol.com.
boltwared.com. 172800 IN NS ns14.domaincontrol.com.
;; ADDITIONAL SECTION:
ns13.domaincontrol.com. 172800 IN A 216.69.185.7
ns14.domaincontrol.com. 172800 IN A 208.109.255.7
Received 135 bytes from 192.35.51.30#53 in 179 ms
denis@denis-desktop:~$ host -a ns1.boltwared.com f.gtld-servers.net
Trying "ns1.boltwared.com"
Using domain server:
Name: f.gtld-servers.net
Address: 192.35.51.30#53
Aliases:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64017
;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;ns1.boltwared.com. IN ANY
;; ANSWER SECTION:
ns1.boltwared.com. 172800 IN A 91.197.32.195
;; AUTHORITY SECTION:
boltwared.com. 172800 IN NS ns13.domaincontrol.com.
boltwared.com. 172800 IN NS ns14.domaincontrol.com.
;; ADDITIONAL SECTION:
ns13.domaincontrol.com. 172800 IN A 216.69.185.7
ns14.domaincontrol.com. 172800 IN A 208.109.255.7
Received 135 bytes from 192.35.51.30#53 in 179 ms
denis@denis-desktop:~$ host -a thechosen5.co.uk 91.197.32.195
Trying "thechosen5.co.uk"
Using domain server:
Name: 91.197.32.195
Address: 91.197.32.195#53
Aliases:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53546
;; flags: qr aa rd; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 3
;; QUESTION SECTION:
;thechosen5.co.uk. IN ANY
;; ANSWER SECTION:
thechosen5.co.uk. 14400 IN MX 0 thechosen5.co.uk.
thechosen5.co.uk. 86400 IN SOA ns1.boltwared.com. rowan.boltwared.co.uk.
2008101402 86400 7200 3600000 86400
thechosen5.co.uk. 86400 IN NS ns1.boltwared.com.
thechosen5.co.uk. 86400 IN NS ns2.boltwared.com.
thechosen5.co.uk. 14400 IN A 91.197.32.195
;; ADDITIONAL SECTION:
thechosen5.co.uk. 14400 IN A 91.197.32.195
ns1.boltwared.com. 14400 IN A 91.197.32.195
ns2.boltwared.com. 14400 IN A 91.197.32.196
Received 215 bytes from 91.197.32.195#53 in 41 ms
denis@denis-desktop:~$ host -a thechosen5.co.uk 91.197.32.196
Trying "thechosen5.co.uk"
Using domain server:
Name: 91.197.32.196
Address: 91.197.32.196#53
Aliases:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64237
;; flags: qr aa rd; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 3
;; QUESTION SECTION:
;thechosen5.co.uk. IN ANY
;; ANSWER SECTION:
thechosen5.co.uk. 14400 IN MX 0 thechosen5.co.uk.
thechosen5.co.uk. 86400 IN SOA ns1.boltwared.com. rowan.boltwared.co.uk.
2008101402 86400 7200 3600000 86400
thechosen5.co.uk. 86400 IN NS ns2.boltwared.com.
thechosen5.co.uk. 86400 IN NS ns1.boltwared.com.
thechosen5.co.uk. 14400 IN A 91.197.32.195
;; ADDITIONAL SECTION:
thechosen5.co.uk. 14400 IN A 91.197.32.195
ns1.boltwared.com. 14400 IN A 91.197.32.195
ns2.boltwared.com. 14400 IN A 91.197.32.196
Received 215 bytes from 91.197.32.196#53 in 27 ms
denis@denis-desktop:~$ host -a www.thechosen5.co.uk 91.197.32.195
Trying "www.thechosen5.co.uk"
Using domain server:
Name: 91.197.32.195
Address: 91.197.32.195#53
Aliases:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56545
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;www.thechosen5.co.uk. IN ANY
;; ANSWER SECTION:
www.thechosen5.co.uk. 14400 IN CNAME thechosen5.co.uk.
;; AUTHORITY SECTION:
thechosen5.co.uk. 86400 IN NS ns1.boltwared.com.
thechosen5.co.uk. 86400 IN NS ns2.boltwared.com.
;; ADDITIONAL SECTION:
ns1.boltwared.com. 14400 IN A 91.197.32.195
ns2.boltwared.com. 14400 IN A 91.197.32.196
Received 133 bytes from 91.197.32.195#53 in 35 ms
denis@denis-desktop:~$ host -a www.thechosen5.co.uk 91.197.32.196
Trying "www.thechosen5.co.uk"
Using domain server:
Name: 91.197.32.196
Address: 91.197.32.196#53
Aliases:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1792
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;www.thechosen5.co.uk. IN ANY
;; ANSWER SECTION:
www.thechosen5.co.uk. 14400 IN CNAME thechosen5.co.uk.
;; AUTHORITY SECTION:
thechosen5.co.uk. 86400 IN NS ns2.boltwared.com.
thechosen5.co.uk. 86400 IN NS ns1.boltwared.com.
;; ADDITIONAL SECTION:
ns1.boltwared.com. 14400 IN A 91.197.32.195
ns2.boltwared.com. 14400 IN A 91.197.32.196
Received 133 bytes from 91.197.32.196#53 in 40 ms
denis@denis-desktop:~$
So, the problem seems to be that demon is looking in the wrong place for
the dns server for thechosen5.co.uk, possibly (and I'm guessing at this
point) because the demon dns cache for ns1/ns2.boltwared.com is stale.
How and who to flag this up to at demon I do not know.
Rgds
Denis McMahon
Steve Rogerson
> As of 03:15 ns1/ns2 .boltwared.com are still not responding to dns
> queries for (www.)thechosen5.co.uk
What's kind of odd -and may be related - is that the Demon DNS servers are
returning a different address for ns2.boltwared.com to another DNS server.
Demon:
; <<>> DiG 9.6.1-P2-RedHat-9.6.1-13.P2.fc12 <<>> ns2.boltwared.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38022
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
;; QUESTION SECTION:
;ns2.boltwared.com. IN A
;; ANSWER SECTION:
ns2.boltwared.com. 1225 IN A 68.178.232.99
;; AUTHORITY SECTION:
boltwared.com. 821 IN NS ns13.domaincontrol.com.
boltwared.com. 821 IN NS ns14.domaincontrol.com.
;; Query time: 31 msec
;; SERVER: 158.152.1.58#53(158.152.1.58)
;; WHEN: Wed Dec 2 09:27:19 2009
;; MSG SIZE rcvd: 103
A.N. Other DNS server:
; <<>> DiG 9.2.4 <<>> ns2.boltwared.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15084
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1
;; QUESTION SECTION:
;ns2.boltwared.com. IN A
;; ANSWER SECTION:
ns2.boltwared.com. 172800 IN A 91.197.32.196
;; AUTHORITY SECTION:
boltwared.com. 172800 IN NS ns13.domaincontrol.com.
boltwared.com. 172800 IN NS ns14.domaincontrol.com.
;; ADDITIONAL SECTION:
ns13.domaincontrol.com. 60126 IN A 216.69.185.7
;; Query time: 29 msec
;; SERVER: 212.23.3.100#53(212.23.3.100)
;; WHEN: Wed Dec 2 09:27:16 2009
;; MSG SIZE rcvd: 119
The Demon DNS server is returning the same address for ns2 as ns1. They both
give the same for ns1.
Demon aren't alone. I tried out http://www.zonecheck.fr/ and they think the same.
I had a similar DNS problem before and it turned out to be a fault with DNS
server of the address I was trying to access. I managed to talk to them and
got them to fix it. Something to do with the nameserve not being definitive
for itself (probably the wrong words, but something like that).
The reason it was showing up with Demon and not others is the DNS software
that Demon use handled the error differently to other packages. If it is the
same problem, then it will mysteriously go away after a few days, but will
return again at some time in the future. I think it is to do with caching of
nameserver address, rather than the names themselves. I was given an eloquent
explanation, but I can't find it and certainly can't remember it.
Steve
Andy
Not Found here at 10:10
--
Andy Taylor [Editor, Austrian Philatelic Society].
Visit <URL:http://www.austrianphilately.com>
Simon Clubley
> In message <1ja2ijz.sm1mgw4cpvc3N%pe...@cara.demon.co.uk>, Peter
> Ceresole <pe...@cara.demon.co.uk> wrote
>>mark <ma...@martem.demon.co.uk> wrote:
>>
>>> >We can't do much to investigate your problem if you don't tell us the
>>> >actual website you're trying to access.
>>> >
>>>
>>> http://www.thechosen5.co.uk/
>>
>>Took a few seconds to connect (maybe 5 or 6) but it comes up fine here
>>at 2300.
>
> Not Found here at 10:10
I can't see it either when accessed via Demon but I can see it when
accessed from another part of the Internet:
From within the Demon network:
> www.thechosen5.co.uk
Server: 158.152.1.58
Address: 158.152.1.58#53
** server can't find www.thechosen5.co.uk: SERVFAIL
From outside of Demon:
> www.thechosen5.co.uk
Server: LOCALHOST
Address: 127.0.0.1
Non-authoritative answer:
Name: thechosen5.co.uk
Address: 91.197.32.195
Aliases: www.thechosen5.co.uk
Simon.
--
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980's technology to a 21st century world
Denis McMahon
> The reason it was showing up with Demon and not others is the DNS
> software that Demon use handled the error differently to other packages.
> If it is the same problem, then it will mysteriously go away after a few
> days, but will return again at some time in the future. I think it is to
> do with caching of nameserver address, rather than the names themselves.
> I was given an eloquent explanation, but I can't find it and certainly
> can't remember it.
Sounds plausible.
My scenario is that demon has / had the old nameserver addresses
(ns1/ns2.boltwared.com) and was trying those, which were giving the
servfail.
Demon simply returned this to the system requesting the lookup for
(www.)thechosen5.co.uk
Other isp's may have been going to *.gtld-servers.net on the initial
servfail, and were thus getting the correct / new / different server(s)
which were functional.
Whether this "stale cache" of the broken dns entry for the boltwared.com
nameservers is related to a previously reported problem with demon dns
servers I don't know. I did see what may have been a bit of slow dns
resolution last week, and had some flakiness on the dsl too.
Rgds
Denis McMahon
ia...@null.com
That is what you would expect to see from an apache webserver ,you are not
asking it for any particular webpage .I did try the index.XXX but it does
not have a page called that either .The above is nothing to do with dns.
Is there anything on this server that has been blocked for any reason ,just
a thought
Denis McMahon
It's the virtual hosting.
The server is set up to look at the website being requested and serve
the appropriate pages.
If you to it by ip you get the basic install page (although most hosters
would probably want to redirect to their hosting sales page).
The server probably hosts several tens or more websites.
Rgds
Denis McMahon
mark
McMahon <denis.m....@gmail.com> writes<Snipped helpful stuff>
Thank you.
I think I've got the gist of all that :)
Everything seems to be working at the moment.
--
Mark Roberts
hugh
Ceresole <pe...@cara.demon.co.uk> writes
"Internet Explorer cannot display the webpage"
--
hugh
It may be more complicated but is it better?
Peter Ceresole
> >I get that too. But entering <http://www.thechosen5.co.uk/> takes me
> >straight there.
> Interestingly I've just tried it and it fails
> "Internet Explorer cannot display the webpage"
Nope, tonight it's gone... It was there a short while ago.
But this might tally with the suggestion that there is something wrong
with the broadcasting of its IP address.
--
Peter