I would love the ability to create custom DNS records for all the machines on my network.
For example I can have test.my-domain.com point to XXX.XXX.XXX.XXX.
I am tired of editing my hosts file. :)
45 Comments
For example I can have test.my-domain.com point to XXX.XXX.XXX.XXX.
I am tired of editing my hosts file. :)
45 Comments
Who voted for this idea
- miked
- nickthephreak
- Dave
- Brian Watters
- Nathan
- ab-imports
- Chris
- gamer8519
- jeffmccann
- peterwald
- srieman
- rnebiker
- foxtyke
- g00fy
- war59312
- gpatterson
- willwill
- msimmons
- jasonward
- saltcreek
- Courtenay
- spsdns
- lordsturm
- andy460
- stemount
- Randy
- Eric Gillette
- K
- tetak
- OpenDNS User
- vader
- ricky1146
- ricmacas
- fmoses
- antlane
- t3hub3rk1tten
- tjg50311
- ddean
- Thor Marius K.H.
- codemaster2
- morriswireless
- bigluck
- sdot
- brentj84062
- asd_itoperations
- davide
- Johan
- manuelvde
- jszobody
- Atte
Comments
written by 2insite 637 days ago - show/hide this comment
Rating: -2
| Rate Comment:
+
-
Glad to read that hosts file comment; I thought I was the only one.
I would have suggested this myself, but I don't see how OpenDNS can make money offering this feature. But, I would be thankful for the feature.
The more users, the more they make off the ad revenue. The more features that make users happy, the more those happy users tell their friends about OpenDNS, the more users they get.
Simple grass-roots, word-of-mouth, referral marketing.
The appropriate method to do this is to set up a DNS server on your network. You can go from scratch to a fully configured BIND server in under an hour, and if you have an old computer lying around, the cost is nil.
"Right. Running your own DNS server (see "editing the hosts file") "
They aren't the same thing.
written by cykelsmeden 503 days ago
Rating: 2
| Rate Comment:
I believe your residenceis US ??
one average PC running bind 24-7-365 is about 200$ a year, in ie. dk - not to mention CO2
You can go one step better and configure a hardened firewall like IPCop. http://www.ipcop.org IPCOP includes an internal DNS server. Check out http://www.howtoforge.com/perfect_linux_firewall_ipcop
and
http://www.howtoforge.com/perfect_linux_firewall_ipcop_p2
pfSense (www.pfSense.org) also allows you to set custom DNS settings in the DNS Forwarder application for local-only resolution.
I like this idea, and have suggested it as a feature along with another feature which is off-site DNS failover for domains. The idea I suggested (should be showing up on the idea bank shortly, I hope) is to add the ability to create an athoritative zone on OpenDNS in my account and set public IP addresses for the records under that zone, then set private resolution to those same records for when the zone is queried from within my network(s). The openDNS name servers could be set as the name servers for that domain name and use OpenDNS as the primary or failover DNS servers.
I currently use zoneedit.com but I would prefer to use OpenDNS
That should be handled by your domain's nameservers.
written by dragon2611 468 days ago
Rating: 2
| Rate Comment:
Some Routers Will do this anyway if the router is the DNS relay.
I know ones using the DD-WRT and Tomato firmwares can resolve machines by their Hostname and also Host.domain as long as the Machine Either Provides its hostname to the router or you set one in the Static DHCP section.
written by shawnkhall 450 days ago
Rating: 4
| Rate Comment:
The problem with using hosts files is that the file has to be duplicated on each device. For a network of even a half dozen computers, this can be a huge pain. ESPECIALLY if we manage multiple sites; East and West coast locations are a little more problematic than your neighbors house, but still it's an added frustration.
The problem with using a DNS server is that it DOES add expense (maintenance/time, $, co2) in addition to being a third system to futz with. Even if I were to use a dedicated private DNS server locally (at my node), it wouldn't help any of the other sites that use my OpenDNS account for filtering, ESPECIALLY since no matter how it was setup it would slow their connection down.
And if I use a hosted name server somewhere (like one of my offsite dedicated servers), I would necessarily have to change the DNS on that to facilitate OpenDNS as a relay, which COULD affect the actual performance and business operations there (like the current "Adware" vs "advertising" miscomprehension with the users on the filtering system). Missing important email or the ability to contact these locations is not a viable option.
Which leaves us to OpenDNS. The power is already there, as it allows us to whitelist and blacklist domains irrespective of their current categorization. It would be only one more step to add fully authoritative naming EXCUSIVELY to our accounts. It would be SO much easier to manage this stuff directly from our current OpenDNS control panel, and it would give us the ability to use domains that we might not be authoritative for. For example, I use "example.com" to test various things, since it's a simple domain to work with and ONLY my staff needs access to it. Sure, I could use example.oneofmydomains.com, except it would be longer, be less memorable and inevitably interrupt the process.
When we had our own wanna-be OpenDNS before switching to OpenDNS, this was simple enough, but now, about 6 months later, I find myself still fighting with the ability to get the same simple functionality back to each of our locations - without having to dedicate the time and energy to actually go to each location and set up crap like hosts files or private DNS servers. Sigh.
As the last poster pointed out, one of the biggest benefits of this feature over a private DNS server would be to allow you to set consistent DNS aliases across multiple locations that you can manage with a single interface (the dashboard).
This would be particularly useful for me (and others probably) with my laptops, since I use them at several public sites where I have no control over the network itself.
We use our own DNS server (running on a Linux box). The suggestion to use one of a number of popular firewall solutions that include an internal DNS server is not a bad one, but wouldn't work for us and many of our clients. We have multiple domain names, and use Untangle as a firewall. It has DNS built in, but will allow DNS entries for one domain name.
It'd be great if OpenDNS allowed us to enter "private DNS entries" that allow us to forward requests for certain host names in certain domains (more than one, please) to the IP address they should. Like others have mentioned, when a laptop user is in our building, beretta.concentrico.net should point to the internal 10.x.x.x address, and when they are on the road, it should point to the external address. And having them modify a hosts file is a support nightmare. Furthermore, having them have an invalid IP address for their first DNS server (as we currently do, since it points to an internal address) mucks things up a little when they are on the road.
This is a common-sense feature. Please add it!
I've set this up for clients (so that foo.myclient.dom resolves to the internal 10.x.x.x address when looked up from the LAN, and when they are on the road, it resolves to the external address). Happy to help anyone get this 'split dns' setup working.
Actually this is the one reason I signed up! I assumed that this feature would be available. In fact, none of the existing features are enough to make me want to use the service (no offence), so I think I will be switching my DNS back to my ISP :(
shortcuts do the job,though it's not quite the BIND9
This is nothing to do with the core functionality of OpenDNS.. forget it.
written by Marius Gologan 279 days ago
Rating: 4
| Rate Comment:
Any DNS Server or even a simple computer (no matter OS) can make it, but not without human intervention. Technology is not able minded. Remember ?
this would be an excellent feature when combined with the netgear live parental controls using opendns. i currently have a problem since implementing a new netgear router. i run a domain at home, but have no easy way to configure my environment to use my internal DNS server for my home domain, yet go out to opendns for everything else - and still use the live parental controls provided as part of the netgear-opendns alliance.
i was hoping to see this perhaps appear as a "deluxe" or "enterprise" feature. i hate having to abort DNS and go back to hosts files just so I can have local name resolution and use the parental controls at the same time.
cheers, wizdude.
Sign in to comment or register here.
