Bob Goodwin: > I changed the router configuration to use 208.67.229.220:5353 and > 208.67.222.222:5353 and see the following: > > [root@box10 bobg]# dig www.bbc.co.uk > > ; <<>> DiG 9.9.3-rl.13207.22-P2-RedHat-9.9.3-5.P2.fc19 <<>> www.bbc.co.uk > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35870 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 > > ;; OPT PSEUDOSECTION: > ; EDNS: version: 0, flags:; udp: 4096 > ;; QUESTION SECTION: > ;www.bbc.co.uk. IN A > > ;; ANSWER SECTION: > www.bbc.co.uk. 176 IN CNAME www.bbc.net.uk. > www.bbc.net.uk. 182 IN A 212.58.246.93 > www.bbc.net.uk. 182 IN A 212.58.246.92 > > ;; Query time: 616 msec > ;; SERVER: 192.168.1.1#53(192.168.1.1) > ;; WHEN: Tue Nov 12 11:46:20 EST 2013 > ;; MSG SIZE rcvd: 100 > > As you say the cache is much faster, 2 ms as opposed to 616 ms. > > But I still don't know what DNS address it actually goes to, how do I > find that? Just to be clear, DNS means domain name *system* not *server*. So, are you asking you're not sure what DNS server has responded, or you don't know how to read the answers you got back from dig? Looking at your above dig results: Your command line asked whatever your computer's default DNS server was (configured in /etc/resolv.conf) to look up www.bbc.co.uk. The ANSWER section gives results about your query addresses. A query for www.bbc.co.uk gets a CNAME answer of www.bbc.net.uk (i.e. it says use that second name, instead). Followed by two answers for IPs for www.bbc.net.uk, saying to use either 212.58.246.93 or 212.58.246.92 (either will do). The QUERY TIME section says the server that answered was 192.168.1.1, so that would be the first DNS server address in your /etc/resolv.conf file. Second or third server addresses in that config file will only be consulted if the first one failed to respond, and there'd be a seriously long time-out period before that happened. Your router, at 192.168.1.1 may have tried to query 208.67.229.220:5353 and 208.67.222.222:5353 to find the results (I don't know if your router/modem can accept port numbers attached to the IPs, like that), and may have connected to them. Or, your ISP may have intercepted that. You might try using those IPs and ports with the dig command, directly. By default, dig will use your pre-configured DNS servers (in your /etc/resolv.conf file) unless you specify a server to query on its command line. That is *which* server to ask, not just what address you want to look up. -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
