DNS server chain breakdown
Posted on 2011-05-05
Hi, I'd like to connect with someone who understands DNS better than I do!
I'm administering a SBS 2011 server. It has some websites on it, and it serves a small domain. SBS controls a wireless router, and I have made some DNS entries so that I can browse locally hosted sites. Currently everything is working fine, except for a little DNS problem. I can browse intranet and internet sites fine, but when I try to get to one particular site, it can't display the page. The page is for the ISP in this case, so it is wrecking a user's access to their webmail.
So this is odd, no? General internet browsing is ok, but not for the main page of the Internet Service Provider. In this case the ISP is shaw.ca.
Once I tried to reset the modem and router, by power cycle, and this restored access to shaw.ca - but recently I reset it and it still can't access that site. I'm thinking that something I've done has altered DNS lookup such that it can't find shaw.ca.
It would be great if I could work with an expert to learn about DNS in this applied way: using tests to see that DNS queries are being properly answered. I'd like to review the sequence of DNS servers, that are used to get to a page.
About a decade ago, I learned to use tracert, so here's my initial info:
tracert to locally hosted site: shows one hop to local NIC's ip address.
tracert to shaw.ca: replies "unable to resolve target system name shaw.ca
tracert to cnn.com first resolves to a specific IP address, and then returns a series of hops, starting with the domain router, then the ISP default gateway, then a series of 5 ip addresses, and then it goes to Request timed out.
I see a similar sequence with other well known sites which I can also browse to.
So, anyone willing to work with me in a trouble shooting format, to learn the cause of the failure to resolve the address for shaw.ca?