DNS Questions
My internal network is connected to a router/firewall all address are down with Nat. So no machines on my network have an outside ip. Our dns is supplied by our ISP and we have 2 others we use that are supplied by our web site hosting company these dns servers are not apart of our internal network. If I wanted to setup a dns server on the internal network what would be the benefit? Why would I want to do this? I have been reading a lot of books on Linux and all of them recommend running a dns server. How would this server get/maintain a list of all the dns records that our current dns servers have. Is this what they even mean or do they mean just to cover the internal machines. If that's the case why bother. Any insights are greatly appreciated.
Paul Kraus
Network Administrator
PEL Supply Company
216.267.5775 Voice
216-267-6176 Fax
www.pelsupply.com
BEGIN:VCARD
VERSION:2.1
N:Kraus;Paul
FN:Paul Kraus ([email protected])
ORG:PEL Supply Company
TITLE:Network Administrator
TEL;WORK;VOICE:(216) 267-5775
TEL;CELL;VOICE:(216) 410-5526
TEL;WORK;FAX:(216) 267-6176
ADR;WORK:;;4666 Manufacturing Road;Cleveland;Ohio;44135;United States of America LABEL;WORK;ENCODING=QUOTED-PRINTABLE:4666 Manufacturing Road=0D=0ACleveland, Ohio 44135=0D=0AUnited States of Ame= rica
ADR;HOME:;;;;;;United States
LABEL;HOME:United States
URL;WORK:http://www.pelsupply.com
EMAIL;PREF;INTERNET:[email protected]
REV:20020416T182124Z
END:VCARD
Quoted 6 lines · Paul Kraus
My internal network is connected to a router/firewall all address are down with Nat. So no machines on my network have an outside ip. Our dns is supplied by our ISP and we have 2 others we use that are supplied by our web site hosting company these dns servers are not apart of our internal network. If I wanted to setup a dns server on the internal network what would be the benefit? Why would I want to do this?
1. The same DNS server can resolve local (on-LAN) FQNs and Internet FQNs.
2. Because the DNS server will cache results, frequently accessed FQNs will resolve both faster and without using part of your external bandwidth.
3. On-LAN communication is faster than off-LAN communication, so resolution will be faster.
(I'm assuming in this reply that you do not need a DNS server that is authoritative, off LAN, for your domain. You can do that too, but it involves a bit more work.)
Quoted 4 lines
I have
been reading a lot of books on Linux and all of them recommend running a dns server. How would this server get/maintain a list of all the dns records that our current dns servers have.
Depends on how you set it up. Any user-level DNS server needs to know where to go to get info on names. There are three asnwers to this question:
1. It is itself authoritative for the name. In your case, this would apply only to on-LAN resolution.
2. If it does not already know the answer, it queries another DNS server designated as a "forwarder". This could be your ISP's DNS server or the Web-hoster's DNS servers.
3. If it does not already know the answer, it queries the root DNS servers (the ones that are authoritative for TLDs -- .com, .org, the country TLDs, and so on). They refer it to DNS servers authoritative for the next name level up, and so on, until the server gets an answer for the actual FQN.
The standard for supplying a DNS record includes an expiration field in the record. The normal behavior for DNS servers is to cache records until either they reach their expiration time or the system runs out of cache space. That's how they "maintain" the lists.
Quoted 3 lines
Is this what they even mean
or do they mean just to cover the internal machines. If that's the case why bother. Any insights are greatly appreciated.
Setting up a DNS server to cover *just* the LAN is possible, but it introduces some problems for resolving off-LAN names. A combined (on- and off-LAN) DNS server lets you skip having each on-LAN host contain an/etc/hosts (or equivalent) file. (I believe an all-Windows LAN can avoid this necessity because its SMB server acts as a sort of DNS server for the LAN, but I really don't know the details of this.)
--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [email protected]
-------------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Ok so from how I understand it. A request is made to the local DNS server. That server checks its DNS records if it does not know the address it passes the request to stated DNS servers if that server does not know then it sends it to the root server.
So does it go request-localdns-ispdns-rootdns then reversed on the way back or does it go
Request-localdns-ispdns FAILED
-localdns-rootdns
I guess it doesn't matter but I am curious.
Then if that address is good then the result is cached. Now lets say that a cached result is no longer good because the DNS entry has changed for that machine. Will the DNS server report it as down or will it go out again and see if it has been updated?
Paul
-----Original Message-----
From: Ray Olszewski [mailto:[email protected]]
Sent: Thursday, September 26, 2002 11:12 AM
To: Paul Kraus; [email protected]
Subject: Re: DNS Questions
Quoted 8 lines · Paul Kraus
My internal network is connected to a router/firewall all address are down with Nat. So no machines on my network have an outside ip. Our dns
is supplied by our ISP and we have 2 others we use that are supplied by
our web site hosting company these dns servers are not apart of our internal network. If I wanted to setup a dns server on the internal network what would be the benefit? Why would I want to do this?
1. The same DNS server can resolve local (on-LAN) FQNs and Internet FQNs.
2. Because the DNS server will cache results, frequently accessed FQNs will
resolve both faster and without using part of your external bandwidth.
3. On-LAN communication is faster than off-LAN communication, so resolution
will be faster.
(I'm assuming in this reply that you do not need a DNS server that is authoritative, off LAN, for your domain. You can do that too, but it involves a bit more work.)
Quoted 4 lines
I have
been reading a lot of books on Linux and all of them recommend running a dns server. How would this server get/maintain a list of all the dns records that our current dns servers have.
Depends on how you set it up. Any user-level DNS server needs to know where
to go to get info on names. There are three asnwers to this question:
1. It is itself authoritative for the name. In your case, this would apply
only to on-LAN resolution.
2. If it does not already know the answer, it queries another DNS server
designated as a "forwarder". This could be your ISP's DNS server or the Web-hoster's DNS servers.
3. If it does not already know the answer, it queries the root DNS servers
(the ones that are authoritative for TLDs -- .com, .org, the country TLDs,
and so on). They refer it to DNS servers authoritative for the next name
level up, and so on, until the server gets an answer for the actual FQN.
The standard for supplying a DNS record includes an expiration field in the
record. The normal behavior for DNS servers is to cache records until either they reach their expiration time or the system runs out of cache space. That's how they "maintain" the lists.
Quoted 4 lines
Is this what they even mean
or do they mean just to cover the internal machines. If that's the casewhy bother. Any insights are greatly appreciated.
Setting up a DNS server to cover *just* the LAN is possible, but it introduces some problems for resolving off-LAN names. A combined (on- and
off-LAN) DNS server lets you skip having each on-LAN host contain an/etc/hosts (or equivalent) file. (I believe an all-Windows LAN can avoid
this necessity because its SMB server acts as a sort of DNS server for the
LAN, but I really don't know the details of this.)
-- -------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [email protected]
------------------------------------------------------------------------
-------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Quoted 11 lines · Paul Kraus
Ok so from how I understand it. A request is made to the local DNS server. That server checks its DNS records if it does not know the address it passes the request to stated DNS servers if that server does not know then it sends it to the root server.
So does it go request-localdns-ispdns-rootdns then reversed on the way back or does it go
Request-localdns-ispdns FAILED
-localdns-rootdnsI guess it doesn't matter but I am curious.
It depends on the particular DNS server you are running and how you have it configured. Typically, though, if you have a forwarder set up (what you call ispdns in your restating), the local DNS server will only go to the forwarder. The forwarder will then do the work of tracking down the answer via the root servers.
Quoted 4 lines
Then if that address is good then the result is cached. Now lets say that a cached result is no longer good because the DNS entry has changed for that machine. Will the DNS server report it as down or will it go out again and see if it has been updated?
Neither. The DNS server will just report the incorrect information in the cache; there is no mechanism in DNS for telling a caching DNS server "you're wrong, please try again". This is why it is important that the authoritative DNS server supply sensible expiration times with its replies ... so that obsolete information is not sitting arouund the Internet in DNS caches. (You will sometimes see this problem discussed in the context of how long it takes for a DNS change to "propagate".)
--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [email protected]
-------------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs