-----Original Message----- From: Doug O'Leary <dkole...@olearycomputers.com> Date: Monday, August 6, 2012 9:58 AM To: 'Doug Barton' <do...@dougbarton.us>, Mike Hoskins <micho...@cisco.com> Cc: "comp-protocols-dns-b...@isc.org" <comp-protocols-dns-b...@isc.org> Subject: RE: new bind 9.9 and root NS
>After the network admin verified there was no firewall rule differences, >we >powered off the old secondary server and re-IPed the new one with the old >secondary. The old secondary is able to get to the root nameservers w/o >issue. Once we re-IPed the new one, it still was unable to get to the >root >nameservers via dig. Just checking the obvious; no host-based firewall on the new box? Is it the same OS? >I also downloaded and installed lft - layer four traceroute (wonderful >program, that one is). Lft was unable to get *anywhere* using udp >regardless of what the IP address of the new system is. So, there's >something with the virtualization software, vmware, which is preventing >udp >packets. There are some web sites saying the same thing so this isn't >completely out of the blue. The client's opening a service call with >vmware >to see if there's a resolution. I'm serving several thousand clients using VMware + BIND, so I'm curious to see where this goes. :-) Which VMware product are you using, and what host platform? Thanks! _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
