Prev: permissions on a share
Next: windows server 2008 wbadmin not remove old backup
From: PorBar on 13 May 2010 15:56
On May 13, 10:43 am, "Danny Sanders" <dsand...(a)NOSPAMbrakesplus.com>
wrote:
> >On the Server:
> >IP: 10.10.10.160
> Sub: 255.255.255.0
> >Gateway: 10.10.10.170  (Router)
> >Primary DNS: 10.10.10.160  (I have also seen people use 127.0.0.1)
>
> Do not use 127.0.0.1 that leads to a whole other set of problems.
>
> >On the Clients:
> >IP: Obtain automatically
> >DNS: 10.10.10.160     (I have seen it manually added like this, but I
> >thought the Server should handle it?)
> >Do these settings look correct to you for a Server providing both DNS
> >& DHCP?
>
> I would have the DHCP server hand out the DNS info. makes it easier if you
> ever have to change your DNS server.
>
> hth
> DDS
>
> "PorBar" <compsos...(a)gmail.com> wrote in message
>
> news:96eece58-2c57-4343-9a16-c27f18007439(a)o14g2000yqb.googlegroups.com...
> On May 13, 6:43 am, Leythos <spam999f...(a)rrohio.com> wrote:
>
>
>
>
>
> > In article <c3635d04-505b-4869-bd6e-4e5566acd354
> > @k2g2000yqe.googlegroups.com>, compsos...(a)gmail.com says...
>
> > > On May 12, 6:39 pm, Leythos <spam999f...(a)rrohio.com> wrote:
> > > > In article <80b49491-44e5-4aad-bd37-e82602216175
> > > > @e1g2000yqe.googlegroups.com>, compsos...(a)gmail.com says...
>
> > > > > On May 12, 4:33 pm, "Danny Sanders" <dsand...(a)NOSPAMbrakesplus.com>
> > > > > wrote:
> > > > > > Use Windows for DHCP and DNS.
>
> > > > > > hth
> > > > > > DDS
>
> > > > > > "PorBar" <compsos...(a)gmail.com> wrote in message
>
> > > > > >news:c583023f-c48e-4aeb-8b02-2c3d037fa1c3(a)h9g2000yqm.googlegroups.com...
>
> > > > > > > We are setting up a network that currently uses WindowsNT Server
> > > > > > > (yes,
> > > > > > > you read that correctly). We are going to use Windows 2008 R2
> > > > > > > Standard. This network only has 6 clients. Should we use the
> > > > > > > router as
> > > > > > > the DHCP server or should we use the Server for both DNS and
> > > > > > > DHCP?
>
> > > > > > > The clients are XP Pro and WIndows7
>
> > > > > > > Thanks
>
> > > > > I thought if the Server is a Domain Controller with Active Directory
> > > > > &
> > > > > DNS, it is best to use the router for DHCP?
>
> > > > NEVER, the DHCP, if properly configured on the server, will provide
> > > > data
> > > > that your router won't provide to the workstations.
>
> > > > Since you're doing a domain, it's not too late to consider SBS 2008
> > > > instead of Server 2008 standard.
>
> > > The Server has already been purchased with 2008 Server. I was thinking
> > > if the Server went down, they could still use the Internet if the
> > > router was handling DHCP. Their primary business requires the Internet
> > > more than any files on the Server.
>
> > If you put the router first or even second, or at all, you will have
> > problems with authentication at some point, it always happens. If the
> > server is not reliable then consider a different server - I have servers
> > that have more than 1 full year of up-time on them.
>
> > --
> > You can't trust your best friends, your five senses, only the little
> > voice inside you that most civilians don't even hear -- Listen to that.
> > Trust yourself.
> > spam999f...(a)rrohio.com (remove 999 for proper email address)
>
> The Server is brand new (still in the box) so I guess it is as
> reliable as most at this point. So what is the best way to configure
> the network IPs, etc? I will give the Server a static IP, eg.
> (10.10.10.160) and the router (10.10.10.170). It would look like this:
>
> On the Server:
>
> IP: 10.10.10.160
> Sub: 255.255.255.0
> Gateway: 10.10.10.170  (Router)
> Primary DNS: 10.10.10.160  (I have also seen people use 127.0.0.1)
>
> On the Clients:
>
> IP: Obtain automatically
> DNS: 10.10.10.160     (I have seen it manually added like this, but I
> thought the Server should handle it?)
>
> Do these settings look correct to you for a Server providing both DNS
> & DHCP?- Hide quoted text -
>
> - Show quoted text -

