| Author |
Message |
BrianG
Guest
|
 Posted:
Fri Nov 11, 2005 1:50 am Post subject:
Help me understand DNS as forwarder |
|
|
I'm making the transition from a single Netware 4.11 server to a single
Server 2003 server. In the past I used solely IPX for communications
with Netware with TCP/IP configured on the desktops to access our ISDN
router. As I get more into configuring TCP/IP with Server 2003 I see
that the one server needs to be a DNS server which becomes the
preferred DNS server for the workstations. I also understand that I
then need to create a forwarder to the router for all other domains
which gets users out on the internet. Is this right? It seems to me
that it will create an awful lot of traffic over the server NIC.
Please help me understand how this all works.
Thanks.
BrianG |
|
| Back to top |
|
 |
Jon Rowlan
Guest
|
| Posted:
Fri Nov 11, 2005 1:50 am Post subject:
Re: Help me understand DNS as forwarder |
|
|
You configure a local DNS server purely to administer your LOCAL dns names
and addresses (your Local server, workstations and any names that you wish
to assign to routers etc for local addresses ranges i.e. 192.168.?.?
10.0.?.? etc etc)
This is so that your local LAN can resolve names internally.
If you want/need to connect to the outside world you create a pointer or two
that is a "Forwarder"
When the local server is asked to resolve a name to an IP address, it
queries the local tables to try and resolve the name first. If the lookup
fails for the local "names" the DNS server forwards the request to the
"Forwarders" to resolve.
The "Forwarders" have a far greater knowledge and are able to resolve the
names via a network of DNS servers all holdings names and IP address on the
Internet.
In essence, your local DNS server answers the requests for IP addresses that
are local and the forwarders answer requests for non-local IP addresses.
The is all channelled through your own DNS server.
The only traffic across your server NIC is that which would occur anyway ...
www.microsoft.com - request sent to forwarder IP and result passed back to
client
mylocalmailserver.mydomain.local - result passed back from local DNS server
The two requests have to be resolved by the local DNS server either by
direct local or referral but either way the name has to be resolved.
You local server does NOT store all the resolved addresses (some maybe
cached) but on the whole the whole thing is quite efficient really.
Normally the forwarder IP addresses are provided by your ISP, you should not
suffer unduly from this service, remember in Novell terms, generally you can
only ever see the local servers and workstations etc (or at least the WAN
linked server maybe) but with TCP/IP the whole world is available to you.
In the past, you have been propagating the same amount of traffic but
directing it ALL at the ISP DNS servers via your router.
I have never known DNS traffic to be a burden on a system ...
Windows 2003 Domain controllers are closely integrated with DNS - you must
have at least one DNS server so you have little choice if you want to use
Windows 2003 I'm afraid.
I hope that heps.
jON
"BrianG" <decc@dec-clt.com> wrote in message
news:1131659969.145434.241560@z14g2000cwz.googlegroups.com...
| Quote: | I'm making the transition from a single Netware 4.11 server to a single
Server 2003 server. In the past I used solely IPX for communications
with Netware with TCP/IP configured on the desktops to access our ISDN
router. As I get more into configuring TCP/IP with Server 2003 I see
that the one server needs to be a DNS server which becomes the
preferred DNS server for the workstations. I also understand that I
then need to create a forwarder to the router for all other domains
which gets users out on the internet. Is this right? It seems to me
that it will create an awful lot of traffic over the server NIC.
Please help me understand how this all works.
Thanks.
BrianG
|
|
|
| Back to top |
|
|
Lanwench [MVP - Exchange]
Guest
|
| Posted:
Fri Nov 11, 2005 1:50 am Post subject:
Re: Help me understand DNS as forwarder |
|
|
In news:1131659969.145434.241560@z14g2000cwz.googlegroups.com,
BrianG <decc@dec-clt.com> typed:
| Quote: | I'm making the transition from a single Netware 4.11 server to a
single Server 2003 server. In the past I used solely IPX for
communications with Netware with TCP/IP configured on the desktops to
access our ISDN router. As I get more into configuring TCP/IP with
Server 2003 I see that the one server needs to be a DNS server which
becomes the preferred DNS server for the workstations. I also
understand that I then need to create a forwarder to the router for
all other domains which gets users out on the internet. Is this
right? It seems to me that it will create an awful lot of traffic
over the server NIC. Please help me understand how this all works.
Thanks.
BrianG
|
You don't create a forwarder to the router, generally - you specify
external/public DNS server IPs as forwarders and/or use root hints...
All clients point *only* at the internal DNS server's IP (not
preferred/primary -the only one).
It doesn't really hog a lot of resources, in my experience. |
|
| Back to top |
|
|
BrianG
Guest
|
| Posted:
Fri Nov 11, 2005 9:50 pm Post subject:
Re: Help me understand DNS as forwarder |
|
|
Hmmm, a little clarification please...
"All clients point *only* at the internal DNS server's IP", I'm crystal
to that point but it gets muddy from there.
My thinking was that my local DNS server forwarded all queries for
external addresses to the forwarder which is why I thought traffic
would be an issue. Do I now understand correctly that the DNS server
merely responds to queries for an external address by providing the
forwarder address?
It would then make sense that I list my ISP's DNS addresses as the
forwarders, yes? |
|
| Back to top |
|
|
Arek Iskra [MVP]
Guest
|
| Posted:
Sat Nov 12, 2005 9:50 am Post subject:
Re: Help me understand DNS as forwarder |
|
|
"BrianG" <decc@dec-clt.com> wrote in message
news:1131737461.535493.109890@g49g2000cwa.googlegroups.com...
| Quote: | Hmmm, a little clarification please...
"All clients point *only* at the internal DNS server's IP", I'm crystal
to that point but it gets muddy from there.
My thinking was that my local DNS server forwarded all queries for
external addresses to the forwarder which is why I thought traffic
would be an issue. Do I now understand correctly that the DNS server
merely responds to queries for an external address by providing the
forwarder address?
|
In short, yes. Local DNS server will provide resolution for local queries.
For external, it will merely say "oops... I don't have that information, but
you might want to check with <forwarder>. It should be in better position to
advise you".
| Quote: |
It would then make sense that I list my ISP's DNS addresses as the
forwarders, yes?
Yes. Make sure you check with your ISP as well. In fact, it is not a bad |
idea to check with them first, they might be even able to guide you on how
to set it up.
--
Arek Iskra
MVP for Windows Server - Software Distribution |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in