Running DNS locally for home network
I have a small home network that just got larger (new roommate, my existing roommate got a laptop (on top of her computer), my friends coming over with laptops, etc.).
I'd like to run a local DNS server for lookups of my local network stuff (fileserver.local
, windowsTV.local
, machineA.local
, machineB.local
, appletv.local
). I used to have a business line with a static IP, and run bind/named internally. However, now I have a normal account.
My ISP's DNS servers are constantly changing (for whatever reasons my ISP doesn't like to keep the same IP range for long). I need my local DNS to be automatically updated to use my ISP's DNS for external traffic, but be able to maintain an internal DNS server (getting to update the hosts file is being a hassle with every new machine on top of rebuilding existing machines with win7 or Ubuntu 9.04).
Additionally, My ISP's DNS servers often crash or become unresponsive. Are there any open DNS servers that are reliable (I don't want to reconfig every day) that I could use as my primary, then if those fail, then use my ISP's?
UPDATE: Also looking for each workstation to be able to use dhcp to connect, but instead of getting ISP DNS servers, getting my internal one....
dns home-networking
add a comment |
I have a small home network that just got larger (new roommate, my existing roommate got a laptop (on top of her computer), my friends coming over with laptops, etc.).
I'd like to run a local DNS server for lookups of my local network stuff (fileserver.local
, windowsTV.local
, machineA.local
, machineB.local
, appletv.local
). I used to have a business line with a static IP, and run bind/named internally. However, now I have a normal account.
My ISP's DNS servers are constantly changing (for whatever reasons my ISP doesn't like to keep the same IP range for long). I need my local DNS to be automatically updated to use my ISP's DNS for external traffic, but be able to maintain an internal DNS server (getting to update the hosts file is being a hassle with every new machine on top of rebuilding existing machines with win7 or Ubuntu 9.04).
Additionally, My ISP's DNS servers often crash or become unresponsive. Are there any open DNS servers that are reliable (I don't want to reconfig every day) that I could use as my primary, then if those fail, then use my ISP's?
UPDATE: Also looking for each workstation to be able to use dhcp to connect, but instead of getting ISP DNS servers, getting my internal one....
dns home-networking
2
There are at least 2 questions here: Local DNS config, public DNS servers. Post 2 questions next time.
– hyperslug
Sep 23 '09 at 19:09
16
I agree, but i'm looking for an overall solution. each question on it's own would have a correct answer, but may not mesh, i'm trying to look for solution to both problems that works together.
– Roy Rico
Sep 23 '09 at 20:51
@RoyRico Did you ever find a good solution? I am trying to do the exat same thing witha Tomato router and am running into walls at every direction.
– Jeff
Dec 15 '12 at 3:04
If you have a linux box, here is how to setup DNSMASq in details -- sfxpt.wordpress.com/2011/02/06/…
– xpt
Jun 15 '14 at 23:29
The new Google DNS servers are 8.8.8.8 and 8.8.4.4 in case anyone was wondering...
– Tmanok
Feb 13 at 21:03
add a comment |
I have a small home network that just got larger (new roommate, my existing roommate got a laptop (on top of her computer), my friends coming over with laptops, etc.).
I'd like to run a local DNS server for lookups of my local network stuff (fileserver.local
, windowsTV.local
, machineA.local
, machineB.local
, appletv.local
). I used to have a business line with a static IP, and run bind/named internally. However, now I have a normal account.
My ISP's DNS servers are constantly changing (for whatever reasons my ISP doesn't like to keep the same IP range for long). I need my local DNS to be automatically updated to use my ISP's DNS for external traffic, but be able to maintain an internal DNS server (getting to update the hosts file is being a hassle with every new machine on top of rebuilding existing machines with win7 or Ubuntu 9.04).
Additionally, My ISP's DNS servers often crash or become unresponsive. Are there any open DNS servers that are reliable (I don't want to reconfig every day) that I could use as my primary, then if those fail, then use my ISP's?
UPDATE: Also looking for each workstation to be able to use dhcp to connect, but instead of getting ISP DNS servers, getting my internal one....
dns home-networking
I have a small home network that just got larger (new roommate, my existing roommate got a laptop (on top of her computer), my friends coming over with laptops, etc.).
I'd like to run a local DNS server for lookups of my local network stuff (fileserver.local
, windowsTV.local
, machineA.local
, machineB.local
, appletv.local
). I used to have a business line with a static IP, and run bind/named internally. However, now I have a normal account.
My ISP's DNS servers are constantly changing (for whatever reasons my ISP doesn't like to keep the same IP range for long). I need my local DNS to be automatically updated to use my ISP's DNS for external traffic, but be able to maintain an internal DNS server (getting to update the hosts file is being a hassle with every new machine on top of rebuilding existing machines with win7 or Ubuntu 9.04).
Additionally, My ISP's DNS servers often crash or become unresponsive. Are there any open DNS servers that are reliable (I don't want to reconfig every day) that I could use as my primary, then if those fail, then use my ISP's?
UPDATE: Also looking for each workstation to be able to use dhcp to connect, but instead of getting ISP DNS servers, getting my internal one....
dns home-networking
dns home-networking
edited Mar 30 '16 at 15:11
alex
1176
1176
asked Sep 23 '09 at 18:40
Roy Rico
3,49443551
3,49443551
2
There are at least 2 questions here: Local DNS config, public DNS servers. Post 2 questions next time.
– hyperslug
Sep 23 '09 at 19:09
16
I agree, but i'm looking for an overall solution. each question on it's own would have a correct answer, but may not mesh, i'm trying to look for solution to both problems that works together.
– Roy Rico
Sep 23 '09 at 20:51
@RoyRico Did you ever find a good solution? I am trying to do the exat same thing witha Tomato router and am running into walls at every direction.
– Jeff
Dec 15 '12 at 3:04
If you have a linux box, here is how to setup DNSMASq in details -- sfxpt.wordpress.com/2011/02/06/…
– xpt
Jun 15 '14 at 23:29
The new Google DNS servers are 8.8.8.8 and 8.8.4.4 in case anyone was wondering...
– Tmanok
Feb 13 at 21:03
add a comment |
2
There are at least 2 questions here: Local DNS config, public DNS servers. Post 2 questions next time.
– hyperslug
Sep 23 '09 at 19:09
16
I agree, but i'm looking for an overall solution. each question on it's own would have a correct answer, but may not mesh, i'm trying to look for solution to both problems that works together.
– Roy Rico
Sep 23 '09 at 20:51
@RoyRico Did you ever find a good solution? I am trying to do the exat same thing witha Tomato router and am running into walls at every direction.
– Jeff
Dec 15 '12 at 3:04
If you have a linux box, here is how to setup DNSMASq in details -- sfxpt.wordpress.com/2011/02/06/…
– xpt
Jun 15 '14 at 23:29
The new Google DNS servers are 8.8.8.8 and 8.8.4.4 in case anyone was wondering...
– Tmanok
Feb 13 at 21:03
2
2
There are at least 2 questions here: Local DNS config, public DNS servers. Post 2 questions next time.
– hyperslug
Sep 23 '09 at 19:09
There are at least 2 questions here: Local DNS config, public DNS servers. Post 2 questions next time.
– hyperslug
Sep 23 '09 at 19:09
16
16
I agree, but i'm looking for an overall solution. each question on it's own would have a correct answer, but may not mesh, i'm trying to look for solution to both problems that works together.
– Roy Rico
Sep 23 '09 at 20:51
I agree, but i'm looking for an overall solution. each question on it's own would have a correct answer, but may not mesh, i'm trying to look for solution to both problems that works together.
– Roy Rico
Sep 23 '09 at 20:51
@RoyRico Did you ever find a good solution? I am trying to do the exat same thing witha Tomato router and am running into walls at every direction.
– Jeff
Dec 15 '12 at 3:04
@RoyRico Did you ever find a good solution? I am trying to do the exat same thing witha Tomato router and am running into walls at every direction.
– Jeff
Dec 15 '12 at 3:04
If you have a linux box, here is how to setup DNSMASq in details -- sfxpt.wordpress.com/2011/02/06/…
– xpt
Jun 15 '14 at 23:29
If you have a linux box, here is how to setup DNSMASq in details -- sfxpt.wordpress.com/2011/02/06/…
– xpt
Jun 15 '14 at 23:29
The new Google DNS servers are 8.8.8.8 and 8.8.4.4 in case anyone was wondering...
– Tmanok
Feb 13 at 21:03
The new Google DNS servers are 8.8.8.8 and 8.8.4.4 in case anyone was wondering...
– Tmanok
Feb 13 at 21:03
add a comment |
13 Answers
13
active
oldest
votes
If you want internal fake domains to work you can't configure your workstations with any DNS servers except your own.
Once you set up BIND it can work by itself and you don't need your ISP's or any other non-authoritative DNS servers at all.
7
However a good netizen will forward to their ISP's DNS caches if possible. The load on the root DNS servers is horrendous. Especially for small sites like this one, because it wouldn't scale if every household decided to go direct. (If you're worried about ISP tampering, use DNSSEC).
– sourcejedi
May 1 '13 at 18:53
1
@sourcejedi, you misunderstand what a caching DNS server actually does.. it certainly doesn't pound on the root servers, it only bothers them maybe once a week.
– milli
Feb 12 '14 at 5:31
7
There's a different reason why you should forward to your ISP DNS servers... you'll look like an ordinary client to them. If you don't and they see you have a system that's sending DNS queries all over the world, they're going to assume you're running a DNS server and might just throw a firewall rule in your face and hose you. You'll struggle to figure out what broke and probably waste hours trying to figure it out if/when that happens.
– milli
Feb 12 '14 at 5:32
Further to @milli's point, your ISP's DNS may also override resolution of some domains to their private machines with faster/cached/unmetered content. Using public DNS can break those services or cost you more.
– Walf
May 19 '17 at 3:03
add a comment |
Basically you need to run your own DHCP and DNS server. You're already running your own DHCP server if you have a typical router that gives out private IP addresses.
Your DHCP server must be configured to hand out your router IP as the gateway address, and your DNS server IP as the DNS server address, obviously.
Your DNS server must be configured to resolve a non-official top-level domain locally, such as .local
, and then forward any other requests to another DNS. In BIND you need to add a forwarders { }
section to your `/etc/bind/named.conf.options' which contains the public DNS servers you want to use to resolve non-local addresses. As other comments suggest, if you don't want to forward to your ISP's DNS servers, you can use OpenDNS, Google's public DNS servers, or 4.2.2.1/4.2.2.2 (I forget who does those).
If you are running your own DNS server, you need a box that will be on all the time, as all DNS queries on your home network will go through it. This box needs a fixed IP on your home subnet. Make sure it can't get bulldozed by DHCP, and the box itself should not be getting an IP via DHCP. If your DHCP is configured to hand out addresses from 192.168.1.1 to 192.168.1.100 for example, then give your DNS server the IP 192.168.1.101. In the usual situation of home routers you just need to simply tell the router that the DNS server is 192.168.1.101 and reboot.
If you can get a local DNS running on your broadband router, great, but a DNS server might benefit from lots of RAM for caching queries, depending on which DNS software you use. On my network I just use straight BIND. Sounds like you might have a little experience with that and for me it works great.
3
4.2.2.1/4.2.2.2/4.2.2.3 are from Layer 3.
– Hengjie
Nov 28 '12 at 11:42
1
Excellent answer! Thanks for the complete, clear info. I'll try setting this up on my local network soon.
– Form
Sep 23 '15 at 12:41
2
Success! This approach is sound. Setting a fixed IP outside of the addressable range / avoiding DHCP for the DNS box is especially relevant. Thanks!
– Form
Sep 25 '15 at 0:57
@Hengjie what is Layer 3?
– Jonathan
Jan 4 at 21:05
Layer 3 is a datacenter provider as well as a network provider. They also happen to provide rock solid DNS servers.
– Hengjie
Jan 10 at 17:22
add a comment |
Are there any open DNS servers that are reliable
You said it: OpenDNS.
208.67.222.222
208.67.220.220
2
I would also look at aboutdebian.com/dns.htm for a good overview of the different ways you can setup your own dns server.
– Kenneth Cochran
Sep 23 '09 at 19:04
1
+1 for OpenDNS. I use it both at work and at home. Fantastic service.
– DWilliams
Sep 24 '09 at 0:19
4
Be careful that OpenDNS name servers are liars: they rewrite DNS responses, to direct you to an ad service or to censor some destinations.
– bortzmeyer
Sep 24 '09 at 7:55
1
@bortz, I haven't seen them lie about it, but they do redirect to their landing page + ads in case of malformed URL's. The censoring is opt-in and is off by default.
– hyperslug
Sep 24 '09 at 17:24
11
Google's public DNS servers at 8.8.8.8 and 8.8.4.4 are also pretty good.
– LawrenceC
Feb 16 '11 at 14:30
|
show 3 more comments
If you are running Windows - you should take a look at Simple DNS Plus - it is a full DNS server that also comes with a DHCP server plug-in - and has an easy-to-use GUI.
[Note: the product is developed by the author of this post]
I'm running windows as one of my machines, but it's not always on. Linux machine is usually on.
– Roy Rico
Jan 25 '11 at 1:31
add a comment |
Unbound is pretty easy, supports bind style config files and fairly reliable. If the server will be a stand-alone 'gateway' type box, and you'd like a few extra niceties, you might want to take a look at the firewall/gateway distro called untangle as well.
add a comment |
If you have a linux box then you'd want to setup DNSMASq got your local addresses and use it as a forwarding/caching DNS server for external addresses. This is also often what is used on linux distributions for home routers such as openwrt/ddwrt/tomato.
Alternately, on mostly Apple/Mac networks you'd be using Bonjour/Zeroconf which both Linux and Apple computers can communicate on for broadcast level DNS/service resolution.
That being said, on a purely hybrid network with all three OS running, you'll definately want a local DNS server with forwarding to either OpenDNS, GoogleDNS, or your local ISP DNS depending on your location/needs.
add a comment |
4.2.2.1 & 4.2.2.2 are what I use
edit: that is, in regard to public servers. Easy to remember and I don't think I've seen them fail since I've been using them.
Iv'e seen those before. Who runs those? Are the public allowed to use them? how reliable are they?
– Roy Rico
Sep 23 '09 at 18:46
Verizon. Seems like they don't care. Very.
– hyperslug
Sep 23 '09 at 18:55
They are open DNS servers, free for public use. They are both fast and reliable.
– Walter
Mar 3 '10 at 3:16
3
I have seen 4.2.2.2 fail enough for our customers (who require reliable DNS for credit card processing!) that I always change these to Google's Public DNS or OpenDNS whenever I see them. Changing away from Verizon's servers always clears this problem immediately.
– Stephen Jennings
Mar 3 '10 at 3:28
add a comment |
Any Broadband router delivers both DNS & DHCP services for the local network.
If you want INcomming connections from internet to local machines you need a router that also supports DynDNS and Incomming PortForwarding.
If you pick one from the DD-wrt supported hardware list you can flash it with that Firmware and it will support any feature you could ever need in your small network.
3
I don't think that most broadband routers provide for DNS service, at least not with the provided firmware. Most just provide DHCP and use that to tell your systems to use your ISP's DNS servers. Now, if you flash on a 3rd party firmware like DD-WRT, OpenWRT, or Tomato, then they can provide DNS services as well.
– afrazier
Feb 16 '11 at 15:00
add a comment |
For running a DNS server on your LAN, take a look at 'pdnsd' which is a nameserver for *nix.
add a comment |
Some free DNS servers you can use for forwarding:
1.1.1.1 - Cloudflare
4.2.2.1 - Layer 3
4.2.2.2 - Layer 3
4.2.2.3 - Layer 3
8.8.8.8 - Google
8.8.4.4 - Google
208.67.222.222 - OpenDNS
208.67.220.220 - OpenDNS
add a comment |
If you download the DNS benchmark program from link text, it will benchmark a list of public DNS servers as well as your local DNS server. After running this program, try putting a copy of the fastest servers into the DNS setting on your router and then renew your DHCP session and running the test again.
If your router allows it, add both the router and one of the fast external DNS servers to the list of DNS servers that it hands to DHCP client (but pick a different one from the one that you entered for the router DNS server addresses).
add a comment |
I had a similar problem. I bought an OpenWRT compatible router and installed OpenWRT. It offers static IP binding along with name resolution in the router, which enabled me to give names to my computers and devices in the network as I wish.
add a comment |
Maybe I'm saying something stupid.
In this case I would simply add IP and names to the hosts files on the individual machines..
192.168.0.120 tv.local
192.168.0.80 studiopc.local
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f45789%2frunning-dns-locally-for-home-network%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
13 Answers
13
active
oldest
votes
13 Answers
13
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you want internal fake domains to work you can't configure your workstations with any DNS servers except your own.
Once you set up BIND it can work by itself and you don't need your ISP's or any other non-authoritative DNS servers at all.
7
However a good netizen will forward to their ISP's DNS caches if possible. The load on the root DNS servers is horrendous. Especially for small sites like this one, because it wouldn't scale if every household decided to go direct. (If you're worried about ISP tampering, use DNSSEC).
– sourcejedi
May 1 '13 at 18:53
1
@sourcejedi, you misunderstand what a caching DNS server actually does.. it certainly doesn't pound on the root servers, it only bothers them maybe once a week.
– milli
Feb 12 '14 at 5:31
7
There's a different reason why you should forward to your ISP DNS servers... you'll look like an ordinary client to them. If you don't and they see you have a system that's sending DNS queries all over the world, they're going to assume you're running a DNS server and might just throw a firewall rule in your face and hose you. You'll struggle to figure out what broke and probably waste hours trying to figure it out if/when that happens.
– milli
Feb 12 '14 at 5:32
Further to @milli's point, your ISP's DNS may also override resolution of some domains to their private machines with faster/cached/unmetered content. Using public DNS can break those services or cost you more.
– Walf
May 19 '17 at 3:03
add a comment |
If you want internal fake domains to work you can't configure your workstations with any DNS servers except your own.
Once you set up BIND it can work by itself and you don't need your ISP's or any other non-authoritative DNS servers at all.
7
However a good netizen will forward to their ISP's DNS caches if possible. The load on the root DNS servers is horrendous. Especially for small sites like this one, because it wouldn't scale if every household decided to go direct. (If you're worried about ISP tampering, use DNSSEC).
– sourcejedi
May 1 '13 at 18:53
1
@sourcejedi, you misunderstand what a caching DNS server actually does.. it certainly doesn't pound on the root servers, it only bothers them maybe once a week.
– milli
Feb 12 '14 at 5:31
7
There's a different reason why you should forward to your ISP DNS servers... you'll look like an ordinary client to them. If you don't and they see you have a system that's sending DNS queries all over the world, they're going to assume you're running a DNS server and might just throw a firewall rule in your face and hose you. You'll struggle to figure out what broke and probably waste hours trying to figure it out if/when that happens.
– milli
Feb 12 '14 at 5:32
Further to @milli's point, your ISP's DNS may also override resolution of some domains to their private machines with faster/cached/unmetered content. Using public DNS can break those services or cost you more.
– Walf
May 19 '17 at 3:03
add a comment |
If you want internal fake domains to work you can't configure your workstations with any DNS servers except your own.
Once you set up BIND it can work by itself and you don't need your ISP's or any other non-authoritative DNS servers at all.
If you want internal fake domains to work you can't configure your workstations with any DNS servers except your own.
Once you set up BIND it can work by itself and you don't need your ISP's or any other non-authoritative DNS servers at all.
edited Sep 24 '09 at 0:09
answered Sep 23 '09 at 18:58
Bender
84646
84646
7
However a good netizen will forward to their ISP's DNS caches if possible. The load on the root DNS servers is horrendous. Especially for small sites like this one, because it wouldn't scale if every household decided to go direct. (If you're worried about ISP tampering, use DNSSEC).
– sourcejedi
May 1 '13 at 18:53
1
@sourcejedi, you misunderstand what a caching DNS server actually does.. it certainly doesn't pound on the root servers, it only bothers them maybe once a week.
– milli
Feb 12 '14 at 5:31
7
There's a different reason why you should forward to your ISP DNS servers... you'll look like an ordinary client to them. If you don't and they see you have a system that's sending DNS queries all over the world, they're going to assume you're running a DNS server and might just throw a firewall rule in your face and hose you. You'll struggle to figure out what broke and probably waste hours trying to figure it out if/when that happens.
– milli
Feb 12 '14 at 5:32
Further to @milli's point, your ISP's DNS may also override resolution of some domains to their private machines with faster/cached/unmetered content. Using public DNS can break those services or cost you more.
– Walf
May 19 '17 at 3:03
add a comment |
7
However a good netizen will forward to their ISP's DNS caches if possible. The load on the root DNS servers is horrendous. Especially for small sites like this one, because it wouldn't scale if every household decided to go direct. (If you're worried about ISP tampering, use DNSSEC).
– sourcejedi
May 1 '13 at 18:53
1
@sourcejedi, you misunderstand what a caching DNS server actually does.. it certainly doesn't pound on the root servers, it only bothers them maybe once a week.
– milli
Feb 12 '14 at 5:31
7
There's a different reason why you should forward to your ISP DNS servers... you'll look like an ordinary client to them. If you don't and they see you have a system that's sending DNS queries all over the world, they're going to assume you're running a DNS server and might just throw a firewall rule in your face and hose you. You'll struggle to figure out what broke and probably waste hours trying to figure it out if/when that happens.
– milli
Feb 12 '14 at 5:32
Further to @milli's point, your ISP's DNS may also override resolution of some domains to their private machines with faster/cached/unmetered content. Using public DNS can break those services or cost you more.
– Walf
May 19 '17 at 3:03
7
7
However a good netizen will forward to their ISP's DNS caches if possible. The load on the root DNS servers is horrendous. Especially for small sites like this one, because it wouldn't scale if every household decided to go direct. (If you're worried about ISP tampering, use DNSSEC).
– sourcejedi
May 1 '13 at 18:53
However a good netizen will forward to their ISP's DNS caches if possible. The load on the root DNS servers is horrendous. Especially for small sites like this one, because it wouldn't scale if every household decided to go direct. (If you're worried about ISP tampering, use DNSSEC).
– sourcejedi
May 1 '13 at 18:53
1
1
@sourcejedi, you misunderstand what a caching DNS server actually does.. it certainly doesn't pound on the root servers, it only bothers them maybe once a week.
– milli
Feb 12 '14 at 5:31
@sourcejedi, you misunderstand what a caching DNS server actually does.. it certainly doesn't pound on the root servers, it only bothers them maybe once a week.
– milli
Feb 12 '14 at 5:31
7
7
There's a different reason why you should forward to your ISP DNS servers... you'll look like an ordinary client to them. If you don't and they see you have a system that's sending DNS queries all over the world, they're going to assume you're running a DNS server and might just throw a firewall rule in your face and hose you. You'll struggle to figure out what broke and probably waste hours trying to figure it out if/when that happens.
– milli
Feb 12 '14 at 5:32
There's a different reason why you should forward to your ISP DNS servers... you'll look like an ordinary client to them. If you don't and they see you have a system that's sending DNS queries all over the world, they're going to assume you're running a DNS server and might just throw a firewall rule in your face and hose you. You'll struggle to figure out what broke and probably waste hours trying to figure it out if/when that happens.
– milli
Feb 12 '14 at 5:32
Further to @milli's point, your ISP's DNS may also override resolution of some domains to their private machines with faster/cached/unmetered content. Using public DNS can break those services or cost you more.
– Walf
May 19 '17 at 3:03
Further to @milli's point, your ISP's DNS may also override resolution of some domains to their private machines with faster/cached/unmetered content. Using public DNS can break those services or cost you more.
– Walf
May 19 '17 at 3:03
add a comment |
Basically you need to run your own DHCP and DNS server. You're already running your own DHCP server if you have a typical router that gives out private IP addresses.
Your DHCP server must be configured to hand out your router IP as the gateway address, and your DNS server IP as the DNS server address, obviously.
Your DNS server must be configured to resolve a non-official top-level domain locally, such as .local
, and then forward any other requests to another DNS. In BIND you need to add a forwarders { }
section to your `/etc/bind/named.conf.options' which contains the public DNS servers you want to use to resolve non-local addresses. As other comments suggest, if you don't want to forward to your ISP's DNS servers, you can use OpenDNS, Google's public DNS servers, or 4.2.2.1/4.2.2.2 (I forget who does those).
If you are running your own DNS server, you need a box that will be on all the time, as all DNS queries on your home network will go through it. This box needs a fixed IP on your home subnet. Make sure it can't get bulldozed by DHCP, and the box itself should not be getting an IP via DHCP. If your DHCP is configured to hand out addresses from 192.168.1.1 to 192.168.1.100 for example, then give your DNS server the IP 192.168.1.101. In the usual situation of home routers you just need to simply tell the router that the DNS server is 192.168.1.101 and reboot.
If you can get a local DNS running on your broadband router, great, but a DNS server might benefit from lots of RAM for caching queries, depending on which DNS software you use. On my network I just use straight BIND. Sounds like you might have a little experience with that and for me it works great.
3
4.2.2.1/4.2.2.2/4.2.2.3 are from Layer 3.
– Hengjie
Nov 28 '12 at 11:42
1
Excellent answer! Thanks for the complete, clear info. I'll try setting this up on my local network soon.
– Form
Sep 23 '15 at 12:41
2
Success! This approach is sound. Setting a fixed IP outside of the addressable range / avoiding DHCP for the DNS box is especially relevant. Thanks!
– Form
Sep 25 '15 at 0:57
@Hengjie what is Layer 3?
– Jonathan
Jan 4 at 21:05
Layer 3 is a datacenter provider as well as a network provider. They also happen to provide rock solid DNS servers.
– Hengjie
Jan 10 at 17:22
add a comment |
Basically you need to run your own DHCP and DNS server. You're already running your own DHCP server if you have a typical router that gives out private IP addresses.
Your DHCP server must be configured to hand out your router IP as the gateway address, and your DNS server IP as the DNS server address, obviously.
Your DNS server must be configured to resolve a non-official top-level domain locally, such as .local
, and then forward any other requests to another DNS. In BIND you need to add a forwarders { }
section to your `/etc/bind/named.conf.options' which contains the public DNS servers you want to use to resolve non-local addresses. As other comments suggest, if you don't want to forward to your ISP's DNS servers, you can use OpenDNS, Google's public DNS servers, or 4.2.2.1/4.2.2.2 (I forget who does those).
If you are running your own DNS server, you need a box that will be on all the time, as all DNS queries on your home network will go through it. This box needs a fixed IP on your home subnet. Make sure it can't get bulldozed by DHCP, and the box itself should not be getting an IP via DHCP. If your DHCP is configured to hand out addresses from 192.168.1.1 to 192.168.1.100 for example, then give your DNS server the IP 192.168.1.101. In the usual situation of home routers you just need to simply tell the router that the DNS server is 192.168.1.101 and reboot.
If you can get a local DNS running on your broadband router, great, but a DNS server might benefit from lots of RAM for caching queries, depending on which DNS software you use. On my network I just use straight BIND. Sounds like you might have a little experience with that and for me it works great.
3
4.2.2.1/4.2.2.2/4.2.2.3 are from Layer 3.
– Hengjie
Nov 28 '12 at 11:42
1
Excellent answer! Thanks for the complete, clear info. I'll try setting this up on my local network soon.
– Form
Sep 23 '15 at 12:41
2
Success! This approach is sound. Setting a fixed IP outside of the addressable range / avoiding DHCP for the DNS box is especially relevant. Thanks!
– Form
Sep 25 '15 at 0:57
@Hengjie what is Layer 3?
– Jonathan
Jan 4 at 21:05
Layer 3 is a datacenter provider as well as a network provider. They also happen to provide rock solid DNS servers.
– Hengjie
Jan 10 at 17:22
add a comment |
Basically you need to run your own DHCP and DNS server. You're already running your own DHCP server if you have a typical router that gives out private IP addresses.
Your DHCP server must be configured to hand out your router IP as the gateway address, and your DNS server IP as the DNS server address, obviously.
Your DNS server must be configured to resolve a non-official top-level domain locally, such as .local
, and then forward any other requests to another DNS. In BIND you need to add a forwarders { }
section to your `/etc/bind/named.conf.options' which contains the public DNS servers you want to use to resolve non-local addresses. As other comments suggest, if you don't want to forward to your ISP's DNS servers, you can use OpenDNS, Google's public DNS servers, or 4.2.2.1/4.2.2.2 (I forget who does those).
If you are running your own DNS server, you need a box that will be on all the time, as all DNS queries on your home network will go through it. This box needs a fixed IP on your home subnet. Make sure it can't get bulldozed by DHCP, and the box itself should not be getting an IP via DHCP. If your DHCP is configured to hand out addresses from 192.168.1.1 to 192.168.1.100 for example, then give your DNS server the IP 192.168.1.101. In the usual situation of home routers you just need to simply tell the router that the DNS server is 192.168.1.101 and reboot.
If you can get a local DNS running on your broadband router, great, but a DNS server might benefit from lots of RAM for caching queries, depending on which DNS software you use. On my network I just use straight BIND. Sounds like you might have a little experience with that and for me it works great.
Basically you need to run your own DHCP and DNS server. You're already running your own DHCP server if you have a typical router that gives out private IP addresses.
Your DHCP server must be configured to hand out your router IP as the gateway address, and your DNS server IP as the DNS server address, obviously.
Your DNS server must be configured to resolve a non-official top-level domain locally, such as .local
, and then forward any other requests to another DNS. In BIND you need to add a forwarders { }
section to your `/etc/bind/named.conf.options' which contains the public DNS servers you want to use to resolve non-local addresses. As other comments suggest, if you don't want to forward to your ISP's DNS servers, you can use OpenDNS, Google's public DNS servers, or 4.2.2.1/4.2.2.2 (I forget who does those).
If you are running your own DNS server, you need a box that will be on all the time, as all DNS queries on your home network will go through it. This box needs a fixed IP on your home subnet. Make sure it can't get bulldozed by DHCP, and the box itself should not be getting an IP via DHCP. If your DHCP is configured to hand out addresses from 192.168.1.1 to 192.168.1.100 for example, then give your DNS server the IP 192.168.1.101. In the usual situation of home routers you just need to simply tell the router that the DNS server is 192.168.1.101 and reboot.
If you can get a local DNS running on your broadband router, great, but a DNS server might benefit from lots of RAM for caching queries, depending on which DNS software you use. On my network I just use straight BIND. Sounds like you might have a little experience with that and for me it works great.
edited Aug 30 '16 at 17:50
Jon
2008
2008
answered Feb 16 '11 at 14:43
LawrenceC
58.7k10102179
58.7k10102179
3
4.2.2.1/4.2.2.2/4.2.2.3 are from Layer 3.
– Hengjie
Nov 28 '12 at 11:42
1
Excellent answer! Thanks for the complete, clear info. I'll try setting this up on my local network soon.
– Form
Sep 23 '15 at 12:41
2
Success! This approach is sound. Setting a fixed IP outside of the addressable range / avoiding DHCP for the DNS box is especially relevant. Thanks!
– Form
Sep 25 '15 at 0:57
@Hengjie what is Layer 3?
– Jonathan
Jan 4 at 21:05
Layer 3 is a datacenter provider as well as a network provider. They also happen to provide rock solid DNS servers.
– Hengjie
Jan 10 at 17:22
add a comment |
3
4.2.2.1/4.2.2.2/4.2.2.3 are from Layer 3.
– Hengjie
Nov 28 '12 at 11:42
1
Excellent answer! Thanks for the complete, clear info. I'll try setting this up on my local network soon.
– Form
Sep 23 '15 at 12:41
2
Success! This approach is sound. Setting a fixed IP outside of the addressable range / avoiding DHCP for the DNS box is especially relevant. Thanks!
– Form
Sep 25 '15 at 0:57
@Hengjie what is Layer 3?
– Jonathan
Jan 4 at 21:05
Layer 3 is a datacenter provider as well as a network provider. They also happen to provide rock solid DNS servers.
– Hengjie
Jan 10 at 17:22
3
3
4.2.2.1/4.2.2.2/4.2.2.3 are from Layer 3.
– Hengjie
Nov 28 '12 at 11:42
4.2.2.1/4.2.2.2/4.2.2.3 are from Layer 3.
– Hengjie
Nov 28 '12 at 11:42
1
1
Excellent answer! Thanks for the complete, clear info. I'll try setting this up on my local network soon.
– Form
Sep 23 '15 at 12:41
Excellent answer! Thanks for the complete, clear info. I'll try setting this up on my local network soon.
– Form
Sep 23 '15 at 12:41
2
2
Success! This approach is sound. Setting a fixed IP outside of the addressable range / avoiding DHCP for the DNS box is especially relevant. Thanks!
– Form
Sep 25 '15 at 0:57
Success! This approach is sound. Setting a fixed IP outside of the addressable range / avoiding DHCP for the DNS box is especially relevant. Thanks!
– Form
Sep 25 '15 at 0:57
@Hengjie what is Layer 3?
– Jonathan
Jan 4 at 21:05
@Hengjie what is Layer 3?
– Jonathan
Jan 4 at 21:05
Layer 3 is a datacenter provider as well as a network provider. They also happen to provide rock solid DNS servers.
– Hengjie
Jan 10 at 17:22
Layer 3 is a datacenter provider as well as a network provider. They also happen to provide rock solid DNS servers.
– Hengjie
Jan 10 at 17:22
add a comment |
Are there any open DNS servers that are reliable
You said it: OpenDNS.
208.67.222.222
208.67.220.220
2
I would also look at aboutdebian.com/dns.htm for a good overview of the different ways you can setup your own dns server.
– Kenneth Cochran
Sep 23 '09 at 19:04
1
+1 for OpenDNS. I use it both at work and at home. Fantastic service.
– DWilliams
Sep 24 '09 at 0:19
4
Be careful that OpenDNS name servers are liars: they rewrite DNS responses, to direct you to an ad service or to censor some destinations.
– bortzmeyer
Sep 24 '09 at 7:55
1
@bortz, I haven't seen them lie about it, but they do redirect to their landing page + ads in case of malformed URL's. The censoring is opt-in and is off by default.
– hyperslug
Sep 24 '09 at 17:24
11
Google's public DNS servers at 8.8.8.8 and 8.8.4.4 are also pretty good.
– LawrenceC
Feb 16 '11 at 14:30
|
show 3 more comments
Are there any open DNS servers that are reliable
You said it: OpenDNS.
208.67.222.222
208.67.220.220
2
I would also look at aboutdebian.com/dns.htm for a good overview of the different ways you can setup your own dns server.
– Kenneth Cochran
Sep 23 '09 at 19:04
1
+1 for OpenDNS. I use it both at work and at home. Fantastic service.
– DWilliams
Sep 24 '09 at 0:19
4
Be careful that OpenDNS name servers are liars: they rewrite DNS responses, to direct you to an ad service or to censor some destinations.
– bortzmeyer
Sep 24 '09 at 7:55
1
@bortz, I haven't seen them lie about it, but they do redirect to their landing page + ads in case of malformed URL's. The censoring is opt-in and is off by default.
– hyperslug
Sep 24 '09 at 17:24
11
Google's public DNS servers at 8.8.8.8 and 8.8.4.4 are also pretty good.
– LawrenceC
Feb 16 '11 at 14:30
|
show 3 more comments
Are there any open DNS servers that are reliable
You said it: OpenDNS.
208.67.222.222
208.67.220.220
Are there any open DNS servers that are reliable
You said it: OpenDNS.
208.67.222.222
208.67.220.220
answered Sep 23 '09 at 18:57
hyperslug
12k43960
12k43960
2
I would also look at aboutdebian.com/dns.htm for a good overview of the different ways you can setup your own dns server.
– Kenneth Cochran
Sep 23 '09 at 19:04
1
+1 for OpenDNS. I use it both at work and at home. Fantastic service.
– DWilliams
Sep 24 '09 at 0:19
4
Be careful that OpenDNS name servers are liars: they rewrite DNS responses, to direct you to an ad service or to censor some destinations.
– bortzmeyer
Sep 24 '09 at 7:55
1
@bortz, I haven't seen them lie about it, but they do redirect to their landing page + ads in case of malformed URL's. The censoring is opt-in and is off by default.
– hyperslug
Sep 24 '09 at 17:24
11
Google's public DNS servers at 8.8.8.8 and 8.8.4.4 are also pretty good.
– LawrenceC
Feb 16 '11 at 14:30
|
show 3 more comments
2
I would also look at aboutdebian.com/dns.htm for a good overview of the different ways you can setup your own dns server.
– Kenneth Cochran
Sep 23 '09 at 19:04
1
+1 for OpenDNS. I use it both at work and at home. Fantastic service.
– DWilliams
Sep 24 '09 at 0:19
4
Be careful that OpenDNS name servers are liars: they rewrite DNS responses, to direct you to an ad service or to censor some destinations.
– bortzmeyer
Sep 24 '09 at 7:55
1
@bortz, I haven't seen them lie about it, but they do redirect to their landing page + ads in case of malformed URL's. The censoring is opt-in and is off by default.
– hyperslug
Sep 24 '09 at 17:24
11
Google's public DNS servers at 8.8.8.8 and 8.8.4.4 are also pretty good.
– LawrenceC
Feb 16 '11 at 14:30
2
2
I would also look at aboutdebian.com/dns.htm for a good overview of the different ways you can setup your own dns server.
– Kenneth Cochran
Sep 23 '09 at 19:04
I would also look at aboutdebian.com/dns.htm for a good overview of the different ways you can setup your own dns server.
– Kenneth Cochran
Sep 23 '09 at 19:04
1
1
+1 for OpenDNS. I use it both at work and at home. Fantastic service.
– DWilliams
Sep 24 '09 at 0:19
+1 for OpenDNS. I use it both at work and at home. Fantastic service.
– DWilliams
Sep 24 '09 at 0:19
4
4
Be careful that OpenDNS name servers are liars: they rewrite DNS responses, to direct you to an ad service or to censor some destinations.
– bortzmeyer
Sep 24 '09 at 7:55
Be careful that OpenDNS name servers are liars: they rewrite DNS responses, to direct you to an ad service or to censor some destinations.
– bortzmeyer
Sep 24 '09 at 7:55
1
1
@bortz, I haven't seen them lie about it, but they do redirect to their landing page + ads in case of malformed URL's. The censoring is opt-in and is off by default.
– hyperslug
Sep 24 '09 at 17:24
@bortz, I haven't seen them lie about it, but they do redirect to their landing page + ads in case of malformed URL's. The censoring is opt-in and is off by default.
– hyperslug
Sep 24 '09 at 17:24
11
11
Google's public DNS servers at 8.8.8.8 and 8.8.4.4 are also pretty good.
– LawrenceC
Feb 16 '11 at 14:30
Google's public DNS servers at 8.8.8.8 and 8.8.4.4 are also pretty good.
– LawrenceC
Feb 16 '11 at 14:30
|
show 3 more comments
If you are running Windows - you should take a look at Simple DNS Plus - it is a full DNS server that also comes with a DHCP server plug-in - and has an easy-to-use GUI.
[Note: the product is developed by the author of this post]
I'm running windows as one of my machines, but it's not always on. Linux machine is usually on.
– Roy Rico
Jan 25 '11 at 1:31
add a comment |
If you are running Windows - you should take a look at Simple DNS Plus - it is a full DNS server that also comes with a DHCP server plug-in - and has an easy-to-use GUI.
[Note: the product is developed by the author of this post]
I'm running windows as one of my machines, but it's not always on. Linux machine is usually on.
– Roy Rico
Jan 25 '11 at 1:31
add a comment |
If you are running Windows - you should take a look at Simple DNS Plus - it is a full DNS server that also comes with a DHCP server plug-in - and has an easy-to-use GUI.
[Note: the product is developed by the author of this post]
If you are running Windows - you should take a look at Simple DNS Plus - it is a full DNS server that also comes with a DHCP server plug-in - and has an easy-to-use GUI.
[Note: the product is developed by the author of this post]
edited Jun 10 '14 at 22:06
Ganesh Sittampalam
1076
1076
answered Sep 25 '09 at 15:38
Jesper
632167
632167
I'm running windows as one of my machines, but it's not always on. Linux machine is usually on.
– Roy Rico
Jan 25 '11 at 1:31
add a comment |
I'm running windows as one of my machines, but it's not always on. Linux machine is usually on.
– Roy Rico
Jan 25 '11 at 1:31
I'm running windows as one of my machines, but it's not always on. Linux machine is usually on.
– Roy Rico
Jan 25 '11 at 1:31
I'm running windows as one of my machines, but it's not always on. Linux machine is usually on.
– Roy Rico
Jan 25 '11 at 1:31
add a comment |
Unbound is pretty easy, supports bind style config files and fairly reliable. If the server will be a stand-alone 'gateway' type box, and you'd like a few extra niceties, you might want to take a look at the firewall/gateway distro called untangle as well.
add a comment |
Unbound is pretty easy, supports bind style config files and fairly reliable. If the server will be a stand-alone 'gateway' type box, and you'd like a few extra niceties, you might want to take a look at the firewall/gateway distro called untangle as well.
add a comment |
Unbound is pretty easy, supports bind style config files and fairly reliable. If the server will be a stand-alone 'gateway' type box, and you'd like a few extra niceties, you might want to take a look at the firewall/gateway distro called untangle as well.
Unbound is pretty easy, supports bind style config files and fairly reliable. If the server will be a stand-alone 'gateway' type box, and you'd like a few extra niceties, you might want to take a look at the firewall/gateway distro called untangle as well.
answered Sep 23 '09 at 23:51
Journeyman Geek♦
112k43216366
112k43216366
add a comment |
add a comment |
If you have a linux box then you'd want to setup DNSMASq got your local addresses and use it as a forwarding/caching DNS server for external addresses. This is also often what is used on linux distributions for home routers such as openwrt/ddwrt/tomato.
Alternately, on mostly Apple/Mac networks you'd be using Bonjour/Zeroconf which both Linux and Apple computers can communicate on for broadcast level DNS/service resolution.
That being said, on a purely hybrid network with all three OS running, you'll definately want a local DNS server with forwarding to either OpenDNS, GoogleDNS, or your local ISP DNS depending on your location/needs.
add a comment |
If you have a linux box then you'd want to setup DNSMASq got your local addresses and use it as a forwarding/caching DNS server for external addresses. This is also often what is used on linux distributions for home routers such as openwrt/ddwrt/tomato.
Alternately, on mostly Apple/Mac networks you'd be using Bonjour/Zeroconf which both Linux and Apple computers can communicate on for broadcast level DNS/service resolution.
That being said, on a purely hybrid network with all three OS running, you'll definately want a local DNS server with forwarding to either OpenDNS, GoogleDNS, or your local ISP DNS depending on your location/needs.
add a comment |
If you have a linux box then you'd want to setup DNSMASq got your local addresses and use it as a forwarding/caching DNS server for external addresses. This is also often what is used on linux distributions for home routers such as openwrt/ddwrt/tomato.
Alternately, on mostly Apple/Mac networks you'd be using Bonjour/Zeroconf which both Linux and Apple computers can communicate on for broadcast level DNS/service resolution.
That being said, on a purely hybrid network with all three OS running, you'll definately want a local DNS server with forwarding to either OpenDNS, GoogleDNS, or your local ISP DNS depending on your location/needs.
If you have a linux box then you'd want to setup DNSMASq got your local addresses and use it as a forwarding/caching DNS server for external addresses. This is also often what is used on linux distributions for home routers such as openwrt/ddwrt/tomato.
Alternately, on mostly Apple/Mac networks you'd be using Bonjour/Zeroconf which both Linux and Apple computers can communicate on for broadcast level DNS/service resolution.
That being said, on a purely hybrid network with all three OS running, you'll definately want a local DNS server with forwarding to either OpenDNS, GoogleDNS, or your local ISP DNS depending on your location/needs.
answered Mar 3 '10 at 5:23
jonathanserafini
2,134294
2,134294
add a comment |
add a comment |
4.2.2.1 & 4.2.2.2 are what I use
edit: that is, in regard to public servers. Easy to remember and I don't think I've seen them fail since I've been using them.
Iv'e seen those before. Who runs those? Are the public allowed to use them? how reliable are they?
– Roy Rico
Sep 23 '09 at 18:46
Verizon. Seems like they don't care. Very.
– hyperslug
Sep 23 '09 at 18:55
They are open DNS servers, free for public use. They are both fast and reliable.
– Walter
Mar 3 '10 at 3:16
3
I have seen 4.2.2.2 fail enough for our customers (who require reliable DNS for credit card processing!) that I always change these to Google's Public DNS or OpenDNS whenever I see them. Changing away from Verizon's servers always clears this problem immediately.
– Stephen Jennings
Mar 3 '10 at 3:28
add a comment |
4.2.2.1 & 4.2.2.2 are what I use
edit: that is, in regard to public servers. Easy to remember and I don't think I've seen them fail since I've been using them.
Iv'e seen those before. Who runs those? Are the public allowed to use them? how reliable are they?
– Roy Rico
Sep 23 '09 at 18:46
Verizon. Seems like they don't care. Very.
– hyperslug
Sep 23 '09 at 18:55
They are open DNS servers, free for public use. They are both fast and reliable.
– Walter
Mar 3 '10 at 3:16
3
I have seen 4.2.2.2 fail enough for our customers (who require reliable DNS for credit card processing!) that I always change these to Google's Public DNS or OpenDNS whenever I see them. Changing away from Verizon's servers always clears this problem immediately.
– Stephen Jennings
Mar 3 '10 at 3:28
add a comment |
4.2.2.1 & 4.2.2.2 are what I use
edit: that is, in regard to public servers. Easy to remember and I don't think I've seen them fail since I've been using them.
4.2.2.1 & 4.2.2.2 are what I use
edit: that is, in regard to public servers. Easy to remember and I don't think I've seen them fail since I've been using them.
answered Sep 23 '09 at 18:44
DHayes
2,0631016
2,0631016
Iv'e seen those before. Who runs those? Are the public allowed to use them? how reliable are they?
– Roy Rico
Sep 23 '09 at 18:46
Verizon. Seems like they don't care. Very.
– hyperslug
Sep 23 '09 at 18:55
They are open DNS servers, free for public use. They are both fast and reliable.
– Walter
Mar 3 '10 at 3:16
3
I have seen 4.2.2.2 fail enough for our customers (who require reliable DNS for credit card processing!) that I always change these to Google's Public DNS or OpenDNS whenever I see them. Changing away from Verizon's servers always clears this problem immediately.
– Stephen Jennings
Mar 3 '10 at 3:28
add a comment |
Iv'e seen those before. Who runs those? Are the public allowed to use them? how reliable are they?
– Roy Rico
Sep 23 '09 at 18:46
Verizon. Seems like they don't care. Very.
– hyperslug
Sep 23 '09 at 18:55
They are open DNS servers, free for public use. They are both fast and reliable.
– Walter
Mar 3 '10 at 3:16
3
I have seen 4.2.2.2 fail enough for our customers (who require reliable DNS for credit card processing!) that I always change these to Google's Public DNS or OpenDNS whenever I see them. Changing away from Verizon's servers always clears this problem immediately.
– Stephen Jennings
Mar 3 '10 at 3:28
Iv'e seen those before. Who runs those? Are the public allowed to use them? how reliable are they?
– Roy Rico
Sep 23 '09 at 18:46
Iv'e seen those before. Who runs those? Are the public allowed to use them? how reliable are they?
– Roy Rico
Sep 23 '09 at 18:46
Verizon. Seems like they don't care. Very.
– hyperslug
Sep 23 '09 at 18:55
Verizon. Seems like they don't care. Very.
– hyperslug
Sep 23 '09 at 18:55
They are open DNS servers, free for public use. They are both fast and reliable.
– Walter
Mar 3 '10 at 3:16
They are open DNS servers, free for public use. They are both fast and reliable.
– Walter
Mar 3 '10 at 3:16
3
3
I have seen 4.2.2.2 fail enough for our customers (who require reliable DNS for credit card processing!) that I always change these to Google's Public DNS or OpenDNS whenever I see them. Changing away from Verizon's servers always clears this problem immediately.
– Stephen Jennings
Mar 3 '10 at 3:28
I have seen 4.2.2.2 fail enough for our customers (who require reliable DNS for credit card processing!) that I always change these to Google's Public DNS or OpenDNS whenever I see them. Changing away from Verizon's servers always clears this problem immediately.
– Stephen Jennings
Mar 3 '10 at 3:28
add a comment |
Any Broadband router delivers both DNS & DHCP services for the local network.
If you want INcomming connections from internet to local machines you need a router that also supports DynDNS and Incomming PortForwarding.
If you pick one from the DD-wrt supported hardware list you can flash it with that Firmware and it will support any feature you could ever need in your small network.
3
I don't think that most broadband routers provide for DNS service, at least not with the provided firmware. Most just provide DHCP and use that to tell your systems to use your ISP's DNS servers. Now, if you flash on a 3rd party firmware like DD-WRT, OpenWRT, or Tomato, then they can provide DNS services as well.
– afrazier
Feb 16 '11 at 15:00
add a comment |
Any Broadband router delivers both DNS & DHCP services for the local network.
If you want INcomming connections from internet to local machines you need a router that also supports DynDNS and Incomming PortForwarding.
If you pick one from the DD-wrt supported hardware list you can flash it with that Firmware and it will support any feature you could ever need in your small network.
3
I don't think that most broadband routers provide for DNS service, at least not with the provided firmware. Most just provide DHCP and use that to tell your systems to use your ISP's DNS servers. Now, if you flash on a 3rd party firmware like DD-WRT, OpenWRT, or Tomato, then they can provide DNS services as well.
– afrazier
Feb 16 '11 at 15:00
add a comment |
Any Broadband router delivers both DNS & DHCP services for the local network.
If you want INcomming connections from internet to local machines you need a router that also supports DynDNS and Incomming PortForwarding.
If you pick one from the DD-wrt supported hardware list you can flash it with that Firmware and it will support any feature you could ever need in your small network.
Any Broadband router delivers both DNS & DHCP services for the local network.
If you want INcomming connections from internet to local machines you need a router that also supports DynDNS and Incomming PortForwarding.
If you pick one from the DD-wrt supported hardware list you can flash it with that Firmware and it will support any feature you could ever need in your small network.
answered Sep 23 '09 at 19:38
Nikolaas
312
312
3
I don't think that most broadband routers provide for DNS service, at least not with the provided firmware. Most just provide DHCP and use that to tell your systems to use your ISP's DNS servers. Now, if you flash on a 3rd party firmware like DD-WRT, OpenWRT, or Tomato, then they can provide DNS services as well.
– afrazier
Feb 16 '11 at 15:00
add a comment |
3
I don't think that most broadband routers provide for DNS service, at least not with the provided firmware. Most just provide DHCP and use that to tell your systems to use your ISP's DNS servers. Now, if you flash on a 3rd party firmware like DD-WRT, OpenWRT, or Tomato, then they can provide DNS services as well.
– afrazier
Feb 16 '11 at 15:00
3
3
I don't think that most broadband routers provide for DNS service, at least not with the provided firmware. Most just provide DHCP and use that to tell your systems to use your ISP's DNS servers. Now, if you flash on a 3rd party firmware like DD-WRT, OpenWRT, or Tomato, then they can provide DNS services as well.
– afrazier
Feb 16 '11 at 15:00
I don't think that most broadband routers provide for DNS service, at least not with the provided firmware. Most just provide DHCP and use that to tell your systems to use your ISP's DNS servers. Now, if you flash on a 3rd party firmware like DD-WRT, OpenWRT, or Tomato, then they can provide DNS services as well.
– afrazier
Feb 16 '11 at 15:00
add a comment |
For running a DNS server on your LAN, take a look at 'pdnsd' which is a nameserver for *nix.
add a comment |
For running a DNS server on your LAN, take a look at 'pdnsd' which is a nameserver for *nix.
add a comment |
For running a DNS server on your LAN, take a look at 'pdnsd' which is a nameserver for *nix.
For running a DNS server on your LAN, take a look at 'pdnsd' which is a nameserver for *nix.
edited Feb 27 '16 at 13:09
answered Sep 23 '09 at 18:46
Zuu
1112
1112
add a comment |
add a comment |
Some free DNS servers you can use for forwarding:
1.1.1.1 - Cloudflare
4.2.2.1 - Layer 3
4.2.2.2 - Layer 3
4.2.2.3 - Layer 3
8.8.8.8 - Google
8.8.4.4 - Google
208.67.222.222 - OpenDNS
208.67.220.220 - OpenDNS
add a comment |
Some free DNS servers you can use for forwarding:
1.1.1.1 - Cloudflare
4.2.2.1 - Layer 3
4.2.2.2 - Layer 3
4.2.2.3 - Layer 3
8.8.8.8 - Google
8.8.4.4 - Google
208.67.222.222 - OpenDNS
208.67.220.220 - OpenDNS
add a comment |
Some free DNS servers you can use for forwarding:
1.1.1.1 - Cloudflare
4.2.2.1 - Layer 3
4.2.2.2 - Layer 3
4.2.2.3 - Layer 3
8.8.8.8 - Google
8.8.4.4 - Google
208.67.222.222 - OpenDNS
208.67.220.220 - OpenDNS
Some free DNS servers you can use for forwarding:
1.1.1.1 - Cloudflare
4.2.2.1 - Layer 3
4.2.2.2 - Layer 3
4.2.2.3 - Layer 3
8.8.8.8 - Google
8.8.4.4 - Google
208.67.222.222 - OpenDNS
208.67.220.220 - OpenDNS
edited Dec 5 at 22:23
zx485
708513
708513
answered Dec 5 at 21:08
JCA122204
112
112
add a comment |
add a comment |
If you download the DNS benchmark program from link text, it will benchmark a list of public DNS servers as well as your local DNS server. After running this program, try putting a copy of the fastest servers into the DNS setting on your router and then renew your DHCP session and running the test again.
If your router allows it, add both the router and one of the fast external DNS servers to the list of DNS servers that it hands to DHCP client (but pick a different one from the one that you entered for the router DNS server addresses).
add a comment |
If you download the DNS benchmark program from link text, it will benchmark a list of public DNS servers as well as your local DNS server. After running this program, try putting a copy of the fastest servers into the DNS setting on your router and then renew your DHCP session and running the test again.
If your router allows it, add both the router and one of the fast external DNS servers to the list of DNS servers that it hands to DHCP client (but pick a different one from the one that you entered for the router DNS server addresses).
add a comment |
If you download the DNS benchmark program from link text, it will benchmark a list of public DNS servers as well as your local DNS server. After running this program, try putting a copy of the fastest servers into the DNS setting on your router and then renew your DHCP session and running the test again.
If your router allows it, add both the router and one of the fast external DNS servers to the list of DNS servers that it hands to DHCP client (but pick a different one from the one that you entered for the router DNS server addresses).
If you download the DNS benchmark program from link text, it will benchmark a list of public DNS servers as well as your local DNS server. After running this program, try putting a copy of the fastest servers into the DNS setting on your router and then renew your DHCP session and running the test again.
If your router allows it, add both the router and one of the fast external DNS servers to the list of DNS servers that it hands to DHCP client (but pick a different one from the one that you entered for the router DNS server addresses).
answered Mar 3 '10 at 3:22
Walter
41637
41637
add a comment |
add a comment |
I had a similar problem. I bought an OpenWRT compatible router and installed OpenWRT. It offers static IP binding along with name resolution in the router, which enabled me to give names to my computers and devices in the network as I wish.
add a comment |
I had a similar problem. I bought an OpenWRT compatible router and installed OpenWRT. It offers static IP binding along with name resolution in the router, which enabled me to give names to my computers and devices in the network as I wish.
add a comment |
I had a similar problem. I bought an OpenWRT compatible router and installed OpenWRT. It offers static IP binding along with name resolution in the router, which enabled me to give names to my computers and devices in the network as I wish.
I had a similar problem. I bought an OpenWRT compatible router and installed OpenWRT. It offers static IP binding along with name resolution in the router, which enabled me to give names to my computers and devices in the network as I wish.
answered Apr 27 at 20:55
Guy
1
1
add a comment |
add a comment |
Maybe I'm saying something stupid.
In this case I would simply add IP and names to the hosts files on the individual machines..
192.168.0.120 tv.local
192.168.0.80 studiopc.local
add a comment |
Maybe I'm saying something stupid.
In this case I would simply add IP and names to the hosts files on the individual machines..
192.168.0.120 tv.local
192.168.0.80 studiopc.local
add a comment |
Maybe I'm saying something stupid.
In this case I would simply add IP and names to the hosts files on the individual machines..
192.168.0.120 tv.local
192.168.0.80 studiopc.local
Maybe I'm saying something stupid.
In this case I would simply add IP and names to the hosts files on the individual machines..
192.168.0.120 tv.local
192.168.0.80 studiopc.local
answered Oct 6 '17 at 10:53
Stefano
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f45789%2frunning-dns-locally-for-home-network%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
There are at least 2 questions here: Local DNS config, public DNS servers. Post 2 questions next time.
– hyperslug
Sep 23 '09 at 19:09
16
I agree, but i'm looking for an overall solution. each question on it's own would have a correct answer, but may not mesh, i'm trying to look for solution to both problems that works together.
– Roy Rico
Sep 23 '09 at 20:51
@RoyRico Did you ever find a good solution? I am trying to do the exat same thing witha Tomato router and am running into walls at every direction.
– Jeff
Dec 15 '12 at 3:04
If you have a linux box, here is how to setup DNSMASq in details -- sfxpt.wordpress.com/2011/02/06/…
– xpt
Jun 15 '14 at 23:29
The new Google DNS servers are 8.8.8.8 and 8.8.4.4 in case anyone was wondering...
– Tmanok
Feb 13 at 21:03