> Eric Wood wrote: > > > Has anyone seen a fix for this? Even though my dns server can resolve > > eweek.com, It can't resolve "e.staples-deals.com". <snip> > > Any ideas on how to track this down? > > I would run named in debug mode on @mydnsserver and check the logs. At > least as a start. (Make sure that the initial cache file is correct and up to date, then) This is a good idea, but first may I suggest that your problem might be with "mydnsserver", as I had no problems resolving the name to an IP with the command: >>> % dig e.staples-deals.com >>> ; <<>> DiG 9.2.4 <<>> e.staples-deals.com >>> ;; global options: printcmd! >>> ;; Got answer: >>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37847 >>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 >>> >>> ;; QUESTION SECTION: >>> ;e.staples-deals.com. IN A >>> >>> ;; ANSWER SECTION: >>> e.staples-deals.com. 3600 IN A 63.210.43.103 >>> >>> ;; AUTHORITY SECTION: >>> e.staples-deals.com. 3600 IN NS >>> ns10.customer.level3.net. >>> e.staples-deals.com. 3600 IN NS >>> ns11.customer.level3.net. >>> >>> ;; ADDITIONAL SECTION: >>> ns10.customer.level3.net. 172800 IN A 209.244.4.149 >>> ns11.customer.level3.net. 172800 IN A 209.244.4.180 >>> >>> ;; Query time: 1512 msec >>> ;; SERVER: 127.0.0.1#53(0.0.0.0) >>> ;; WHEN: Mon Feb 12 16:21:42 2007 >>> ;; MSG SIZE rcvd: 142 I used to run several name servers at a large organization and when these sorts of problems arose my first diagnostic tool was dig with the '+trace' command line option. This will expand the dig output and show what name servers were called in order in the attempt to resolve the host name. For example: >>> % dig e.staples-deals.com +trace >>> >>> ; <<>> DiG 9.2.4 <<>> e.staples-deals.com +trace >>> ;; global options: printcmd >>> . 450456 IN NS A.ROOT-SERVERS.NET. >>> . 450456 IN NS B.ROOT-SERVERS.NET. >>> . 450456 IN NS C.ROOT-SERVERS.NET. >>> . 450456 IN NS D.ROOT-SERVERS.NET. >>> . 450456 IN NS E.ROOT-SERVERS.NET. >>> . 450456 IN NS F.ROOT-SERVERS.NET. >>> . 450456 IN NS G.ROOT-SERVERS.NET. >>> . 450456 IN NS H.ROOT-SERVERS.NET. >>> . 450456 IN NS I.ROOT-SERVERS.NET. >>> . 450456 IN NS J.ROOT-SERVERS.NET. >>> . 450456 IN NS K.ROOT-SERVERS.NET. >>> . 450456 IN NS L.ROOT-SERVERS.NET. >>> . 450456 IN NS M.ROOT-SERVERS.NET. >>> ;; Received 292 bytes from 127.0.0.1#53(0.0.0.0) in 59 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 509 bytes from 198.41.0.4#53(A.ROOT-SERVERS.NET) in 128 ms >>> >>> staples-deals.com. 172800 IN NS >>> dbru.br.ns.els-gms.att.net. >>> staples-deals.com. 172800 IN NS >>> dmtu.mt.ns.els-gms.att.net. >>> ;; Received 131 bytes from 192.5.6.30#53(A.GTLD-SERVERS.NET) in 103 ms >>> >>> e.staples-deals.com. 86400 IN NS >>> ns11.customer.level3.net. >>> e.staples-deals.com. 86400 IN NS >>> ns10.customer.level3.net. >>> ;; Received 94 bytes from 199.191.128.106#53(dbru.br.ns.els-gms.att.net) >>> in 64 ms >>> >>> e.staples-deals.com. 3600 IN A 63.210.43.103 >>> e.staples-deals.com. 3600 IN NS >>> ns11.customer.level3.net. >>> e.staples-deals.com. 3600 IN NS >>> ns10.customer.level3.net. >>> ;; Received 142 bytes from 209.244.4.180#53(ns11.customer.level3.net) in >>> 88 ms You should see the 'SERVFAIL'ing name server Good luck! dlg
