Check this out
1.) Do a direct query against ns1.loudcloud.com for wltx.com - Returns
66.54.32.202.
2.) Do a direct query against ns1.infi.net for wltx.com - Returns
66.54.32.202.
3.) Do a direct query against ns1.mindspring.net or ns2. or ns3 and the
query will in general 9 out of 10 times
Matt,
I think you are right. My guess is that for some reason they dropped the domain out
of the root servers for a period of time and the major isps grabed the worldnic
servers as being authoratative.
Not much we can do, other than wait...
Darrell
-- Original Message
I was able to resolve wltx.com just fine.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Darrell LaRock
Sent: Saturday, December 20, 2003 3:59 AM
To: [EMAIL PROTECTED]
Subject: [Declude.JunkMail] OT: DNS Issue (HELP)
This is off topic, but I need some
Hello Darrell,
Working from here. Denver, CO area.
Scott
Friday, December 19, 2003, 6:59:06 PM, you wrote:
Darrell This is off topic, but I need some help in a bad way to figure out a DNS
problem I am having that is preventing one of our sites from receiving mail and thier
web site from
Hello Darrell,
Email works too:
12:19 19:41 SMTP-(07540069) [x] Connecting socket to service SMTP on host wltx.com
using protocol tcp
12:19 19:41 SMTP-(07540069) [x] using source IP for arvadafire.com [65.125.147.225]
12:19 19:41 SMTP-(07540069) Info - Found wltx.com in DNS Cache
12:19 19:41
I am absolutly baffled.
Eathlink Dial-up - Does not work
Charter Cable Connection - Does not work
ATT T1 using local bind server - Works
Roadrunner Cable - Does not work
AOL - Intermittent.
Several users who replied - Works
Darrell
-- Original Message --
I'd say that the domain is fine at its new home; the question is what was
the TTL on the domain before it was moved?
I would go very little out on a limb and say that the folks with trouble to
wltx.com were cacheing the DNS for longer than the TTL on the domain, or it
was really high before the
Andrew,
One question that I have is the TTL stuff shouldnt matter since the zone files that
were moved over are the same. All we are doing is switching DNS providers right now.
Darrell
-- Original Message --
From: Colbeck, Andrew [EMAIL PROTECTED]
Service
and Clear DNS Cache...just a thought.
- Original Message -
From: Darrell LaRock [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, December 19, 2003 8:46 PM
Subject: Re: [Declude.JunkMail] OT: DNS Issue (HELP)
I am absolutly baffled.
Eathlink Dial-up - Does not work
Scott,
We duplicated the zone files between both providers. So all records are identical.
If the zone files are the same than all of the timeouts should not matter.
Check this out
1.) Do a direct query against ns1.loudcloud.com for wltx.com - Returns 66.54.32.202.
2.) Do a direct query
Scott,
On the DNSSTUFF, I used the cached ISP report looking at the NS record. What does it
mean when an ISP has the name server set to ns92.worldnic.com? Does this mean at one
time when the domain was looked up it was not resolved from the root servers?
ATT Worldnet #1
Darrell,
It looks like your name server records were maybe munged for a period of
time from a root update that is now fixed. Those munged records though
are being cached and they should get a good copy once they expire. This
might explain why all of us seem to be able to resolve your domain,
12 matches
Mail list logo
