[ale] DNS problems

[David Brooks]

Part of the problem appears to be that your nameserver is rather
unreachable.

13:13:18  db at flexo:(~)$ dig @63.168.35.79 ns1.jamfo.com

; <<>> DiG 9.1.0 <<>> @63.168.35.79 ns1.jamfo.com
;; global options:  printcmd
;; connection timed out; no servers could be reached

...That would be coming from AT&T.  Coming over SprintLink (which I'm
guessing is your upstream), I still can't query your server, however
SprintLink's cache servers report the correct IP address.  Something
tells me the DNS service on your server died, and your upstream's
servers (and maybe a few others) cached it, but nothing else had time
to.

I'm digging what I guess to be your DNS server as reported by
a.gtld-servers.net:

13:19:21  db at flexo:(~)$ dig @a.gtld-servers.net ns1.jamfo.com
[.. misc ..]
;; ANSWER SECTION:
ns1.jamfo.com.          172800  IN      A       63.168.35.79

;; AUTHORITY SECTION:
jamfo.com.              172800  IN      NS      ns1.jamfo.com.
[.. misc ..]

I would check the DNS service on ns1.jamfo.com.  I can't query it.  See
if you can locally.  Also, not that this is causing your problem, but
register.com reports both ns1.and ns2.jamfo.com, yet there's only one
SOA record for your domain.

Hope this helps.

-Dave








On Fri, 2002-01-04 at 11:42, Gene Matthews wrote:
> Hello all,
> 
> I have a name server that I am maintaining (ns1.jamfo.com) that is 
> authoritative for the jamfo.com domain.  I THINK i have everything 
> configured correctly, however a lot of other name servers don't seem to 
> be able to resolve some jamfo.com names.  I know it takes some time for 
> things to propogate, however, some of these changes have been in place 
> for over a week.
> 
> Some name servers (Adelphia's for one, 24.53.64.18) can resolve every 
> name in my zone file fine, some others can only resolve some of them.
> 
> Sprint and mindspring don't seem to be resolving much.
> 
> For instance,
> 
> jamfo.com
> *.jamfo.com
> *.media.jamfo.com
> 
> should all resolve to a given IP (not the same one though).  They do, 
> obviously, if i point directly at ns1.jamfo.com to resolve them.
> 
> Would the timeout below indicate some config problem on my side?  I'm 
> not completely ignorant of DNS, but I'm not a guru either.  I'd 
> appreciate any thoughts/suggestions anyone may have.
> 
> Thanks,
> 
> Gene
> 
> 
> # nslookup
> Note:  nslookup is deprecated and may be removed from future releases.
> Consider using the `dig' or `host' programs instead.  Run nslookup with
> the `-sil[ent]' option to prevent this message from appearing.
>  > server 204.117.214.10
> Default server: 204.117.214.10
> Address: 204.117.214.10#53
>  > jamfo.com
> ;; connection timed out; no servers could be reached
>  > wb.jamfo.com
> Server: 
> 	204.117.214.10
> Address: 
> 204.117.214.10#53
> 
> ** server can't find wb.jamfo.com: SERVFAIL
>  > gene.jamfo.com
> ;; connection timed out; no servers could be reached
>  > server 24.53.64.18
> Default server: 24.53.64.18
> Address: 24.53.64.18#53
>  > jamfo.com
> Server: 
> 	24.53.64.18
> Address: 
> 24.53.64.18#53
> 
> Name: 
> jamfo.com
> Address: 63.168.35.72
>  > wb.jamfo.com
> Server: 
> 	24.53.64.18
> Address: 
> 24.53.64.18#53
> 
> Non-authoritative answer:
> wb.jamfo.com 
> canonical name = prodweb.jamfo.com.
> Name: 
> prodweb.jamfo.com
> Address: 63.168.35.73
>  > wb.media.jamfo.com
> Server: 
> 	24.53.64.18
> Address: 
> 24.53.64.18#53
> 
> wb.media.jamfo.com 
> canonical name = prodmedia.jamfo.com.
> Name: 
> prodmedia.jamfo.com
> Address: 63.168.35.74
> 
> 
> ---
> This message has been sent through the ALE general discussion list.
> See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
> sent to listmaster at ale dot org.
> 
> 
-- 
david a. brooks
* systems administrator
* stayonline.net
* voice: .. 770/933-0600 x217
* email: .. db at stayonline.net
* :wq!


---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.