Re: [Declude.JunkMail] OT: DNS Issue (HELP)
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 timeout. We can also duplicate this behavior on Charter and Road Runner. I can't even come up with a possible explanation... The zone files are the same That is odd. At first I thought that it was just a generic problem with their DNS servers, but they handle declude.com fine. Note that they are reporting a SERVER FAILURE response, which technically should only happen if their DNS servers fail for some reason. However, there are cases where BIND will return the SERVER FAILURE if it gets that message from the remote DNS server -- which could in theory have caused the problem. They may have 10 DNS servers at each IP, 9 of which have a cached SERVER FAILURE response, and 1 does not. Unfortunately, this bit of information doesn't offer a solution. 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 #1NS=ns1.infi.net. [TTL=1d 9h 38m 50s] NS=ns2.infi.net. [TTL=1d 9h 38m 50s] ATT Worldnet #2NS=ns1.infi.net. [TTL=1d 4h 18m 50s] NS=ns2.infi.net. [TTL=1d 4h 18m 50s] ATT Worldnet #1NS=ns1.infi.net. [TTL=1d 2h 53m 53s] NS=ns2.infi.net. [TTL=1d 2h 53m 53s] ATT Worldnet #2NS=ns91.worldnic.com. [TTL=10h 45m 11s] NS=ns92.worldnic.com. [TTL=10h 45m 11s] It means that one of ATT's DNS servers thinks that ns91.worldnic.com and ns92.worldnic.com are your DNS servers. If their servers are working properly, it means that about 38 hours earlier (the 48 hour TTL for .com NS records minus the 10+ hours left on their TTL) they connected to the .com parent servers and were told that ns91.worldnic.com and ns92.worldnic.com are the NS records for wltx.com. If you read Matt's response, I think he figured it out -- his explanation (corrupt information at the .com parent servers) sounds like it would fit what happened. -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers. Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection. Find out what you've been missing: Ask about our free 30-day evaluation. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
Re: [Declude.JunkMail] OT: DNS Issue (HELP)
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 -- From: Matthew Bramble [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Date: Sat, 20 Dec 2003 00:02:14 -0500 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, being that we aren't likely to have it cached being smaller providers, however the larger providers seem to have bad records for it because they hit your domain while the data was bad. Just guessing of course. If you have some local ISP's which are likely to have chached an earlier copy of the records, try querying their servers to see what it returns. I suspect that they will have a bad copy also, at least for a short period of time. I don't believe there is anything you can do about this if I am correct. Matt Darrell LaRock wrote: 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 #1NS=ns1.infi.net. [TTL=1d 9h 38m 50s] NS=ns2.infi.net. [TTL=1d 9h 38m 50s] ATT Worldnet #2NS=ns1.infi.net. [TTL=1d 4h 18m 50s] NS=ns2.infi.net. [TTL=1d 4h 18m 50s] ATT Worldnet #1NS=ns1.infi.net. [TTL=1d 2h 53m 53s] NS=ns2.infi.net. [TTL=1d 2h 53m 53s] ATT Worldnet #2NS=ns91.worldnic.com. [TTL=10h 45m 11s] NS=ns92.worldnic.com. [TTL=10h 45m 11s] Taking wild stabs in the dark :) Darrell -- Original Message -- From: R. Scott Perry [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Date: Fri, 19 Dec 2003 22:56:28 -0500 However, something is seriously wrong as the major ISP's can't resolve it (Earthlink, Charter, Some AOL Users, Road Runner). This occured right after the whois info was updated to the new authoratative servers. That's probably the problem. Once the first .com parent server gets the new NS records, it takes up to about 6 hours for all the other .com parent servers to get updated, and another 48 hours before TTL values expire on DNS servers throughout the world. Earthlink, Charter, and some other larger ISPs almost certainly have the old values cached, which will take up to 48 hours to expire after the change. During that time, they will be using the old NS records. -Scott --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
RE: [Declude.JunkMail] OT: DNS Issue (HELP)
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 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 loading. We recently (this week) switched the name servers from our current provider to another provider. The zone files are duplicate between providers. However, something is seriously wrong as the major ISP's can't resolve it (Earthlink, Charter, Some AOL Users, Road Runner). This occured right after the whois info was updated to the new authoratative servers. Now the crazy thing is I can resolve the site using the auth. servers, but not off one of Earthlink's or charters. The site is wltx.com. Can you resolve it? How can I verify that the site did not fall out of the root servers? Anyone else have any input? Darrell --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
Re: [Declude.JunkMail] OT: DNS Issue (HELP)
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 loading. Darrell We recently (this week) switched the name servers from our current provider to another provider. The zone files are duplicate between providers. Darrell However, something is seriously wrong as the major ISP's can't resolve it (Earthlink, Charter, Some AOL Users, Road Runner). This occured right after the whois info was updated to the new Darrell authoratative servers. Darrell Now the crazy thing is I can resolve the site using the auth. servers, but not off one of Earthlink's or charters. Darrell The site is wltx.com. Darrell Can you resolve it? Darrell How can I verify that the site did not fall out of the root servers? Anyone else have any input? Darrell Darrell Darrell --- Darrell [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] Darrell --- Darrell This E-mail came from the Declude.JunkMail mailing list. To Darrell unsubscribe, just send an E-mail to [EMAIL PROTECTED], and Darrell type unsubscribe Declude.JunkMail. The archives can be found Darrell at http://www.mail-archive.com. -- Scottmailto:[EMAIL PROTECTED] --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
Re: [Declude.JunkMail] OT: DNS Issue (HELP)
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 SMTP-(07540069) Connect wltx.com [209.94.11.105:25] (1) 12:19 19:41 SMTP-(07540069) 220 mail1.gannett-tv.com (IMail 7.15 56973-6) NT-ESMTP Server X1 12:19 19:41 SMTP-(07540069) EHLO arvadafire.com 12:19 19:41 SMTP-(07540069) 250-mail1.gannett-tv.com says hello 12:19 19:41 SMTP-(07540069) 250-SIZE 2000 12:19 19:41 SMTP-(07540069) 250-8BITMIME 12:19 19:41 SMTP-(07540069) 250-DSN 12:19 19:41 SMTP-(07540069) 250-ETRN 12:19 19:41 SMTP-(07540069) 250-AUTH LOGIN CRAM-MD5 12:19 19:41 SMTP-(07540069) 250-AUTH=LOGIN 12:19 19:41 SMTP-(07540069) 250 EXPN 12:19 19:41 SMTP-(07540069) MAIL FROM:[EMAIL PROTECTED] 12:19 19:41 SMTP-(07540069) 250 ok 12:19 19:41 SMTP-(07540069) RCPT To:[EMAIL PROTECTED] 12:19 19:41 SMTP-(07540069) 250 ok its for [EMAIL PROTECTED] 12:19 19:41 SMTP-(07540069) DATA 12:19 19:41 SMTP-(07540069) 354 ok, send it; end with CRLF.CRLF 12:19 19:41 SMTP-(07540069) . 12:19 19:41 SMTP-(07540069) 250 Message queued 12:19 19:41 SMTP-(07540069) rdeliver wltx.com [EMAIL PROTECTED] (1) [EMAIL PROTECTED] 827 12:19 19:41 SMTP-(07540069) QUIT 12:19 19:41 SMTP-(07540069) 221 Goodbye 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 loading. Darrell We recently (this week) switched the name servers from our current provider to another provider. The zone files are duplicate between providers. Darrell However, something is seriously wrong as the major ISP's can't resolve it (Earthlink, Charter, Some AOL Users, Road Runner). This occured right after the whois info was updated to the new Darrell authoratative servers. Darrell Now the crazy thing is I can resolve the site using the auth. servers, but not off one of Earthlink's or charters. Darrell The site is wltx.com. Darrell Can you resolve it? Darrell How can I verify that the site did not fall out of the root servers? Anyone else have any input? Darrell Darrell Darrell --- Darrell [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] Darrell --- Darrell This E-mail came from the Declude.JunkMail mailing list. To Darrell unsubscribe, just send an E-mail to [EMAIL PROTECTED], and Darrell type unsubscribe Declude.JunkMail. The archives can be found Darrell at http://www.mail-archive.com. -- Scottmailto:[EMAIL PROTECTED] --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
Re: [Declude.JunkMail] OT: DNS Issue (HELP)
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 -- From: Scott Winberg [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Date: Fri, 19 Dec 2003 19:13:55 -0700 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 loading. Darrell We recently (this week) switched the name servers from our current provider to another provider. The zone files are duplicate between providers. Darrell However, something is seriously wrong as the major ISP's can't resolve it (Earthlink, Charter, Some AOL Users, Road Runner). This occured right after the whois info was updated to the new Darrell authoratative servers. Darrell Now the crazy thing is I can resolve the site using the auth. servers, but not off one of Earthlink's or charters. Darrell The site is wltx.com. Darrell Can you resolve it? Darrell How can I verify that the site did not fall out of the root servers? Anyone else have any input? Darrell Darrell Darrell --- Darrell [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] Darrell --- Darrell This E-mail came from the Declude.JunkMail mailing list. To Darrell unsubscribe, just send an E-mail to [EMAIL PROTECTED], and Darrell type unsubscribe Declude.JunkMail. The archives can be found Darrell at http://www.mail-archive.com. -- Scottmailto:[EMAIL PROTECTED] --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
RE: [Declude.JunkMail] OT: DNS Issue (HELP)
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 change, and they're respecting that. If you didn't already know it, this site, courtesy of declude.com, is a wonderful resource: http://www.dnsreport.com/ Andrew 8) -Original Message- From: Darrell LaRock [mailto:[EMAIL PROTECTED] Sent: Friday, December 19, 2003 5:59 PM To: [EMAIL PROTECTED] Subject: [Declude.JunkMail] OT: DNS Issue (HELP) 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 loading. We recently (this week) switched the name servers from our current provider to another provider. The zone files are duplicate between providers. However, something is seriously wrong as the major ISP's can't resolve it (Earthlink, Charter, Some AOL Users, Road Runner). This occured right after the whois info was updated to the new authoratative servers. Now the crazy thing is I can resolve the site using the auth. servers, but not off one of Earthlink's or charters. The site is wltx.com. Can you resolve it? How can I verify that the site did not fall out of the root servers? Anyone else have any input? Darrell --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
RE: [Declude.JunkMail] OT: DNS Issue (HELP)
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] Reply-To: [EMAIL PROTECTED] Date: Fri, 19 Dec 2003 18:45:00 -0800 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 change, and they're respecting that. If you didn't already know it, this site, courtesy of declude.com, is a wonderful resource: http://www.dnsreport.com/ Andrew 8) -Original Message- From: Darrell LaRock [mailto:[EMAIL PROTECTED] Sent: Friday, December 19, 2003 5:59 PM To: [EMAIL PROTECTED] Subject: [Declude.JunkMail] OT: DNS Issue (HELP) 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 loading. We recently (this week) switched the name servers from our current provider to another provider. The zone files are duplicate between providers. However, something is seriously wrong as the major ISP's can't resolve it (Earthlink, Charter, Some AOL Users, Road Runner). This occured right after the whois info was updated to the new authoratative servers. Now the crazy thing is I can resolve the site using the auth. servers, but not off one of Earthlink's or charters. The site is wltx.com. Can you resolve it? How can I verify that the site did not fall out of the root servers? Anyone else have any input? Darrell --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
Re: [Declude.JunkMail] OT: DNS Issue (HELP)
From an earthlink dsl user Ping test 1 wltx.com 56 60 Success 2 wltx.com 56 60 Success 3 wltx.com 56 60 Success 4 wltx.com 56 60 Success 5 wltx.com 56 60 Success trace rt 1 0 0 172.16.0.254 2 35 35 172.31.255.251 3 30 -5 192.168.5.53 4 30 0 209.247.34.177 ge-8-0-131.ipcolo1.Chicago1.Level3.net 5 30 0 4.68.112.201 so-7-0-0.bbr1.Chicago1.Level3.net 6 70 40 64.159.0.234 so-0-0-0.bbr1.NewYork1.Level3.net 7 60 -10 64.159.17.3 ge-6-0.ipcolo1.NewYork1.Level3.net 8 70 10 209.244.13.198 so-10-0.hsa1.Newark1.Level3.net 9 65 -5 64.156.0.26 unknown.Level3.net 10 Timed out 11 70 5 66.54.32.202 gannetttv.cust.loudcloud.com Official name: wltx.com (stack DNS) IP address: 66.54.32.202 wltx.com. (Earthlink DNS) nameserver = ns1.infi.net. wltx.com. nameserver = ns2.infi.net. wltx.com. 66.54.32.202 Whois Server Version 1.3 Domain names in the .com and .net domains can now be registered with many different competing registrars. Go to http://www.internic.net for detailed information. Domain Name: WLTX.COM Registrar: NETWORK SOLUTIONS, INC. Whois Server: whois.networksolutions.com Referral URL: http://www.networksolutions.com Name Server: NS1.INFI.NET Name Server: NS2.INFI.NET Status: ACTIVE Updated Date: 18-dec-2003 Creation Date: 19-dec-1997 Expiration Date: 18-dec-2007 Scan (DNS,FTP,HTTP,POP3,SMTP,ECHO,GOPHER,NNTP,TIME,IMAP) 066.054.032.202 HTTP gannetttv.cust.loudcloud.com Stupid question, what are you testing with? W2k? Turn of DNS Client 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 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 -- From: Scott Winberg [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Date: Fri, 19 Dec 2003 19:13:55 -0700 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 loading. Darrell We recently (this week) switched the name servers from our current provider to another provider. The zone files are duplicate between providers. Darrell However, something is seriously wrong as the major ISP's can't resolve it (Earthlink, Charter, Some AOL Users, Road Runner). This occured right after the whois info was updated to the new Darrell authoratative servers. Darrell Now the crazy thing is I can resolve the site using the auth. servers, but not off one of Earthlink's or charters. Darrell The site is wltx.com. Darrell Can you resolve it? Darrell How can I verify that the site did not fall out of the root servers? Anyone else have any input? Darrell Darrell Darrell --- Darrell [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] Darrell --- Darrell This E-mail came from the Declude.JunkMail mailing list. To Darrell unsubscribe, just send an E-mail to [EMAIL PROTECTED], and Darrell type unsubscribe Declude.JunkMail. The archives can be found Darrell at http://www.mail-archive.com. -- Scottmailto:[EMAIL PROTECTED] --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
Re: [Declude.JunkMail] OT: DNS Issue (HELP)
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 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 timeout. We can also duplicate this behavior on Charter and Road Runner. I can't even come up with a possible explanation... The zone files are the same Thanks Darrell -- Original Message -- From: R. Scott Perry [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Date: Fri, 19 Dec 2003 22:56:28 -0500 However, something is seriously wrong as the major ISP's can't resolve it (Earthlink, Charter, Some AOL Users, Road Runner). This occured right after the whois info was updated to the new authoratative servers. That's probably the problem. Once the first .com parent server gets the new NS records, it takes up to about 6 hours for all the other .com parent servers to get updated, and another 48 hours before TTL values expire on DNS servers throughout the world. Earthlink, Charter, and some other larger ISPs almost certainly have the old values cached, which will take up to 48 hours to expire after the change. During that time, they will be using the old NS records. -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers. Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection. Find out what you've been missing: Ask about our free 30-day evaluation. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
Re: [Declude.JunkMail] OT: DNS Issue (HELP)
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 #1NS=ns1.infi.net. [TTL=1d 9h 38m 50s] NS=ns2.infi.net. [TTL=1d 9h 38m 50s] ATT Worldnet #2NS=ns1.infi.net. [TTL=1d 4h 18m 50s] NS=ns2.infi.net. [TTL=1d 4h 18m 50s] ATT Worldnet #1NS=ns1.infi.net. [TTL=1d 2h 53m 53s] NS=ns2.infi.net. [TTL=1d 2h 53m 53s] ATT Worldnet #2NS=ns91.worldnic.com. [TTL=10h 45m 11s] NS=ns92.worldnic.com. [TTL=10h 45m 11s] Taking wild stabs in the dark :) Darrell -- Original Message -- From: R. Scott Perry [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Date: Fri, 19 Dec 2003 22:56:28 -0500 However, something is seriously wrong as the major ISP's can't resolve it (Earthlink, Charter, Some AOL Users, Road Runner). This occured right after the whois info was updated to the new authoratative servers. That's probably the problem. Once the first .com parent server gets the new NS records, it takes up to about 6 hours for all the other .com parent servers to get updated, and another 48 hours before TTL values expire on DNS servers throughout the world. Earthlink, Charter, and some other larger ISPs almost certainly have the old values cached, which will take up to 48 hours to expire after the change. During that time, they will be using the old NS records. -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers. Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection. Find out what you've been missing: Ask about our free 30-day evaluation. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
Re: [Declude.JunkMail] OT: DNS Issue (HELP)
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, being that we aren't likely to have it cached being smaller providers, however the larger providers seem to have bad records for it because they hit your domain while the data was bad. Just guessing of course. If you have some local ISP's which are likely to have chached an earlier copy of the records, try querying their servers to see what it returns. I suspect that they will have a bad copy also, at least for a short period of time. I don't believe there is anything you can do about this if I am correct. Matt Darrell LaRock wrote: 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 #1NS=ns1.infi.net. [TTL=1d 9h 38m 50s] NS=ns2.infi.net. [TTL=1d 9h 38m 50s] ATT Worldnet #2NS=ns1.infi.net. [TTL=1d 4h 18m 50s] NS=ns2.infi.net. [TTL=1d 4h 18m 50s] ATT Worldnet #1NS=ns1.infi.net. [TTL=1d 2h 53m 53s] NS=ns2.infi.net. [TTL=1d 2h 53m 53s] ATT Worldnet #2NS=ns91.worldnic.com. [TTL=10h 45m 11s] NS=ns92.worldnic.com. [TTL=10h 45m 11s] Taking wild stabs in the dark :) Darrell -- Original Message -- From: R. Scott Perry [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Date: Fri, 19 Dec 2003 22:56:28 -0500 However, something is seriously wrong as the major ISP's can't resolve it (Earthlink, Charter, Some AOL Users, Road Runner). This occured right after the whois info was updated to the new authoratative servers. That's probably the problem. Once the first .com parent server gets the new NS records, it takes up to about 6 hours for all the other .com parent servers to get updated, and another 48 hours before TTL values expire on DNS servers throughout the world. Earthlink, Charter, and some other larger ISPs almost certainly have the old values cached, which will take up to 48 hours to expire after the change. During that time, they will be using the old NS records. -Scott --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
