Re: DNS Name Server with one IP address
From: Dan (dan_at_dontspammecauseidontlikit.com)
Date: 01/23/04
- Next message: Ben B: "100 packets/sec outgoing traffic for each socket"
- Previous message: alvin: "Re: MSN Messenger Behind a NATting IPtables Firewall"
- In reply to: Ivan: "DNS Name Server with one IP address"
- Next in thread: Ivan: "Re: DNS Name Server with one IP address"
- Reply: Ivan: "Re: DNS Name Server with one IP address"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 23 Jan 2004 09:41:31 GMT
On 21 Jan 2004 13:40:56 -0800, ivanfernandes@flashmail.com (Ivan)
wrote:
I agree with Ben, I don't think you need your own name server, anyone
can do this for you. I'll do my best to explain what I think you
need.
Your name server is the computer that has the public ip addresses for
your network. From what you've said, you only have one public ip
address, the ip address of your Linux box gateway. This makes things
fairly simple The name server can be anywhere, it doesn't have to be
on your Linux box, in fact it's probably easier if it isn't. Your
name server is the one that other dns servers come to in order to get
your ip address.
This is basically what happens when a domain name is resolved in say,
your web browser, (the simplified explanation). The browser will ask
a local dns server for the ip address. That server will 'ask around',
other name servers and will find out where the 'authoritive' name
server is. The authoritive name server has the ip address for the
name and this will get relayed back to the web browser( or email
client or whatever ).
So what you have to do is determine who you want to be your
authoritive name server, and then configure that name server so that
it has the public ip address of your network And then you have to let
all the other name servers on the internet know where the authoritive
name server for your domain is. It's actually a lot simpler than it
might sound.
The hard way will probably be to use your own network gateway Linux
box as your name server. I use a free name server at
www.zoneedit.com. It's free if you have less than five domain names
and your traffic isn't huge. And even if you have a lot of traffic,
it's still cheap. There are others as well, but this is the one I've
had experience with. You set up an account with them and configure it
with your domain name. Then you configure the domain name with the
public ip address of your network. Very easy, can be done with a web
browser in a few minutes. Now it knows the ip address of your network
and can tell other name servers what it is. One of the advantages of
using them is that they have diesel generators as a backup in case of
a power failure, and a secondary name server on a different network
altogether. So you're name server isn't likely to be down.
Now you have to let name servers on the internet know where your
authoritive name server is. When you created the account with
zoneedit, they tell you what the addresses of the their (your) name
servers are( primary and secondary). It will be something like
ns1.zoneedit.com and ns2.zoneedit.com. These are the name servers
that are authorative for your domain name. Now you go back to your
domain name registrar, the place where you registered the name, and
tell them these two addresses. Some of them let you do this via web
configuration, you go to the place where it says primary and secondary
name servers, and you put in the addresses that were given to you.
You should at least be able to do this via email. The name of your
authoritive name server propogates from the registrar through to the
rest of the name servers on the internet, or at least to the root
ones. This is where the delay comes in. This will take somewhere
between 24 to 72 hours before it's finally done, but once that's
completed you're set.
You can run your different services, like web and mail servers, on the
one computer, or you can put them on different machines on your
network. All of the request for your domain name will come to the
gateway machine. The services can be running there, or the gateway
can forward them to another computer.
You might want to run a caching name server on your network to speed
up access to external sites, or you might want a name server local to
your network to resolve names for the computers on your network, but
this is a different story.
Dan
dan_nelson123>>>>>>>hotmail>>>>>com
>Hi all,
>
>Scenario:-
>Linsys Router
>External IP (xxx.xx.xx.xx)
>Internal IP (192.168.1.1)
>
>Router DMZ on and points to Linux box (192.168.1.10)
>
>Linux Box (192.168.1.10)
>
>Now I have a domain name www.mydomain.com registered with a registrar
>(Currently uses their dummy name servers need to supply my own)
>
>1) I cannot ask my ISP for this service or the registrar due to $$
>2) I would like to use run my own name server for flexibility (i will
>find a secondary nameserver)
>3) I have tried free name server providers (but the refresh times are
>too long >24hr)
>
>How do I set up so when a user points to www.mydomain.com so it
>resolves to my Static IP address (xx.xx.xx.xx)?
>My primary dns/www/mail server will all be on one machine
>(192.168.1.10), is this configuration possible for an individual with
>one IP address? If so how?
>Please brief me on the DNS named and zone files as to what IP address
>they should contain (local 192.168.1.10 or external (xx.xx.xx.xx)).
>
>All suggestions welcome however wish your answer can be detailed as I
>am now worn out....
>
>p.s. I have gone through a lot of postings but not come across with my
>setup above.(I could eliminate the router in between and configure
>Linux as the router)
- Next message: Ben B: "100 packets/sec outgoing traffic for each socket"
- Previous message: alvin: "Re: MSN Messenger Behind a NATting IPtables Firewall"
- In reply to: Ivan: "DNS Name Server with one IP address"
- Next in thread: Ivan: "Re: DNS Name Server with one IP address"
- Reply: Ivan: "Re: DNS Name Server with one IP address"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
