Re: Issue 171346 in chromium: Built-in DNS uses the wrong DNS server

[chro...@googlecode.com]

Comment #4 on issue 171346 by fkhp...@gmail.com: Built-in DNS uses the
wrong DNS server
http://code.google.com/p/chromium/issues/detail?id=171346

C: \ Users \ Administrator> ipconfig / all

Windows IP Configuration

   Host name .............: TS08
   Primary DNS suffix ...........:
   Node Type ............: Hybrid
   IP routing enabled ..........: Yes
   WINS Proxy Enabled .........: No

The PPP adapter broadband connection:

   Connection-specific DNS Suffix .......:
   Description ...............: broadband connection
   Physical address .............:
   DHCP Enabled ...........: No
   Autoconfiguration Enabled ..........: Yes
   IPv4 Address ............: 123.115.245.246 (preferred)
   Subnet Mask ............: 255.255.255.255
   Default Gateway .............: 0.0.0.0
   DNS server ...........: 202.106.195.68
   NetBIOS over TCPIP on .......: Disabled

Ethernet adapter bridge:

   Connection-specific DNS Suffix .......:
   Description ...............: MAC Bridge Miniport
   Physical Address .............: 02-50-56-C0-00-08
   DHCP Enabled ...........: No
   Autoconfiguration Enabled ..........: Yes
   Link-local IPv6 Address ........: fe80 :: f447: 4761:69 b0: a89c% 16
(preferred)
   IPv4 Address ............: 192.168.0.1 (Preferred)
   Subnet Mask ............: 255.255.255.0
   IPv4 Address ............: 192.168.0.8 (Preferred)
   Subnet Mask ............: 255.255.255.0
   IPv4 Address ............: 192.168.137.1 (preferred)
   Subnet Mask ............: 255.255.255.0
   Default Gateway .............: 192.168.0.2
   DHCPv6 IAID ...........: 469901680
   The DHCPv6 client the DUID .......:
00-01-00-01-15-E5-90-2E-00-0C-29-0C-58-20
   DNS server ...........: 2001:470:20 ::
   NetBIOS over TCPIP on .......: Enabled

Ethernet adapter VMware Network Adapter VMnet1, is:

   Connection-specific DNS Suffix .......:
   Description ...............: VMware Virtual Ethernet Adapter for VMnet1
   Physical Address .........: 00-50-56-C0-00-01
   DHCP Enabled ...........: No
   Autoconfiguration Enabled ..........: Yes
   Link-local IPv6 Address ........: fe80 :: d1bf: 4417: e690: 4c89% 17
(preferred)
   IPv4 Address ............: 192.168.106.1 (preferred)
   Subnet Mask ............: 255.255.255.0
   Default Gateway .............:
   DHCPv6 IAID ...........: 335564886
   The DHCPv6 client the DUID .......:
00-01-00-01-15-E5-90-2E-00-0C-29-0C-58-20
   DNS server ...........: fec0: 0:0: ffff :: 1% 1
                                       fec0: 0:0: ffff :: 2% 1
                                       fec0: 0:0: ffff :: 3% 1
   NetBIOS over TCPIP on .......: Enabled

Tunnel adapter isatap. {6F9377E6-6D7A-46FD-BAE9-1BB3857B00FD}:

   Connection-specific DNS Suffix .......:
   Description ...............: Microsoft ISATAP Adapter
   Physical Address .........: 00-00-00-00-00-00-00-E0
   DHCP Enabled ...........: No
   Autoconfiguration Enabled ..........: Yes
   Link-local IPv6 Address ........: fe80 :: 200:5 efe: 123.115.245.246% 21
(preferred)
   Default Gateway .............:
   DNS server ...........: 202.106.195.68
   NetBIOS over TCPIP on .......: Disabled

Tunnel adapter IP6Tunnel:

   Media State ............: Media disconnected
   Connection-specific DNS Suffix .......:
   Description ...............: Microsoft Direct Point-to-point Adapater
   Physical Address .........: 00-00-00-00-00-00-00-E0
   DHCP Enabled ...........: No
   Autoconfiguration Enabled ..........: Yes

Tunnel adapter isatap. {3A44B582-AFA7-400E-B2E3-C75785688165}:

   Connection-specific DNS Suffix .......:
   Description ...............: Microsoft ISATAP Adapter # 2
   Physical Address .........: 00-00-00-00-00-00-00-E0
   DHCP Enabled ...........: No
   Autoconfiguration Enabled ..........: Yes
   Link-local IPv6 Address ........: fe80 :: 5efe: 192.168.0.1% 20
