Problem resolving www.futureshop.ca
Mark Andrews
Mark_Andrews at isc.org
Wed May 25 15:28:54 UTC 2005
> BIND Users:
>
> I am no longer able to access www.futureshop.ca (or www.bestbuy.ca) while
> using a Local BIND (Caching Nameserver), which I find strange since up
> until a few months ago I could (only recently did I notice this appears to
> be an "issue" with my Local BIND being able to Resolve these particula
> addresses)!!! If I use my Provider's Nameservers directly or indirectly
> as FORWARDERs for the Local BIND the above addresses do resolve:
>
> -----------------------------------------------------------------------------
> ---
> ; <<>> DiG 9.2.1 <<>> www.futureshop.ca
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50486
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
>
> ;; QUESTION SECTION:
> ;www.futureshop.ca. IN A
>
> ;; ANSWER SECTION:
> www.futureshop.ca. 10 IN A 199.60.115.193
>
> ;; AUTHORITY SECTION:
> futureshop.ca. 33 IN NS dns2.cidc.telus.com.
> futureshop.ca. 33 IN NS dns1.cidc.telus.com.
>
> ;; ADDITIONAL SECTION:
> dns1.cidc.telus.com. 78832 IN A 216.123.224.131
> dns2.cidc.telus.com. 27007 IN A 66.203.199.203
>
> ;; Query time: 48 msec
> ;; SERVER: 127.0.0.1#53(127.0.0.1)
> ;; WHEN: Wed May 25 01:33:36 2005
> ;; MSG SIZE rcvd: 135
> -----------------------------------------------------------------------------
> ---
>
> Although deeper DNS Traces fail while attempting to access
> dns1.cidc.telus.com/dns2.cidc.telus.com directly:
>
> -----------------------------------------------------------------------------
> ---
> ; <<>> DiG 9.2.1 <<>> +trace www.futureshop.ca
> ;; global options: printcmd
> . 484175 IN NS F.ROOT-SERVERS.NET.
> . 484175 IN NS G.ROOT-SERVERS.NET.
> . 484175 IN NS H.ROOT-SERVERS.NET.
> . 484175 IN NS I.ROOT-SERVERS.NET.
> . 484175 IN NS J.ROOT-SERVERS.NET.
> . 484175 IN NS K.ROOT-SERVERS.NET.
> . 484175 IN NS L.ROOT-SERVERS.NET.
> . 484175 IN NS M.ROOT-SERVERS.NET.
> . 484175 IN NS A.ROOT-SERVERS.NET.
> . 484175 IN NS B.ROOT-SERVERS.NET.
> . 484175 IN NS C.ROOT-SERVERS.NET.
> . 484175 IN NS D.ROOT-SERVERS.NET.
> . 484175 IN NS E.ROOT-SERVERS.NET.
> ;; Received 436 bytes from 127.0.0.1#53(127.0.0.1) in 83 ms
>
> ca. 172800 IN NS CA05.CIRA.ca.
> ca. 172800 IN NS CA06.CIRA.ca.
> ca. 172800 IN NS NS-EXT.ISC.ORG.
> ca. 172800 IN NS CA01.CIRA.ca.
> ca. 172800 IN NS CA02.CIRA.ca.
> ca. 172800 IN NS CA04.CIRA.ca.
> ;; Received 287 bytes from 192.5.5.241#53(F.ROOT-SERVERS.NET) in 52 ms
>
> futureshop.ca. 86400 IN NS dns1.cidc.telus.com.
> futureshop.ca. 86400 IN NS dns2.cidc.telus.com.
> ;; Received 87 bytes from 129.33.164.84#53(CA05.CIRA.ca) in 50 ms
>
> ;; connection timed out; no servers could be reached
> -----------------------------------------------------------------------------
> ---
>
> I am further confounded since similar Traces from other providers do NOT
> exhibit this "problem"... What new "feature" might be Provider Specific
> such that a Local BIND is unable to receive data directly (but ONLY in a
> limited case)???
>
> Lawrence Houston -- (bind at greenfield.dyndns.org)
>
>
>
You most probably have a routing / firewall problem between you
and those servers.
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews at isc.org
More information about the bind-users
mailing list