Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Saturday, February 25, 2012 7:54 PM
Hello All,
I am newbie and doing this for first time.
I want to create a public DNS server similar to Googles 8.8.8.8 DNS server and want to accomplish this in Windows Server 2008.
I know the steps of configuring DNS server on windows 2008 server, but how i will make it PUBLIC mean how would I set the server to pickup records from other domain’s across the world. Just like i use my ISP DNS server right now .
So you can suppose i want to configure a server as an ISP , so my client can use it for internet.
Regards,
All replies (6)
Saturday, February 25, 2012 10:47 PM
Do you have DNS installed on this server? Simply set DNS to forward to 8.8.8.8 or 4.2.2.2 or whatever. The local DNS will do the lookup un behalf of the client.
http://technet.microsoft.com/en-us/library/cc754941.aspx
Bill
Sunday, February 26, 2012 9:06 AM
Hello All,
Thanks Bill for your reply .
Is it possible to resolve queries for domains it is not authoritive for. Probably using its root hints not forwarders ??
I mean an independent Public Dns server rather than forwarders ..
Regards,
Sunday, February 26, 2012 6:35 PM
Hi.
If you dont have any forwarders at all, Windows DNS server will resolve using root hints. The root hints contains IP of root servers.
Your client asks the server
The server asks the root servers for which DNS servers are authorative for the TLD (com,net,org, ..)
The server now asks the DNS servers responsible for that TLD for servers which knows about the domain.tld your are interested in.
And it continutes like that.
Oscar Virot
Monday, February 27, 2012 6:11 AM | 4 votes
Heeena,
Here are my notes on this. It's been discussed before, which you will find links to below.
==================================================================
Host your own DNS server on the internet
Technet Thread: [Host own DNS] "How to configure DNS server to route a domain name to an ip address" 11/1/2011
http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/64d0b0eb-620a-4b82-9fbe-dbeeaf5c2ada/
.
First, the Registrar requires you to have two DNS servers, one for NS1.example.com, and one for NS2.example.com.
Second, to port remap/translate UDP 53 and TCP 53, as Tiger indicated, you will need two WAN IP addresses from your ISP.
Third, these two DNS servers cannot be hosting your Active Directory infrastructures or cannot contain private internal IP addresses.
Fourth, you will need to make sure that your two DNS servers are up and running 24/7 with 99.9999% uptime, otherwise if they go down, your public resources will not be available
Fifth, you need a business class ISP line. A residential line won't work.
FYI, It's usually much easier to just allow your registrar to host your public DNS requirements. The registrar has numerous DNS servers and offer 99.9999% uptime. I can see if you are hosting multiple zones, such as 20 or more, and purchase the equipment and additional ISP services to support it, but if you are just doing this for one public domain name, it's really not worth the time and money to do this.
I used to run two public DNS servers at my home office years ago handling over 50 domain names, but to save electricity, ISP line costs ( had a T1 line about 10 years ago), backup solutions, etc, it was much easier I've found to simply allow my registrar to host all the zone. I retired my two DNS servers, sold them, reduced my ISP line requirements, and saved about $700/mo between ISP and electrical costs.
More info:
Since we are going to allow remote users where form internet could be able to access our internal resources with a internet domain name then we have to first register our internet valid domain in order to make our internet address could be resolved by all internet DNS servers:
Creating an Internet DNS Domain Name
http://technet.microsoft.com/en-us/library/cc787342(WS.10).aspx
Getting a Domain Name
http://www.itgeared.com/articles/1217-getting-domain-name/
If we are going to host our internet domain by our own DNS server at internal network then we should modify the SOA and NS record of our internet domain to point to the internet address we own and publish this DNS server to internet on NAT by setting port mapping.
Hosting DNS Servers for Your Domain
http://www.itgeared.com/articles/1218-hosting-dns-servers-for-your-domain/
If we are using RRAS as NAT device then we can get the method on how to configure port mapping for publishing form the article below:
Configuring Access to Services Behind a Network Address Translator (NAT)
http://technet.microsoft.com/en-us/library/bb878046.aspx
==================================================================
.
Ace
.
Ace Fekay
MVP, MCT, MCITP Enterprise Administrator, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
This posting is provided AS-IS with no warranties or guarantees and confers no rights.
Thursday, October 1, 2015 8:26 PM
Thanks Ace, very good explanation
Friday, October 2, 2015 2:28 AM
Thanks Ace, very good explanation
I'm happy you found it helpful. :-)
Ace Fekay
MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
This posting is provided AS-IS with no warranties or guarantees and confers no rights.