Where do I put the DNS information from my ISP-? Or does the Server
get this from the fact that the router is the gateway. We do not have
a StaticIP from our ISP -- I am used to putting that int he router
along with the ISP's DNS server information.
From: Danny Sanders on 13 May 2010 16:29
>>Where do I put the DNS information from my ISP-? Or does the Server
<<get this from the fact that the router is the gateway. We do not have
>>a StaticIP from our ISP -- I am used to putting that int he router
>>along with the ISP's DNS server information.


With an AD domain all AD clients must point to the DNS server setup for the
AD domain ONLY. Don't use your ISP's DNS server on any of your AD clients
(servers are AD clients also). The only exception is when you use your ISP's
DNS server as a forwarder for your AD DNS server. If your router has your
ISP's DNS server setup on it you can use the router's IP as the forwarder.
If not you can use your ISP's DNS servers as the forwarder.

hth
DDS




"PorBar" <compsosinc(a)gmail.com> wrote in message
news:67393df7-e348-47ab-964b-162e132dfe70(a)i10g2000yqh.googlegroups.com...
On May 13, 10:43 am, "Danny Sanders" <dsand...(a)NOSPAMbrakesplus.com>
wrote:
> >On the Server:
> >IP: 10.10.10.160
> Sub: 255.255.255.0
> >Gateway: 10.10.10.170 (Router)
> >Primary DNS: 10.10.10.160 (I have also seen people use 127.0.0.1)
>
> Do not use 127.0.0.1 that leads to a whole other set of problems.
>
> >On the Clients:
> >IP: Obtain automatically
> >DNS: 10.10.10.160 (I have seen it manually added like this, but I
> >thought the Server should handle it?)
> >Do these settings look correct to you for a Server providing both DNS
> >& DHCP?
>
> I would have the DHCP server hand out the DNS info. makes it easier if you
> ever have to change your DNS server.
>
> hth
> DDS
>
> "PorBar" <compsos...(a)gmail.com> wrote in message
>
> news:96eece58-2c57-4343-9a16-c27f18007439(a)o14g2000yqb.googlegroups.com...
> On May 13, 6:43 am, Leythos <spam999f...(a)rrohio.com> wrote:
>
>
>
>
>
> > In article <c3635d04-505b-4869-bd6e-4e5566acd354
> > @k2g2000yqe.googlegroups.com>, compsos...(a)gmail.com says...
>
> > > On May 12, 6:39 pm, Leythos <spam999f...(a)rrohio.com> wrote:
> > > > In article <80b49491-44e5-4aad-bd37-e82602216175
> > > > @e1g2000yqe.googlegroups.com>, compsos...(a)gmail.com says...
>
> > > > > On May 12, 4:33 pm, "Danny Sanders"
> > > > > <dsand...(a)NOSPAMbrakesplus.com>
> > > > > wrote:
> > > > > > Use Windows for DHCP and DNS.
>
> > > > > > hth
> > > > > > DDS
>
> > > > > > "PorBar" <compsos...(a)gmail.com> wrote in message
>
> > > > > >news:c583023f-c48e-4aeb-8b02-2c3d037fa1c3(a)h9g2000yqm.googlegroups.com...
>
> > > > > > > We are setting up a network that currently uses WindowsNT
> > > > > > > Server
> > > > > > > (yes,
> > > > > > > you read that correctly). We are going to use Windows 2008 R2
> > > > > > > Standard. This network only has 6 clients. Should we use the
> > > > > > > router as
> > > > > > > the DHCP server or should we use the Server for both DNS and
> > > > > > > DHCP?
>
> > > > > > > The clients are XP Pro and WIndows7
>
> > > > > > > Thanks
>
> > > > > I thought if the Server is a Domain Controller with Active
> > > > > Directory
> > > > > &
> > > > > DNS, it is best to use the router for DHCP?
>
> > > > NEVER, the DHCP, if properly configured on the server, will provide
> > > > data
> > > > that your router won't provide to the workstations.
>
> > > > Since you're doing a domain, it's not too late to consider SBS 2008
> > > > instead of Server 2008 standard.
>
> > > The Server has already been purchased with 2008 Server. I was thinking
> > > if the Server went down, they could still use the Internet if the
> > > router was handling DHCP. Their primary business requires the Internet
> > > more than any files on the Server.
>
> > If you put the router first or even second, or at all, you will have
> > problems with authentication at some point, it always happens. If the
> > server is not reliable then consider a different server - I have servers
> > that have more than 1 full year of up-time on them.
>
> > --
> > You can't trust your best friends, your five senses, only the little
> > voice inside you that most civilians don't even hear -- Listen to that.
> > Trust yourself.
> > spam999f...(a)rrohio.com (remove 999 for proper email address)
>
> The Server is brand new (still in the box) so I guess it is as
> reliable as most at this point. So what is the best way to configure
> the network IPs, etc? I will give the Server a static IP, eg.
> (10.10.10.160) and the router (10.10.10.170). It would look like this:
>
> On the Server:
>
> IP: 10.10.10.160
> Sub: 255.255.255.0
> Gateway: 10.10.10.170 (Router)
> Primary DNS: 10.10.10.160 (I have also seen people use 127.0.0.1)
>
> On the Clients:
>
> IP: Obtain automatically
> DNS: 10.10.10.160 (I have seen it manually added like this, but I
> thought the Server should handle it?)
>
> Do these settings look correct to you for a Server providing both DNS
> & DHCP?- Hide quoted text -
>
> - Show quoted text -

