Server not being found error

[Alan B]

No, 11 hops is not long.

[marksalehouse]

That is what I thought - considering it hit Dublin for some reason! It should only have gone Belfast - Glasgow - Manchester then a BTconnect Router and back again. I will try it again later.

[marksalehouse]

I am now off that IP, and I have no idea why it was listed to me. I go Belfast - Edinburgh too quick to be measured.

M

[Vladimir.B]

Apart from that, what should I be looking for?

Please read this: http://en.wikipedia.org/wiki/Glue_re...d_glue_records


I have tuned up bind and DNS zones on our DNS cluster servers, please check how it is working now.

[Alan B]

Vladimir:

I understand well about glue records. Any glue records in this case are not within Mark's control, since he is not using personal nameservers. He has named WHB nameservers:

ns100.whbdns.com.
ns101.whbdns.com.

In my case, where I use personal nameservers under my main reseller domain for all my client domains, glue records are important and can be affected by my setup. I ensure that I have A records for each of my personal nameservers in my main reseller domain's DNS Zone. If I were using WHB named nameservers, then I could not do such a thing.

[marksalehouse]

Vladimir:

I understand well about glue records. Any glue records in this case are not within Mark's control, since he is not using personal nameservers. He has named WHB nameservers:

ns100.whbdns.com.
ns101.whbdns.com.

In my case, where I use personal nameservers under my main reseller domain for all my client domains, glue records are important and can be affected by my setup. I ensure that I have A records for each of my personal nameservers in my main reseller domain's DNS Zone. If I were using WHB named nameservers, then I could not do such a thing.

Thanks Alan, and thanks Vladimir - I also found this:

Broken resolvers
An additional level of complexity emerges when resolvers violate the rules of the DNS protocol. A number of large ISPs have configured their DNS servers to violate rules (presumably to allow them to run on less-expensive hardware than a fully-compliant resolver), such as by disobeying TTLs, or by indicating that a domain name does not exist just because one of its name servers does not respond.[9]

MAXIM:Thanks for notifying about the error. The technicians are aware of the problem and currently investigating.

We will update this thread with the results.

Any more word?

Mark

[Maxim M.]

As Vladimir said, some maintenance had been done on DNS cluster servers.
Are you still receiving the error?

[marksalehouse]

Not as yet Maxim. I am off to bed soon. I will be logging on tomorrow to do a few things and will check the stability.

Thanks to all for their support here.

Mark

[marksalehouse]

UPDATE:

I know it is too early to tell, but access to webmail/Cpanel is quicker. I checked the error log and found these:

[Thu Sep 03 08:22:05 2009] [error] [client 90.214.11.87] File does not exist: /home/*/public_html/forum/styles/Iconic_Dark/templateli class=,
referer: http://www.*.co.uk/forum/posting.php...27b086a4&t=219

[Thu Sep 03 03:51:42 2009] [error] [client 117.8.143.97] File does not exist: /home/*/public_html/forum/gallery

Gallery is hidden behind the PHPBB Forum and is members only. I did a Neotrace and found the IP to be Peking, so obviously a spam/hacker.

However, the first one still shows mixed URL/HTML. Neotrace shows about 20 hops all over the UK so I guess that is a spammer trying to keep hidden. I guess the 20 hops may have something to do with the error.

At least todays error list is not huge.

I will keep an eye on things.

Mark

[marksalehouse]

GREAT!
Everything going fine. The error list only shows spammers trying to get where they should not. It has been working fine all day.

Except just now.

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, webmaster@*.co.uk and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.8i DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server at www.strictlybdsm.co.uk Port 80

ROFL!

Always something.

Mark

________________________________

[Fri Sep 04 18:21:09 2009] [alert] [client 86.158.121.154] /home/strict1a/public_html/.htaccess: ErrorDocument takes two arguments, Change responses for HTTP errors

Renamed .htaccess and solved the fault.

the problem was

ErrorDocument 500 /500.shtmldeny from 117.8.131.2

What I had done was use the Cpanel to deny what appears to be a spam/attack IP from Peking. For some reason the HTaccess line was wrong.

I hope this helps others!

Mark