DNS not working in bridged networking on Windows host v3.1.2

[Gary]

I upgraded to version 3.1.2 and have not been able to get guest DNS resolution to work under bridged networking. I have tried this with OpenSolaris, Fedora, WinXP and Win7 guests. All are consistent. If I select NAT the guests' DNS resolution works fine. However, if I use bridged networking I get no name resolution. DHCP assigns the DNS server correctly and I can ping the name server and I can access Internet sites via ethernet addresses. The only problem seems to be the name resolution.

Here is some NAT info from a successful DNS config. Again, it is NAT.

---

ifconfig -a
eth0      Link encap:Ethernet  HWaddr 08:00:27:B2:05:49
          inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:feb2:549/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:29 errors:0 dropped:0 overruns:0 frame:0
          TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3786 (3.6 KiB)  TX bytes:5997 (5.8 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:22 errors:0 dropped:0 overruns:0 frame:0
          TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1868 (1.8 KiB)  TX bytes:1868 (1.8 KiB)

pan0      Link encap:Ethernet  HWaddr D6:25:56:27:0F:63  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

[gary@fedspike ~]$ cat /etc/resolv.conf 
# Generated by NetworkManager
nameserver 192.168.1.1

Here is a bridged session. I can ping the 192.168.1.1 or even the google.com IP address. I just cannot get ANY name resolution at all...

---

[gary@fedspike ~]$ nslookup google.com
;; connection timed out; no servers could be reached

[gary@fedspike ~]$ ifconfig -a
eth0      Link encap:Ethernet  HWaddr 08:00:27:B2:05:49  
          inet addr:192.168.1.148  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:feb2:549/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:205 errors:0 dropped:0 overruns:0 frame:0
          TX packets:140 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:13542 (13.2 KiB)  TX bytes:13592 (13.2 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1040 (1.0 KiB)  TX bytes:1040 (1.0 KiB)

pan0      Link encap:Ethernet  HWaddr 2A:FF:22:C6:BD:87  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

[gary@fedspike ~]$ cat /etc/resolv.conf 
# Generated by NetworkManager
nameserver 192.168.1.1

Is it possible that there is a problem in the VBoxNetflt driver? It seems to have been updated in 3.1.2 for Windows.