Where do I put the DNS information from my ISP-? Or does the Server
get this from the fact that the router is the gateway. We do not have
a StaticIP from our ISP -- I am used to putting that int he router
along with the ISP's DNS server information.


From: Leythos on 13 May 2010 16:58
In article <67393df7-e348-47ab-964b-162e132dfe70
@i10g2000yqh.googlegroups.com>, compsosinc(a)gmail.com says...
>
> Where do I put the DNS information from my ISP-? Or does the Server
> get this from the fact that the router is the gateway. We do not have
> a StaticIP from our ISP -- I am used to putting that int he router
> along with the ISP's DNS server information.
>

The router ROUTES your traffic from the LAN to the WAN, so the server
doesn't really need to know your public IP information, but the ROUTER
does.

You could use the ISP's DNS in "Forwarders" if you wanted.

If you don't have a Static IP are you sure that your ISP allows you to
have a server connected, most don't.

--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
spam999free(a)rrohio.com (remove 999 for proper email address)
From: Bill Grant on 13 May 2010 19:39


Let me try to summarize what is required and why.

Active directory relies on DNS. Your local DNS enables clients to access
domain resources. No other DNS server has this information. For this reason
your AD clients should use the local DNS only.

Clients do need to be able to resolve foreign URLs as well as AD
resources. For this to happen, your local DNS needs to be configured to
forward these non-local requests to a public DNS server. You could use your
ISP's DNS for this, or you could use a public DNS service like 4.2.2.2

127.0.0.1 is the loopback address of a machine. It is the DNS address of
localhost, if you like. You could use that as the DNS address on the server
itself (since it hosts your local DNS), but it is less confusing if you use
the DC's LAN IP as the DNS address, just as you do for clients.

In brief, all machines use the local DNS server. If the target is local,
it answers the request itself. If it is not, it forwards the request to a
public DNS server and relays the reply to the requesting client.

Yes, the clients will not be able to access the Internet if the DC is
down. If the DC goes down, Internet access will be the least of your
problems!


From: Dave Warren on 13 May 2010 21:32
In message <uR#CCWv8KHA.1892(a)TK2MSFTNGP05.phx.gbl> "Bill Grant"
<not.available(a)online> was claimed to have wrote:

> 127.0.0.1 is the loopback address of a machine. It is the DNS address of
>localhost, if you like. You could use that as the DNS address on the server
>itself (since it hosts your local DNS), but it is less confusing if you use
>the DC's LAN IP as the DNS address, just as you do for clients.

Isn't there also some potential issues with self-registration if you use
127.0.0.1?

Admittedly I might be thinking of W2K issues that might not apply in the
modern world, but I'm sure I recall changing from 127.0.0.1 to the
locally assigned IP for technical reasons rather than just clarity.
First  |  Prev  | 
Pages: 1 2 3
Prev: permissions on a share
Next: windows server 2008 wbadmin not remove old backup