|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Matthew Dempsky (matthew
dempsky.org)
Date: Thu Oct 02 2008 - 13:36:32 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Oct 2, 2008 at 8:55 AM, Jack Woehr <jax
well.com> wrote:
> The website http://www.oorexx.org 9 times out of ten does not resolve for
> me.
I think they setup a CNAME record for *.oorexx.org pointing to
208.34.240.200 instead of an A record. The planetdomain.com servers
respond to A and ANY queries for www.oorexx.org with an A record as
expected, but queries for any other hosts (e.g., xyzzy.oorexx.org)
yield the CNAME record as do explicit CNAME queries for
www.oorexx.org.
Probably what's happening is your cache is ending up with a CNAME
record for www.oorexx.org, so future A queries end up trying to
instead resolve "208.34.240.200" (because CNAME records take
precedence over anything else), which it then doesn't know how to
resolve.
Ask the oorexx.org team to double check that there's no CNAME records
for *.oorexx.org where they meant to configure an A record. They
probably either meant "*.oorexx.org CNAME www.oorexx.org" or
"*.oorexx.org A 208.34.240.200", but "*.oorexx.org CNAME
208.34.240.200" is going to break for any caches that don't internally
handle IP address literals.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]