Hosting DNS locally

[Daniel Tan]

Does installing a DNS in a local network would enable client's host
name resolution much faster ? Thanks

Regards,
Daniel

 

[Steven Umbach]

I have not noticed much of a difference either way as your dns server still will
either need to forward to your ISP dns servers or use root hints to do it's own
lookups. The speed increase may come though from your dns server caching results
which may be helpful if users are looking up many of the same sites. If you have
a W2K server online it would be easy enough to try. Assuming you are not using
an Active Directory domain which requires an AD domain controller running dns on
the network, just install dns on the server and you do not need to configure a
zone. Then either configure it to point to the ISP dns server as a forwarder or
leave as is and it will use root hints to resolve internet names. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;323380 --- applies
to W2K also. If you are not in an AD domain, ignore parts about domain
configuration.

 

[ravi]

Yes -- No


your server is Win2k or higher and all your clients are
win2k or higher.-- Yes Local DNS improve the name
resolution to domains and your clients should have an
entry to your local dns server first


Your server is win2k or higher and all your clients are
winNT or less. --No Local DNS will not improve to access
your local systems( for to access your local systems you
need to have WINS server) but Yes it will improve domain
resolution.

 

[Oli Restorick [MVP]]

.... your clients should have an
entry to your local dns server first

Clients should *only* have an entry to your local DNS server. The local DNS
server should use a forwarder to enable outside name resolution.

This mistake seems the most popular way to build a screwed Active Directory
network.

Oli

 

[Daniel Tan]

Steve
How to know wether the DNS is resolving name even if nothing is configured ?

Regards,
Daniel

 

[Steven L Umbach]

