> Jason, thanks, but i dont really understand what you mean. Can you > elaborate more? That command should have either returned a proper lookup, which looks like this: ; <<>> DiG 9.3.2 <<>> google.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36313 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 4 ;; QUESTION SECTION: ;google.com. IN A ;; ANSWER SECTION: google.com. 86 IN A 72.14.207.99 google.com. 86 IN A 64.233.167.99 google.com. 86 IN A 64.233.187.99 ;; AUTHORITY SECTION: google.com. 313475 IN NS ns3.google.com. google.com. 313475 IN NS ns4.google.com. google.com. 313475 IN NS ns1.google.com. google.com. 313475 IN NS ns2.google.com. ;; ADDITIONAL SECTION: ns1.google.com. 136895 IN A 216.239.32.10 ns2.google.com. 136895 IN A 216.239.34.10 ns3.google.com. 315244 IN A 216.239.36.10 ns4.google.com. 315244 IN A 216.239.38.10 ;; Query time: 37 msec ;; SERVER: 67.50.135.146#53(67.50.135.146) ;; WHEN: Thu Jul 20 00:49:29 2006 ;; MSG SIZE rcvd: 212 Or a timeout/unreachable error, which looks like this: ; <<>> DiG 9.3.2 <<>> google.com @1.2.3.4 ; (1 server found) ;; global options: printcmd ;; connection timed out; no servers could be reached Or some sort of server failed error. Instead, it dumped all the root name servers. That means that either a) you didn't really type the command the way I specified / have some sort of weird settings in .digrc / have some sort of weird alias, or b) the name server you specified is returning bogus results. In the case of bogus results, it's the name server admin's problem, not yours (unless you are that admin... =). There is an option c) which is a stretch that involved hijacked queries or a compromised system, but like I said, that's a far reach. j -- Jason Bradley Nance What would you cry for? aitrus at tresgeek.net Swallow your pride for? Tres Geek What would you go wild for? http://tresgeek.net/ -Poe, "Wild" --