Re: Dyndns.org configuration

From: Ivan Marsh (annoyed_at_you.now)
Date: 08/24/05 

Date: Wed, 24 Aug 2005 12:38:24 -0500

On Thu, 25 Aug 2005 02:32:48 +1000, Netocrat wrote:
> On Tue, 23 Aug 2005 16:39:24 -0500, Ivan Marsh <annoyed@you.now> wrote:
>> On Wed, 24 Aug 2005 04:41:57 +1000, Netocrat wrote:
>>> Ivan Marsh <annoyed@you.now> wrote:
>>>> On Tue, 23 Aug 2005 01:23:48 +0100, Steve Welsh wrote:
>>>>> Ivan Marsh wrote:
>>>>>> On Mon, 22 Aug 2005 23:29:44 +0200, Jollyluke wrote: If you're only
>>>>>> talking about a few machines it would probably be easier to put
>>>>>> your local machines in your host files rather than setting up a DNS
>>>>>> server.
>>>>>
>>>>> Bind is one of the easiest things I ever set up on my Linux server -
>>>>> just follow the HOWTO :)
>>>>
>>>> True... it is quite easy to set up... but host files are easier.
>>>>
>>>>> Also, considerable improvements in resolution times.
>>>>
>>>> It's impossible for a DNS server to resolve faster than host files.
>>>> Your machine always checks the host files before it does a DNS
>>>> lookup.
>>>
>>> You're assuming that the host exists in the host file.
>>
>> That goes without saying, hence the "put your hosts in the host file"
>> part of the previous message.
>
> It seemed to me that Steve was referring to resolution in general (which
> he has confirmed in a separate post).

Not to beat a dead horse but I'm not sure what that means... resolution,
in general, includes the host file.

If we're speaking of, as Steve mentioned, the resolution performance
between a local DNS and a remote DNS it's a moot point... the hosts on
your local LAN will, unless registered with the internet DNS system, not
resolve at all from a remote DNS.

If they are registered with the internet DNS system then the "proper" way
to resolve those addresses locally is to run a secondary caching DNS
server locally and not put them in the host file or a primary zone in the
local DNS.

If this is the case then the OP does, in fact, need to use the hostnames
and full domain registered with dyndns on his local machines in order to
have proper resolution using a local DNS server.

> In the specific case under discussion, unless as someone else has
> pointed out the resolution order has been changed so that DNS is
> consulted before hosts file, of course you are right that the hosts file
> will always be faster.

I don't know of any distro of *nix... or any other OS for that matter
that, by default, resolves DNS before the host file. But, as always,
things that are different aren't the same. 

-- 
"Blessed is he who expects nothing, for he shall never be disappointed."
   Benjamin Franklin (I didn't know he was a Buddhist)

Relevant Pages

  • Re: Cannot see computer on network
    ... One thing that strikes me is that the DNS listed in the ipconfig/all is the ... If your router is addressed as a DNS server, it's providing a DNS relay - ... And it won't provide local name resolution. ... DNS is used for local name resolution only if you have an actual local DNS ...
    (microsoft.public.windowsxp.network_web)
  • Re: Novice: TRANSFERS folder disappeared
    ... >The LMHost file is really not needed. ... I prefer to use the Host file ... >instead if I really need DNS Name resolution. ...
    (microsoft.public.windowsxp.network_web)
  • Re: How is DNS resolution working?
    ... > network is really our private corporate network (which in turn is ... > DNS: 192.168.1.10 ... > resolution is being properly handled by the DNS server on Machine B ... > resolves) on the external network ...
    (microsoft.public.win2000.dns)
  • Re: How is DNS resolution working?
    ... > network is really our private corporate network (which in turn is ... > DNS: 192.168.1.10 ... > resolution is being properly handled by the DNS server on Machine B ... > resolves) on the external network ...
    (microsoft.public.win2000.networking)
  • Re: DNS-NetBios name resolution order
    ... it could help with slow access to shares but that depends on whether there is another problem other that the default name resolution ... You could setup a zone on your local DNS server, add A records for the local hosts and then use this DNS server on home LAN. ... You can add forwarders to the DNS server so the clients can resolve names out on the internet. ... >> of XP will attempt to resolve this name using Netbios. ...
    (microsoft.public.windows.server.networking)