On 12/19/06, David Boyes <[EMAIL PROTECTED]> wrote:
It's handy for test purposes because you could force the Linux guest to give any answer you wanted w/o having to convince your Windows admins to break the real DNS for your purpose. It's also useful in the case where you're hosting Linux guests that provide network services to not have a
Yeah... depending on how fluent you are in DNS it will either bite you very soon or only later... The DNS protocol has been stretched and the de-facto standard extended beyond the RFCs. When you make your DNS claim authority over a domain that you don't own, real world effects may vary. Things like negative caching can make you go bold very fast. I learned a lot of those tricks when I did my own DNS server on CMS. And I learned from my network colleague that you can also contaminate the cache of the NAMESERV freebie with names that you made up yourself. Can do for several evenings happy searching. For an occasional telnet or ping command, the impact of going out to resolve the name is neglectable. The best case imho for having a DNS cache local on VM is for reverse lookup of client IP address when you run a web server on VM. The typical visit may contain several hits and going out to the LAN for each of them is a waste because probably the web server will wait for the response before serving the client. Rob -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.com/
