kamper
Diamond Member
While I'm browsing, certain domain names will just stop working. For instance, for the last few hours, forums.anandtech.com has been inaccessible to me. It only happens for a few seemingly random domains at seemingly random times. I'm posting right now using ssh port forwarding with my server at home because my dyndns domain is currently working, although it's gone missing before as well.
I'm currently living in a university residence-style building with an ethernet jack in the room (ie. I know very little about the network) but it's generally very unreliable.
So the first diagnostic I've done is to try and ping the given domain. Here's what I get when pinging forums.anandtech.com:
90:~ jeremy$ ping forums.anandtech.com
PING forums.anandtech.com.mth (172.24.32.1): 56 data bytes
64 bytes from 172.24.32.1: icmp_seq=0 ttl=63 time=0.443 ms
... ^C
The interesting thing there is the appended '.mth' on the domain name that I can't figure out. 172.24.32.1 is on my subnet and evidently has some form of webserver running on it (from the 404's I get while browsing) and this is the IP I get no matter which particular domain I'm having trouble with.
I also fired up ethereal to see if there was anything funny going on with the dns that I could see, but the first relevant packets were the ping going to 172.24.32.1 so I assume that the domain/ip has been cached (gotta figure out how to flush that...).
My friends with windows computers on the same network don't seem to have similar problems. I have also never had such problems on other networks with this machine so I'm guessing it's a combination of os x and the residences dns server not playing nice but I don't know. Anybody know what's up?
Edit: here's the contents of my /etc/resolv.conf which seem rather relevant. I am using dhcp so this is dynamic. Maybe I should have posted this in Operating System...
domain mth
nameserver 172.24.32.1
Edit2: Further weirdness. Here's the output of the host(1) command:
90:/etc jeremy$ host forums.anandtech.com
forums.anandtech.com has address 66.117.33.59
However, pinging after this still goes to forums.anandtech.com.mth
Edit2: w00t. 'lookupd -flushcache' fixed the symptom 🙂 I'm still curious if anyone knows anything about the actual problem though so I don't have to flush the cache every time.
I'm currently living in a university residence-style building with an ethernet jack in the room (ie. I know very little about the network) but it's generally very unreliable.
So the first diagnostic I've done is to try and ping the given domain. Here's what I get when pinging forums.anandtech.com:
90:~ jeremy$ ping forums.anandtech.com
PING forums.anandtech.com.mth (172.24.32.1): 56 data bytes
64 bytes from 172.24.32.1: icmp_seq=0 ttl=63 time=0.443 ms
... ^C
The interesting thing there is the appended '.mth' on the domain name that I can't figure out. 172.24.32.1 is on my subnet and evidently has some form of webserver running on it (from the 404's I get while browsing) and this is the IP I get no matter which particular domain I'm having trouble with.
I also fired up ethereal to see if there was anything funny going on with the dns that I could see, but the first relevant packets were the ping going to 172.24.32.1 so I assume that the domain/ip has been cached (gotta figure out how to flush that...).
My friends with windows computers on the same network don't seem to have similar problems. I have also never had such problems on other networks with this machine so I'm guessing it's a combination of os x and the residences dns server not playing nice but I don't know. Anybody know what's up?
Edit: here's the contents of my /etc/resolv.conf which seem rather relevant. I am using dhcp so this is dynamic. Maybe I should have posted this in Operating System...
domain mth
nameserver 172.24.32.1
Edit2: Further weirdness. Here's the output of the host(1) command:
90:/etc jeremy$ host forums.anandtech.com
forums.anandtech.com has address 66.117.33.59
However, pinging after this still goes to forums.anandtech.com.mth
Edit2: w00t. 'lookupd -flushcache' fixed the symptom 🙂 I'm still curious if anyone knows anything about the actual problem though so I don't have to flush the cache every time.
