Re: Resolving hostnames in remote VPN network

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Bill Grant (not.available_at_online)
Date: 02/25/04 

Date: Wed, 25 Feb 2004 10:53:02 +1000

   You seem to have a strange idea about how broadcasts work. Adding a DNS
suffix will affect how DNS works, but will have no effect on LAN broadcasts
or Netbios over TCP/IP! Look at WINS. It uses Netbios names and is a "flat"
file. Only the name is significant. The only "suffixes" are the special
Netbios codes like 03 or 1c! (You are probably, in fact, getting a result
from WINS via DNS.)

    In any case, if you are using WINS, you are not relying on Netbt
broadcasts for name resolution. Netbios names will be resolved by a direct
name server query to WINS, not by trying to broadcast. Perhaps you could
enable Netmon and have a look at what actually happens.

    The problem of which connection is used for DNS was discussed recently
in the windows.server.dns newsgroup. Try posting a query in that newsgroup
on this topic.

"Aaron Seet" <poster@news.microsoft.com> wrote in message
news:uoKiGNo#DHA.2308@tk2msftngp13.phx.gbl...
> Take for example, my PC at home. Its network adapter uses ISP nameservers.
> I'd of course have to use this network adapter to VPN back to my office.
The
> resulting PPP adapter does have its internal DNS/WINS servers settings.
>
> However trying to ping an office host like server.internal.office.com will
> have the ISP DNS servers try to resolve that, never using the DNS servers
at
> the VPN end. A trick I discovered to get NBT broadcasts to get through is
to
> explicitly append the "local" DNS suffix in the advanced DNS TCP/IP
> properties. But that's NetBIOS and not DNS.
>
> So how does one controller _which_ DNS server to query when there're
> multiple adapters (multihomed)?
>
>
>
> "Bill Grant" <not.available@online> wrote in message
> news:%23VJbo4m%23DHA.2072@TK2MSFTNGP11.phx.gbl...
>
> That isn't strictly true. Your client will resolve names using the DNS
> server across the link if the client is correctly configured. For this,
the
> client's connection properties need to have the correct DNS domain
> suffix(es) as well as the DNS server IP.
>
> LAN broadcasts do not usually cross WAN links or routers.
>
>

Relevant Pages

  • Re: NetBIOS Question...
    ... On the client that you tested with did you verify that DNS name resolution ... What DNS servers is the client pointing to (should ... We turned off all NetBIOS traffic between router interfaces. ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS Problem
    ... I speak from experience on this as an AD engineer. ... to fall back on broadcasts in a domain environment by default. ... DNS vs broadcasts are one such case where faking it causes a ... false sense of "it works" in which ...
    (microsoft.public.windows.server.dns)
  • NetBIOS Node Type
    ... We have a large number of Windows XP PCs in an Active Directory ... PCs and servers used to be on a single subnet. ... but fail over to broadcasts if necessary. ... PCs are registering in both WINS and DNS ...
    (microsoft.public.windows.server.networking)
  • Re: Resolving hostnames in remote VPN network
    ... Do you mean that you make each DNS ... server a secondary for the primary zoneat the other site? ... > the office and not known to the public Internet. ... > You seem to have a strange idea about how broadcasts work. ...
    (microsoft.public.win2000.ras_routing)
  • Re: SID/DACL refresh
    ... It has the proper dns but I have figured out that if I turn off netbios it ... fixes the problem?? ... I do not understand how that clarifies the DNS in use. ... Does the new member have ONLY the DNS servers that ...
    (microsoft.public.windows.server.security)