(Preferred)
   Link-local IPv6 Address ........: fe80 :: 5efe: 192.168.0.8% 20
(Preferred)
   Link-local IPv6 Address ........: fe80 :: 5efe: 192.168.137.1% 20
(Preferred)
   Default Gateway .............:
   DNS server ...........: 2001:470:20 ::
   NetBIOS over TCPIP on .......: Disabled

Tunnel adapter 6TO4 Adapter:

   Connection-specific DNS Suffix .......:
   Description ...............: Microsoft 6to4 Adapter
   Physical Address .........: 00-00-00-00-00-00-00-E0
   DHCP Enabled ...........: No
   Autoconfiguration Enabled ..........: Yes
   IPv6 Address ............: 2002:7 b73: f5f6 :: 7b73: f5f6 (preferred)
   Default Gateway .........: 2002: c058: 6301 :: 1
                                       2002: c058: 6301 :: c058: 6301
   DNS server ...........: 202.106.195.68
   NetBIOS over TCPIP on .......: Disabled

Tunnel adapter isatap. {DC141DC5-9299-4167-9D51-E096C58E2166}:

   Connection-specific DNS Suffix .......:
   Description ...............: Microsoft ISATAP Adapter # 6
   Physical Address .........: 00-00-00-00-00-00-00-E0
   DHCP Enabled ...........: No
   Autoconfiguration Enabled ..........: Yes
   Default Gateway .............:
   NetBIOS over TCPIP on .......: Disabled

C: \ Users \ Administrator> regedit

[chro...@googlecode.com]

Updates:
Owner: sz...@chromium.org
Cc: -sz...@chromium.org

Comment #7 on issue 171346 by sz...@chromium.org: Built-in DNS uses the

wrong DNS server
http://code.google.com/p/chromium/issues/detail?id=171346

In both cases, Chrome's built-in resolver does not handle the situation
where different interfaces have different DNS servers. For now, we should
detect such situations and disable the built-in resolver.

On Windows, it seems the solution for this particular case could be to
assemble a list of DNS servers from all the interfaces. Currently, Chrome's
built-in DNS uses only the first non-loopback interface.

On OSX, Chrome uses configd which is also used by the system resolver, so
I'm surprised you are seeing different behavior from Chrome and the system
resolver.


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Comment #8 on issue 171346 by n...@robinson-wall.com: Built-in DNS uses the

wrong DNS server
http://code.google.com/p/chromium/issues/detail?id=171346

I've just come across a problem running 26.0.1410.43 on OSX 10.8.2 where
some domains should resolve differently through a VPN than not. Connecting
to a split-horizon Cisco IPSec VPN which pushes an internal DNS server for
certain domains.

* The VPN endpoint instructs the client to resolve *.example.com through a
DNS server accessible via the VPN.
* foo.example.com is resolvable publicly, as well as on the VPN. It is only
accessible externally from certain subnets, and resolves to an internal IP
address for VPN access.
* `ping foo.example.com` behaves as expected while on and off the VPN.
* Chrome tries to connect to the same external IP address both on and off
the VPN, even after clearing caches.
* bar.example.com is only resolvable via the VPN, NXDOMAIN externally.
* Chrome is able to resolve and connect to bar.example.com while connected
to the VPN.

[chro...@googlecode.com]

Comment #9 on issue 171346 by je...@jessejoe.com: Built-in DNS uses the

wrong DNS server
http://code.google.com/p/chromium/issues/detail?id=171346

+1 for chrome://flags disable internal DNS

I use /etc/resolver/domain.tld to specify DNS servers for specific domains
for my VPN. This was broken on Mac lately until I disabled the internal DNS.

[chro...@googlecode.com]

Comment #10 on issue 171346 by sz...@chromium.org: Built-in DNS uses the

wrong DNS server
http://code.google.com/p/chromium/issues/detail?id=171346

Re #9. This issue describes a problem on Windows. The problem you are
describing is tracked by Issue 265970.

[chro...@googlecode.com]

Comment #11 on issue 171346 by eclip...@gmail.com: Built-in DNS uses the
wrong DNS server
https://code.google.com/p/chromium/issues/detail?id=171346

I'm having similar issues with Chrome on Mac OS. Whenever I dial into the
VPN I have to flush the DNS cache. Otherwise it won't find any hosts on the
VPN. Sometime even flushing won't help and I need to restart Chrome.