jerry writes:
> What you probably need to do is to track down using dig or
> nslookup which name server is messing up.  Check your
> resolv.conf file, and check those specifically as servers.
> Note that below I checked the authority section, then the
> primary name server (north.affordablehost.com).

thanks, jerry.  i didn't know about dig, a very useful utility.
i actually found the culprit first, just by cleaning out my
resolv.conf file - for some reason, i had the netgear router
in the list of nameservers (192.168.0.1) and removing it
(or moving it under the others) solved the problem.

   dig @192.168.0.1 telseto.affordablehost.com

returned the reverse order of numbers:

   ;; ANSWER SECTION:
   telesto.affordablehost.com. 86400 IN    A       96.192.46.216

   dig @192.168.0.1 luna.affordablehost.com

returned the correct order:

   ;; ANSWER SECTION:
   luna.affordablehost.com. 600    IN      A       216.46.192.79

is there a rational explanation for this?

dan

j. daniel moylan
84 harvard ave #2
brookline, ma 02446-6202
617-232-2360 (tel)
810-454-1823 (fax)
jdm@moylan.info
www.moylan.info