How to configure a public dns server onsite

Posted on 2006-05-27
Last Modified: 2008-03-17
Client has two websites i.e and [ both hosted on ISP .When users try to connect to the websites from internet, they find connection is very slow.
Hence the client was advised by ISP to change the extension .ae to .com [ which will be done by ISP itself].
and to move the dns server from ISP to their own inhouse public dns server.
HOw can we setup the inhouse public dns server onsite.
please help !!!!!!
Question by:indiansandy
    LVL 32

    Expert Comment

    I would get a different ISP.  Their connection and DNS services should be MUCH better than anything you can do in-house unless you are an ISP yourself.

    I do not recommend this course of action for anything but a "hobby" web site.  If your client is in business and this web site is related to that, get a BUSINESS ISP.  I use and recommend  They are rock solid, have low tolerance for SPAMMERS (which means their email servers don't get blacklisted often), their support is 1st rate (i.e. you can call anytime day or night and talk to a tech within minutes), and their prices reasonable.

    I've also used 1&1 ( and have found their servers are good and their prices excellent but their support is lacking.  If you don't need much support, then they can be a good choice.  I have a client who's been with them for 2 years on a dedicated Windows Server and the server and network have been excellent.
    LVL 3

    Expert Comment


    This link has all the details you need.

    Do you have the DNS server installed on you server?

    If yes just add a static statment about the two web sites matching their ip addreses with their domains. Go the properties tab of the DNS server and on the tab forwarders put the DNS servers of your ISP . Then on your client pc put as a DNS server the local ip of you local private DNS server.I don't think you will have any details if you do that.

    If no install the DNS server and do as above.

    I don't think you need a puplic DNS server for just two web sites but if you insist you can find instructions about setting up a public DNS server in that link.

    I hope that all these will be usefull

    Author Comment

    Thanks for your help but it doesnt answer my queries.
    Let me make my queries simpler
    1) How to add and to the dns server[This dns server is now public server onsite]. I have basic idea about configuring a internal dns server but please note that these two websites and are public domains . What are the records to be created ?
    2) How will the name resolution occur when a client wants to connect to and
    Earlier since these websites were hosted by isp , isp used to do name resolution . But now what should i do to make sure that clients get proper name resolution? should i inform the isp to add something in their dns server ?
    3) I have 2 mbps dedicated link for the dns server , is it ok for the the new public dns server onsite?
    4) seems interesting , but i want my public dns server completely onsite. How do i do that ?
    Please help !!!!!
    LVL 10

    Accepted Solution

    1) You should keep your public DNS server seperate from your internal DNS server. If these are websites, you will create Host A records for and with www, i.e. to point to IP Address.

    2) You need to update DNS records with Service that registered the domain. For example if domain was purchased through the Network Solution, login to your account for and update the DNS server for to your Onsite DNS server. The name resolution starts with root servers, the root servers in turn give the DNS server which hosts a particular record for domain, in your case they are sending clients to your ISPs DNS server, when you update the information with your registrar, they will point to your Onsite DNS server. Your ISP will be able to help you with that change of records.

    3) Depends on traffic, it should be OK for normal activity as your DNS server will only be inquired for abc1 and, if you are getting few hundred or more hits on your website every hour, you may have issues.

    4) Assuming you are planning to use Microsoft windows, if you have configured your internal DNS, it should not be very difficult, the concept is same, you will create two primary zones in your DNS, one for and one for Very basic steps are listed here:
    LVL 32

    Assisted Solution

    >>but i want my public dns server completely onsite

    Once again I will advise you NOT to do this.   It makes your web site completely vulnerable to either system failure, power failure, networking failure at your location.  A hosted server should be in a datacenter with those problems greatly reduced.
    LVL 3

    Assisted Solution

    look at this link if you want to host a real public "HOST" for DNS resolution

    Note that you must first have your ISP setup PTR records for those hosts.  
    Typically, ISPs won't set up PTR records listing domains for which they are not authoritative, unless you buy a block of IPs.

    Real Public DNS servers are no joke, if you lose your IP, you're screwed.  
    In any event, the reason for the lag is probably the .ae TLD, so just changing over to a .com TLD will probably fix any latency in DNS resolution.

    There are lots of possible causes for seemingly slow-to-resolve/connect websites, change things one step at a time and give each a few days to judge the effect.
    LVL 44

    Assisted Solution

    "How to add and to the dns server[This dns server is now public server onsite]. I have basic idea about configuring a internal dns server but please note that these two websites and are public domains . What are the records to be created ?"

    NO NO, you dont want to do this.  You send ALL clients out to the internet to get these .COM addresses, if you have them routed on the internal network, that is a serious mistake, they MUSt go through the internet to find them.  So NO DNS routing for these sites at all, that is the only correct way to do it.

    Featured Post

    6 Surprising Benefits of Threat Intelligence

    All sorts of threat intelligence is available on the web. Intelligence you can learn from, and use to anticipate and prepare for future attacks.

    Join & Write a Comment

    I wrote this article to explain some important DNS concepts that should be known to avoid some typical configuration errors I often see in forums. I assume that what is described here is the typical behavior of Microsoft DNS client. I don't know …
    If you're not part of the solution, you're part of the problem.   Tips on how to secure IoT devices, even the dumbest ones, so they can't be used as part of a DDoS botnet.  Use PRTG Network Monitor as one of the building blocks, to detect unusual…
    After creating this article (, I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
    Here's a very brief overview of the methods PRTG Network Monitor ( offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…

    728 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    15 Experts available now in Live!

    Get 1:1 Help Now