Wed, 09 Sep 2009

Way to respect TTL, VMware.

Here's something fun. Here's a DNS query that looks right: 

wxs@ack wxs % dig @4.2.2.1 +nocmd +nocomments +noquestion +nostats syn.atarininja.org
syn.atarininja.org.     1771    IN      A       129.21.60.158
wxs@ack wxs %

Here's the same query but from a NAT'ed VM (VMware Workstation) using the NAT device as a DNS server: 

wxs@rst wxs % dig @192.168.2.2 +nocmd +nocomments +noquestion +nostats syn.atarininja.org
syn.atarininja.org. 5       IN      A       129.21.60.158
wxs@rst wxs %

The TTL is always 5. It's not like it starts at 5 and counts down. It's always 5. The NAT device acts as a DNS proxy, forwarding requests to whatever DNS server the host machine uses. I checked these requests and the response coming back has the real TTL. Why does VMware feel the need to manipulate TTL values on DNS responses?

posted at: 12:33 | tags: | path: /entries/geek | permanent link to this entry