First Dns Setup

[iphonogasm]

Hi, so this is also my first DNS setup, but i know nothing about DNS, i dont know how it works or what its for HAHA!

 

all i know is its something to do with the internet, correct. Very new to this and keen to learn..

 

had a play around with setting one up but as you could immagine didnt get far,

 

I guess my question right now is how exactly does it work and what exactly is it for, and maybe do i need one

 

What lead me to setting up DNS was the fact that i have a DHCP server configured and i want the DHCP server to issue the DNS of the server not the router, eg, the DHCP server is 192.168.0.2 and so i want a DHCP lease to be

 

IP: 192.168.0.xxx

Gateway: 192.168.0.2

DNS: 192.168.0.2

 

this is just to keep things tidy, so its all controlled by the server, and not some things pointing to the router and some to the server!

 

so do i require DNS to be setup?

 

 

Thanks heaps!!

[ICTCity]

Hi,

 

DNS RESOLVES name to IP and vice versa. if you try to ping www.google.com you receive this message:

Pinging [url="http://www.l.google.com"]www.l.google.com[/url] [74.125.39.99] with 32 bytes of data:
Reply from 74.125.39.99: bytes=32 time=30ms TTL=53

 

Can you see the IP?

Internet works with IPs not with names, but for us (people) it's easier to remember name instead of numbers, right?

 

There are 13 ROOTs DNS server which are there to answer the questions. How it's made a question? Easy:

 

Let's say you want to navigate to www.serverforum.org. PLEASE NOT THE DOT AT THE END!

 

The query is splitted:

www

windows2008forum

com

.

 

Starting from the right or from the bottom, you have .[dot] this is managed by ROOT DOMAINS NAME SERVERS. They look at the next part: COM and they say: HEY, I know WHO is responsible for COM domains, let's forward the query to WHO MANAGES "COM" domains. So, the manager of COM domains check the next part WINDOWS2008FORUM and says: "Hey, I have something which is called WINDOWS2008FORUM" and it forwards the request again. Finally the WWW HOST is searched and... FOUND! So, you have the main page of your site!

 

What a DNS server does is to resolve name on ip and vice versa.

 

Fist of all you must configure a DNS service on your service, once ready, change DHCP options to point on another DNS server. Actually if you don't need specials configurations (like AD or web site hosting), you router is doing the right job, so you don't need another server.

 

There are many other possibilities, like virtual hosting, aliases, records, trees and so on, but basically this is what you need to start with DNS server which is not really the easier thing in a network. Many problems with AD are caused by misconfigured DNS.

[iphonogasm]

Hi,

 

DNS RESOLVES name to IP and vice versa. if you try to ping www.google.com you receive this message:

Pinging [url="http://www.l.google.com"]www.l.google.com[/url] [74.125.39.99] with 32 bytes of data:
Reply from 74.125.39.99: bytes=32 time=30ms TTL=53

 

Can you see the IP?

Internet works with IPs not with names, but for us (people) it's easier to remember name instead of numbers, right?

 

There are 13 ROOTs DNS server which are there to answer the questions. How it's made a question? Easy:

 

Let's say you want to navigate to www.serverforum.org. PLEASE NOT THE DOT AT THE END!

 

The query is splitted:

www

windows2008forum

com

.

 

Starting from the right or from the bottom, you have .[dot] this is managed by ROOT DOMAINS NAME SERVERS. They look at the next part: COM and they say: HEY, I know WHO is responsible for COM domains, let's forward the query to WHO MANAGES "COM" domains. So, the manager of COM domains check the next part WINDOWS2008FORUM and says: "Hey, I have something which is called WINDOWS2008FORUM" and it forwards the request again. Finally the WWW HOST is searched and... FOUND! So, you have the main page of your site!

 

What a DNS server does is to resolve name on ip and vice versa.

 

Fist of all you must configure a DNS service on your service, once ready, change DHCP options to point on another DNS server. Actually if you don't need specials configurations (like AD or web site hosting), you router is doing the right job, so you don't need another server.

 

There are many other possibilities, like virtual hosting, aliases, records, trees and so on, but basically this is what you need to start with DNS server which is not really the easier thing in a network. Many problems with AD are caused by misconfigured DNS.

 

So reading a bit further, i can do away with my router if i setup DNS?

 

Thanks

[ICTCity]

Yes, you can disable DNS on your router... but it doesn't matter, because if you set the clients to point on your server, they will never know anything about your router :)