I would point a machine to it and try it out. You could also use nslookup on the
machine you configure to use it. Just enter nslookup at the command prompt and
assuming it finds for dns server [don't worry if it squaks about not finding the name
of the dns server but it should display it's IP address] enter a name to resolve such
as Microsoft.com and you should see if it is resolving names to IP addresses or not.
It will be configured if you enable the service, but it will not have it's own zone
to host if it is not part of an AD domain. --- Steve

 

[Daniel Tan]

Steve,
Do you mean that if no AD domain setup , i can;t set any zone to
host records ? What about cache ? if the same name resolution would
it keep in the cache ?

Daniel

I would point a machine to it and try it out. You could also use nslookup on the
machine you configure to use it. Just enter nslookup at the command prompt and
assuming it finds for dns server [don't worry if it squaks about not finding the name
of the dns server but it should display it's IP address] enter a name to resolve such
as Microsoft.com and you should see if it is resolving names to IP addresses or not.
It will be configured if you enable the service, but it will not have it's own zone
to host if it is not part of an AD domain. --- Steve

Steve
How to know wether the DNS is resolving name even if nothing is configured ?

Regards,
Daniel


"Steven Umbach" <[email protected]> wrote in message

 

[Steven L Umbach]

You can pretty much put as many zones as you want to an a W2K dns server
even if it is an AD domian controller, though in that situation it may not
be wise do to demands on a domain controller. Domain contollers can use AD
integreated zones and still host traditional primary and secondary zones and
quite often secondary zones are needed for interforest trusts.

If you have no zones defined then the dns server will basically be what is
called a caching only dns server. You can see what the dns server has
cached by enabling view/advanced in the dns server Management Console where
you will see a folder/zone with cached lookups. -- Steve

http://www.microsoft.com/windows2000/en/server/help/default.asp?url=/WINDOWS
2000/en/server/help/sag_DNS_pro_CachingOnlyServer.htm
http://tinyurl.com/yudql -- same link as above, shorter in case of wrap.

Steve,
Do you mean that if no AD domain setup , i can;t set any zone to
host records ? What about cache ? if the same name resolution would
it keep in the cache ?

Daniel

"Steven L Umbach" <[email protected]> wrote in message

I would point a machine to it and try it out. You could also use nslookup on the
machine you configure to use it. Just enter nslookup at the command prompt and
assuming it finds for dns server [don't worry if it squaks about not finding the name
of the dns server but it should display it's IP address] enter a name to resolve such
as Microsoft.com and you should see if it is resolving names to IP addresses or not.
It will be configured if you enable the service, but it will not have it's own zone
to host if it is not part of an AD domain. --- Steve

Steve
How to know wether the DNS is resolving name even if nothing is configured ?

Regards,
Daniel


"Steven Umbach" <[email protected]> wrote in message

I have not noticed much of a difference either way as your dns server still will
either need to forward to your ISP dns servers or use root hints to do it's own
lookups. The speed increase may come though from your dns server caching results
which may be helpful if users are looking up many of the same sites. If you have
a W2K server online it would be easy enough to try. Assuming you are not using
an Active Directory domain which requires an AD domain controller running dns on
the network, just install dns on the server and you do not need to configure a
zone. Then either configure it to point to the ISP dns server as a forwarder or
leave as is and it will use root hints to resolve internet names. --- Steve

ttp://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B323380 ---
applies

 

[Daniel Tan]

Steve,
Will caching server be much faster than having any zones ?

Regards
Daniel

You can pretty much put as many zones as you want to an a W2K dns server
even if it is an AD domian controller, though in that situation it may not
be wise do to demands on a domain controller. Domain contollers can use AD
integreated zones and still host traditional primary and secondary zones and
quite often secondary zones are needed for interforest trusts.

If you have no zones defined then the dns server will basically be what is
called a caching only dns server. You can see what the dns server has
cached by enabling view/advanced in the dns server Management Console where
you will see a folder/zone with cached lookups. -- Steve

http://www.microsoft.com/windows2000/en/server/help/default.asp?url=/WINDOWS
2000/en/server/help/sag_DNS_pro_CachingOnlyServer.htm
http://tinyurl.com/yudql -- same link as above, shorter in case of wrap.

Steve,
Do you mean that if no AD domain setup , i can;t set any zone to
host records ? What about cache ? if the same name resolution would
it keep in the cache ?

Daniel

"Steven L Umbach" <[email protected]> wrote in message

I would point a machine to it and try it out. You could also use nslookup on the
machine you configure to use it. Just enter nslookup at the command prompt and
assuming it finds for dns server [don't worry if it squaks about not finding the name
of the dns server but it should display it's IP address] enter a name to resolve such
as Microsoft.com and you should see if it is resolving names to IP addresses or not.
It will be configured if you enable the service, but it will not have it's own zone
to host if it is not part of an AD domain. --- Steve


Steve
How to know wether the DNS is resolving name even if nothing is configured ?

Regards,
Daniel


"Steven Umbach" <[email protected]> wrote in message

I have not noticed much of a difference either way as your dns server still will
either need to forward to your ISP dns servers or use root hints to do it's own
lookups. The speed increase may come though from your dns server caching results
which may be helpful if users are looking up many of the same sites. If you have
a W2K server online it would be easy enough to try. Assuming you are not using
an Active Directory domain which requires an AD domain controller running dns on
the network, just install dns on the server and you do not need to configure a
zone. Then either configure it to point to the ISP dns server as a forwarder or
leave as is and it will use root hints to resolve internet names. --- Steve

ttp://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B323380 ---
applies

 

[Steven L Umbach]

In theory it could be, but if it does not have a lot of zones or host records than I
doubt any difference would be noticed. It always checks the cache first [as do
clients] --- Steve

Steve,
Will caching server be much faster than having any zones ?

Regards
Daniel

"Steven L Umbach" <[email protected]> wrote in message

You can pretty much put as many zones as you want to an a W2K dns server
even if it is an AD domian controller, though in that situation it may not
be wise do to demands on a domain controller. Domain contollers can use AD
integreated zones and still host traditional primary and secondary zones and
quite often secondary zones are needed for interforest trusts.

If you have no zones defined then the dns server will basically be what is
called a caching only dns server. You can see what the dns server has
cached by enabling view/advanced in the dns server Management Console where
you will see a folder/zone with cached lookups. -- Steve

http://www.microsoft.com/windows2000/en/server/help/default.asp?url=/WINDOWS
2000/en/server/help/sag_DNS_pro_CachingOnlyServer.htm
http://tinyurl.com/yudql -- same link as above, shorter in case of wrap.

Steve,
Do you mean that if no AD domain setup , i can;t set any zone to
host records ? What about cache ? if the same name resolution would
it keep in the cache ?

Daniel

"Steven L Umbach" <[email protected]> wrote in message

I would point a machine to it and try it out. You could also use nslookup on the
machine you configure to use it. Just enter nslookup at the command prompt and
assuming it finds for dns server [don't worry if it squaks about not finding the name
of the dns server but it should display it's IP address] enter a name to resolve such
as Microsoft.com and you should see if it is resolving names to IP addresses or not.
It will be configured if you enable the service, but it will not have it's own zone
to host if it is not part of an AD domain. --- Steve


Steve
How to know wether the DNS is resolving name even if nothing is configured ?

Regards,
Daniel


"Steven Umbach" <[email protected]> wrote in message

I have not noticed much of a difference either way as your dns server still will
either need to forward to your ISP dns servers or use root hints to do it's own
lookups. The speed increase may come though from your dns server caching results
which may be helpful if users are looking up many of the same sites. If you have
a W2K server online it would be easy enough to try. Assuming you are not using
an Active Directory domain which requires an AD domain controller running dns on
the network, just install dns on the server and you do not need to configure a
zone. Then either configure it to point to the ISP dns server as a forwarder or
leave as is and it will use root hints to resolve internet names. --- Steve

ttp://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B323380 ---
applies

to W2K also. If you are not in an AD domain, ignore parts about domain
configuration.


Does installing a DNS in a local network would enable client's host
name resolution much faster ? Thanks

Regards,
Daniel

 

[Daniel Tan]

Steve,
Inside the cache folder, how come there are so many subfolder with
name such as COM, JP,UK .... Does it cached based on country ?

Regards,
Daniel

You can pretty much put as many zones as you want to an a W2K dns server
even if it is an AD domian controller, though in that situation it may not
be wise do to demands on a domain controller. Domain contollers can use AD
integreated zones and still host traditional primary and secondary zones and
quite often secondary zones are needed for interforest trusts.

If you have no zones defined then the dns server will basically be what is
called a caching only dns server. You can see what the dns server has
cached by enabling view/advanced in the dns server Management Console where
you will see a folder/zone with cached lookups. -- Steve

http://www.microsoft.com/windows2000/en/server/help/default.asp?url=/WINDOWS
2000/en/server/help/sag_DNS_pro_CachingOnlyServer.htm
http://tinyurl.com/yudql -- same link as above, shorter in case of wrap.

Steve,
Do you mean that if no AD domain setup , i can;t set any zone to
host records ? What about cache ? if the same name resolution would
it keep in the cache ?

Daniel

"Steven L Umbach" <[email protected]> wrote in message

I would point a machine to it and try it out. You could also use nslookup on the
machine you configure to use it. Just enter nslookup at the command prompt and
assuming it finds for dns server [don't worry if it squaks about not finding the name
of the dns server but it should display it's IP address] enter a name to resolve such
as Microsoft.com and you should see if it is resolving names to IP addresses or not.
It will be configured if you enable the service, but it will not have it's own zone
to host if it is not part of an AD domain. --- Steve


Steve
How to know wether the DNS is resolving name even if nothing is configured ?

Regards,
Daniel


"Steven Umbach" <[email protected]> wrote in message

I have not noticed much of a difference either way as your dns server still will
either need to forward to your ISP dns servers or use root hints to do it's own
lookups. The speed increase may come though from your dns server caching results
which may be helpful if users are looking up many of the same sites. If you have
a W2K server online it would be easy enough to try. Assuming you are not using
an Active Directory domain which requires an AD domain controller running dns on
the network, just install dns on the server and you do not need to configure a
zone. Then either configure it to point to the ISP dns server as a forwarder or
leave as is and it will use root hints to resolve internet names. --- Steve

ttp://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B323380 ---
applies

 

[Steven Umbach]

Not on country, but on second level domain name where root is top level. Second
level would be com, net, edu, org, mil, UK, etc. --- Steve

Steve,
Inside the cache folder, how come there are so many subfolder with
name such as COM, JP,UK .... Does it cached based on country ?

Regards,
Daniel


"Steven L Umbach" <[email protected]> wrote in message

You can pretty much put as many zones as you want to an a W2K dns server
even if it is an AD domian controller, though in that situation it may not
be wise do to demands on a domain controller. Domain contollers can use AD
integreated zones and still host traditional primary and secondary zones and
quite often secondary zones are needed for interforest trusts.

If you have no zones defined then the dns server will basically be what is
called a caching only dns server. You can see what the dns server has
cached by enabling view/advanced in the dns server Management Console where
you will see a folder/zone with cached lookups. -- Steve

http://www.microsoft.com/windows2000/en/server/help/default.asp?url=/WINDOWS
2000/en/server/help/sag_DNS_pro_CachingOnlyServer.htm
http://tinyurl.com/yudql -- same link as above, shorter in case of wrap.

Steve,
Do you mean that if no AD domain setup , i can;t set any zone to
host records ? What about cache ? if the same name resolution would
it keep in the cache ?

Daniel

"Steven L Umbach" <[email protected]> wrote in message

I would point a machine to it and try it out. You could also use nslookup on the
machine you configure to use it. Just enter nslookup at the command prompt and
assuming it finds for dns server [don't worry if it squaks about not finding the name
of the dns server but it should display it's IP address] enter a name to resolve such
as Microsoft.com and you should see if it is resolving names to IP addresses or not.
It will be configured if you enable the service, but it will not have it's own zone
to host if it is not part of an AD domain. --- Steve


Steve
How to know wether the DNS is resolving name even if nothing is configured ?

Regards,
Daniel


"Steven Umbach" <[email protected]> wrote in message

I have not noticed much of a difference either way as your dns server still will
either need to forward to your ISP dns servers or use root hints to do it's own
lookups. The speed increase may come though from your dns server caching results
which may be helpful if users are looking up many of the same sites. If you have
a W2K server online it would be easy enough to try. Assuming you are not using
an Active Directory domain which requires an AD domain controller running dns on
the network, just install dns on the server and you do not need to configure a
zone. Then either configure it to point to the ISP dns server as a forwarder or
leave as is and it will use root hints to resolve internet names. --- Steve

ttp://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B323380 ---
applies

to W2K also. If you are not in an AD domain, ignore parts about domain
configuration.


Does installing a DNS in a local network would enable client's host
name resolution much faster ? Thanks

Regards,
Daniel

 

[Daniel Tan]

Hi Steve
Is it different from normal definition ? I thought mydomain.my
where .my is the top level while mydomain. is second level. Correct ?

Regards,
Daniel

Not on country, but on second level domain name where root is top level. Second
level would be com, net, edu, org, mil, UK, etc. --- Steve

Steve,
Inside the cache folder, how come there are so many subfolder with
name such as COM, JP,UK .... Does it cached based on country ?

Regards,
Daniel


"Steven L Umbach" <[email protected]> wrote in message

You can pretty much put as many zones as you want to an a W2K dns server
even if it is an AD domian controller, though in that situation it may not
be wise do to demands on a domain controller. Domain contollers can use AD
integreated zones and still host traditional primary and secondary zones and
quite often secondary zones are needed for interforest trusts.

If you have no zones defined then the dns server will basically be what is
called a caching only dns server. You can see what the dns server has
cached by enabling view/advanced in the dns server Management Console where
you will see a folder/zone with cached lookups. -- Steve

http://www.microsoft.com/windows2000/en/server/help/default.asp?url=/WINDOWS
2000/en/server/help/sag_DNS_pro_CachingOnlyServer.htm
http://tinyurl.com/yudql -- same link as above, shorter in case of wrap.

Steve,
Do you mean that if no AD domain setup , i can;t set any zone to
host records ? What about cache ? if the same name resolution would
it keep in the cache ?

Daniel

"Steven L Umbach" <[email protected]> wrote in message

I would point a machine to it and try it out. You could also use nslookup on the
machine you configure to use it. Just enter nslookup at the command prompt and
assuming it finds for dns server [don't worry if it squaks about not finding the name
of the dns server but it should display it's IP address] enter a name to resolve such
as Microsoft.com and you should see if it is resolving names to IP addresses or not.
It will be configured if you enable the service, but it will not have it's own zone
to host if it is not part of an AD domain. --- Steve


Steve
How to know wether the DNS is resolving name even if nothing is configured ?

Regards,
Daniel


"Steven Umbach" <[email protected]> wrote in message

I have not noticed much of a difference either way as your dns server still will
either need to forward to your ISP dns servers or use root hints to do it's own
lookups. The speed increase may come though from your dns server caching results
which may be helpful if users are looking up many of the same sites. If you have
a W2K server online it would be easy enough to try. Assuming you are not using
an Active Directory domain which requires an AD domain controller running dns on
the network, just install dns on the server and you do not need to configure a
zone. Then either configure it to point to the ISP dns server as a forwarder or
leave as is and it will use root hints to resolve internet names. --- Steve


ttp://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B323380 ---
applies
to W2K also. If you are not in an AD domain, ignore parts about domain
configuration.


Does installing a DNS in a local network would enable client's host
name resolution much faster ? Thanks

Regards,
Daniel

 

[Steven L Umbach]

I guess I was a bit off the mark.

Root is root - (.).
Com, net, org, etc are top level domains. And you are correct the name to the left of
the period between it and the top level is the secondary level name which must be
registered. Thanks for pointing that out. --- Steve

http://www.iana.org/gtld/gtld.htm

Hi Steve
Is it different from normal definition ? I thought mydomain.my
where .my is the top level while mydomain. is second level. Correct ?

Regards,
Daniel


"Steven Umbach" <[email protected]> wrote in message

Not on country, but on second level domain name where root is top level. Second
level would be com, net, edu, org, mil, UK, etc. --- Steve

Steve,
Inside the cache folder, how come there are so many subfolder with
name such as COM, JP,UK .... Does it cached based on country ?

Regards,
Daniel


"Steven L Umbach" <[email protected]> wrote in message

You can pretty much put as many zones as you want to an a W2K dns server
even if it is an AD domian controller, though in that situation it may not
be wise do to demands on a domain controller. Domain contollers can use AD
integreated zones and still host traditional primary and secondary zones and
quite often secondary zones are needed for interforest trusts.

If you have no zones defined then the dns server will basically be what is
called a caching only dns server. You can see what the dns server has
cached by enabling view/advanced in the dns server Management Console where
you will see a folder/zone with cached lookups. -- Steve

http://www.microsoft.com/windows2000/en/server/help/default.asp?url=/WINDOWS
2000/en/server/help/sag_DNS_pro_CachingOnlyServer.htm
http://tinyurl.com/yudql -- same link as above, shorter in case of wrap.

Steve,
Do you mean that if no AD domain setup , i can;t set any zone to
host records ? What about cache ? if the same name resolution would
it keep in the cache ?

Daniel

"Steven L Umbach" <[email protected]> wrote in message

I would point a machine to it and try it out. You could also use nslookup on the
machine you configure to use it. Just enter nslookup at the command prompt and
assuming it finds for dns server [don't worry if it squaks about not finding the name
of the dns server but it should display it's IP address] enter a name to resolve such
as Microsoft.com and you should see if it is resolving names to IP addresses or not.
It will be configured if you enable the service, but it will not have it's own zone
to host if it is not part of an AD domain. --- Steve


Steve
How to know wether the DNS is resolving name even if nothing is configured ?

Regards,
Daniel


"Steven Umbach" <[email protected]> wrote in message

I have not noticed much of a difference either way as your dns server still will
either need to forward to your ISP dns servers or use root hints to do it's own
lookups. The speed increase may come though from your dns server caching results
which may be helpful if users are looking up many of the same sites. If you have
a W2K server online it would be easy enough to try. Assuming you are not using
an Active Directory domain which requires an AD domain controller running dns on
the network, just install dns on the server and you do not need to configure a
zone. Then either configure it to point to the ISP dns server as a forwarder or
leave as is and it will use root hints to resolve internet names. --- Steve


ttp://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B323380 ---
applies
to W2K also. If you are not in an AD domain, ignore parts about domain
configuration.


Does installing a DNS in a local network would enable client's host
name resolution much faster ? Thanks

Regards,
Daniel