Problem resolving www.futureshop.ca

Thu May 26 20:32:12 UTC 2005

On Thu, 2005-05-26 at 11:08 -0700, kevinr at hutchtel.net wrote:
> I have a customer that is having the same problem. They have called a
> friend in another town who is not having problems getting to
> www.manheim.com. From my output below it looks like it is the
> manheim.com nameservers that are not responding.
> 
> Below is the output from my trace:
> 
> [root at mislab1 root]# dig +trace manheim.com
> 
> ; <<>> DiG 9.2.2 <<>> +trace manheim.com
> ;; global options:  printcmd
> .                       180574  IN      NS      M.ROOT-SERVERS.NET.
> .                       180574  IN      NS      I.ROOT-SERVERS.NET.
> .                       180574  IN      NS      E.ROOT-SERVERS.NET.
> .                       180574  IN      NS      D.ROOT-SERVERS.NET.
> .                       180574  IN      NS      A.ROOT-SERVERS.NET.
> .                       180574  IN      NS      H.ROOT-SERVERS.NET.
> .                       180574  IN      NS      C.ROOT-SERVERS.NET.
> .                       180574  IN      NS      G.ROOT-SERVERS.NET.
> .                       180574  IN      NS      F.ROOT-SERVERS.NET.
> .                       180574  IN      NS      B.ROOT-SERVERS.NET.
> .                       180574  IN      NS      J.ROOT-SERVERS.NET.
> .                       180574  IN      NS      K.ROOT-SERVERS.NET.
> .                       180574  IN      NS      L.ROOT-SERVERS.NET.
> ;; Received 436 bytes from 66.103.161.102#53(66.103.161.102) in 2 ms
> 
> com.                    172800  IN      NS      A.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      G.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      H.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      C.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      I.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      B.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      D.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      L.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      F.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      J.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      K.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      E.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      M.GTLD-SERVERS.NET.
> ;; Received 489 bytes from 202.12.27.33#53(M.ROOT-SERVERS.NET) in 135
> ms
> 
> manheim.com.            172800  IN      NS      ns1.manheim.com.
> manheim.com.            172800  IN      NS      ns2.manheim.com.
> ;; Received 97 bytes from 192.5.6.30#53(A.GTLD-SERVERS.NET) in 55 ms
> 
> ;; connection timed out; no servers could be reached
> 
> 
> 
> Lawrence Houston wrote:
> > On Wed, 25 May 2005, James Philpott wrote:
> >
> > > Ensure that you have port 53 tcp/udp enabled at any route point/firewall
> > > between that machine and the Internet.
> >
> > Todate this is the first "persistent" instance of my Local BIND being
> > unable to access a specific Nameserver to resolve specific Hostnames
> > (other Hostnames remain resolvable), hence I assume Port 53 tcp/udp on my
> > Debian Firewall/Router must be "open" (what exactly my Provider is up to
> > is another question???)...  As a "test" I replaced the Debian BOX with a
> > GNAT Box, but the "problem" remained!
> >
> > > You could also try dumping the cache of your local cache server and then
> > > grep for 'futureshop' or 'bestbuy'. In the data of a cache dump it is
> > > fairly easy to see where the problem is if it is caching data that is
> > > affecting you (e.g. negative response, bad referral, etc...).
> >
> > After a dig +trace run GREP found no instances of "futureshop" or
> > "bestbuy" in my Local BIND's Cache...  This actually appears to be a
> > problem reaching the dns1.cidc.telus.com/dns2.cidc.telus.com Nameservers
> > from my location!!!  Hence there maybe nothing much I can do from my
> > end???
> > 
> > Lawrence Houston  --  (bind at greenfield.dyndns.org)
> 

[tazman at inyoureyes ~]$ dig @ns1.manheim.com manheim.com

; <<>> DiG 9.2.5 <<>> @ns1.manheim.com manheim.com
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50259
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;manheim.com.                   IN      A

;; ANSWER SECTION:
manheim.com.            180     IN      A       198.5.152.15

;; AUTHORITY SECTION:
manheim.com.            1800    IN      NS      ns1.manheim.com.
manheim.com.            1800    IN      NS      ns2.manheim.com.

;; ADDITIONAL SECTION:
ns1.manheim.com.        180     IN      A       67.97.218.11
ns2.manheim.com.        3600    IN      A       67.97.218.5

;; Query time: 35 msec
;; SERVER: 67.97.218.11#53(67.97.218.11)
;; WHEN: Thu May 26 16:31:14 2005
;; MSG SIZE  rcvd: 113

[tazman at inyoureyes ~]$
[tazman at inyoureyes ~]$ dig @ns2.manheim.com manheim.com

; <<>> DiG 9.2.5 <<>> @ns2.manheim.com manheim.com
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27300
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;manheim.com.                   IN      A

;; ANSWER SECTION:
manheim.com.            180     IN      A       198.5.152.15

;; AUTHORITY SECTION:
manheim.com.            1800    IN      NS      ns1.manheim.com.
manheim.com.            1800    IN      NS      ns2.manheim.com.

;; ADDITIONAL SECTION:
ns1.manheim.com.        180     IN      A       67.97.218.11
ns2.manheim.com.        3600    IN      A       67.97.218.5

;; Query time: 33 msec
;; SERVER: 67.97.218.5#53(67.97.218.5)
;; WHEN: Thu May 26 16:31:53 2005
;; MSG SIZE  rcvd: 113

[tazman at inyoureyes ~]$

Look fine from here.

Ted