this is just very very odd.
I've had my linux box setup the same way for a year and a half. Used it every couple days. Today it can't resolve hostnames, everything times out. I can ping ip's fine. Here's more wierdness, my resolve.conf says:
domain local.me
nameserver 127.0.0.1
nameserver 151.202.0.84
nameserver 151.203.0.84
But, if I run dig on either one of those servers, I get a name back no problem:
$ dig hello.com @151.202.0.84
; <<>> DiG 9.2.3 <<>> hello.com @151.202.0.84
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30658
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 0
;; QUESTION SECTION:
;hello.com. IN A
;; ANSWER SECTION:
hello.com. 179 IN A 63.236.5.136
;; AUTHORITY SECTION:
hello.com. 2473 IN NS ns4.google.com.
hello.com. 2473 IN NS ns1.google.com.
hello.com. 2473 IN NS ns2.google.com.
hello.com. 2473 IN NS ns3.google.com.
;; Query time: 518 msec
;; SERVER: 151.202.0.84#53(151.202.0.84)
;; WHEN: Sun Apr 3 20:02:06 2005
;; MSG SIZE rcvd: 122
But if I try to do anything that needs to do dns lookups, it times out. For example:
$ lynx hello.com
Looking up hello.com first
Looking up
www.hello.com.com, guessing...
Looking up
www.hello.com.edu, guessing...
Looking up
www.hello.com.net, guessing...
Looking up
www.hello.com.org, guessing...
Can't Access `file://localhost/www/hello.com'
Alert!: Unable to access document.
lynx: Can't access startfile
so, wtf??
I have a linksys router, but that's always been there the same. And I'm on my windows machine right now behind he same router with no dns problems (and I checked, it's using the same dns servers).
wacky?