Leopard Name Resolution Issues

Daniel M. Zimmerman dmz-lists at tffenterprises.com
Tue Nov 27 19:52:45 PST 2007


Not strictly an "admin" question, except insofar as it has to do with 
system settings, but I figure somebody on here might know about this. I was 
messing with the "use dynamic global hostname" (hereafter, UDGH) settings 
on a Leopard machine of mine, and although I turned UDGH off after I was 
done messing with it, I seem to have somehow borked name resolution on my 
machine. It seems that CNAME records in the tffenterprises.com domain, 
which is where I was messing with UDGH, no longer resolve properly. Here is 
some example output from "dig" and "ping" (on the same machine, with no 
change in DNS server settings in between):

dmz at whitestar ~ =) dig babylon4.tffenterprises.com

; <<>> DiG 9.4.1-P1 <<>> babylon4.tffenterprises.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42517
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;babylon4.tffenterprises.com.	IN	A

;; ANSWER SECTION:
babylon4.tffenterprises.com. 3538 IN	CNAME	babylon4-tff.dyndns.org.
babylon4-tff.dyndns.org. 60	IN	A	128.208.244.210

;; Query time: 93 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Tue Nov 27 19:47:06 2007
;; MSG SIZE  rcvd: 98

dmz at whitestar ~ =) ping babylon4.tffenterprises.com
ping: cannot resolve babylon4.tffenterprises.com: Unknown host

I find this very odd, because it seems to me that my nameserver (which 
happens to be the built-in caching nameserver of an AirPort Express, in 
this case) is working fine - and on all the other machines connected to it, 
the above ping works properly. I've run "dscacheutil -flushcache" to see if 
maybe I had a bad directory services cache entry, but that didn't help... 
and neither did a reboot.

Anybody have any idea what might cause this, or how I could start tracking 
it down? I've tried resetting my TCP/IP settings from scratch, even to the 
point of deleting my AirPort device and recreating it in the Network 
preferences, and nothing seems to get rid of the problem.

-Dan

------------------------------------------------------------------
Daniel M. Zimmerman                                TFF Enterprises
1900 Commerce St. Box 358426   http://www.tffenterprises.com/~dmz/
Tacoma, WA  98402  USA                      dmz at tffenterprises.com


More information about the MacOSX-admin mailing list