fowaders

  • Thread starter Thread starter Chris Harries
  • Start date Start date
C

Chris Harries

I am trying to add my 2 ISP fowaders to the DNS dowaders section. So i
have added 62.30.112.39 and 62.30.0.39 but as i have

Server (192.168.0.7) -> Router (192.168.0.1) -> ISP

do i need to have a fowader of 192.168.0.1 as it needs to go though my
router to set to the ISP or do it not as the computer is set to run
though the router to connect to the internet?

Regards
Chris
 
In
Chris Harries said:
I am trying to add my 2 ISP fowaders to the DNS dowaders section. So i
have added 62.30.112.39 and 62.30.0.39 but as i have

Server (192.168.0.7) -> Router (192.168.0.1) -> ISP

do i need to have a fowader of 192.168.0.1 as it needs to go though my
router to set to the ISP or do it not as the computer is set to run
though the router to connect to the internet?

Regards
Chris
Click to expand...

No. Your network configuration will handle the traffic. Just point all your
machines to 192.168.0.7 for DNS. The forwarders will forward Internet name
queries to your ISP's directly and receive the response. The router should
be kept out of the picture, since if it is offering proxying services (what
Jonathan is talking about if your router is doing that), its an extra
uneeded hop.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
In
Chris Harries said:
I am trying to add my 2 ISP fowaders to the DNS dowaders
section. So i have added 62.30.112.39 and 62.30.0.39 but
as i have

Server (192.168.0.7) -> Router (192.168.0.1) -> ISP

do i need to have a fowader of 192.168.0.1 as it needs to
go though my router to set to the ISP or do it not as the
computer is set to run though the router to connect to
the internet?
Click to expand...

You can set your router as your forwarder.
 
CH> do i need to have a fowader of 192.168.0.1

Does your router provide forwarding proxy DNS service on port 53 of that
IP address ? If not, then using it as a forwardee is definitely not
going to work.

Forward queries to the IP address(es) where you know that the forwarding
proxy DNS service *actually listens*.
 
bascially i have my server which is main server (i am trying to set up
exchange 2003) i then havea router then on to the ISP. Now i have port
53 on the router open but i dont no wether my ISP's or router's IP's go
in the 'fowaders' section of DNS properties. My main problem i am trying
to resolve is this

Testing server: Default-First-Site-Name\CHRIS
Starting test: Connectivity
CHRIS's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(6d8d62dc-6cdd-44e2-9d35-1e28f3d1fdc7._msdcs.localhost) couldn't be
resolved, the server name (chris.localhost) resolved to the IP
address
(192.168.0.7) and was pingable. Check that the IP address is
registered correctly with the DNS server.
......................... CHRIS failed test Connectivity

and i think it may have something to do with the fowaders bit

Regards
Chris
 
In
Chris Harries said:
bascially i have my server which is main server (i am trying to set up
exchange 2003) i then havea router then on to the ISP. Now i have
port 53 on the router open but i dont no wether my ISP's or router's
IP's go in the 'fowaders' section of DNS properties. My main problem
i am trying to resolve is this

Testing server: Default-First-Site-Name\CHRIS
Starting test: Connectivity
CHRIS's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(6d8d62dc-6cdd-44e2-9d35-1e28f3d1fdc7._msdcs.localhost)
couldn't be resolved, the server name (chris.localhost)
resolved to the IP
address
(192.168.0.7) and was pingable. Check that the IP address is
registered correctly with the DNS server.
......................... CHRIS failed test Connectivity

and i think it may have something to do with the fowaders bit

Regards
Chris
Click to expand...

Chris, looks like you have a single label DNS domain name. Not good at all,
unless you munged the name.

Is your domain called "localhost" and not "localhost.com" or localhost.net"
or "localhost.chris" ?

If so, this can be the cause of all your problems.


--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
So do you know how i can correct this problem. When setting it up it
says when it is its name
and is has "for example (microsoft.com) But i am setting this server up
on this server so what name do i put?

Regards
Chris
 
In Ace Fekay [MVP] <PleaseSubstituteMyActualFirstName&[email protected]>
wrote their comments
Then Kevin replied below:
In

Chris, looks like you have a single label DNS domain
name. Not good at all, unless you munged the name.

Is your domain called "localhost" and not
"localhost.com" or localhost.net" or "localhost.chris" ?

If so, this can be the cause of all your problems.
Click to expand...

A single-label domain is bad enough but if he named his domain "localhost"
that would be a much bigger problem, I would think. Imagine another client
try to contact this domain with a name like localhost. How would group
policies apply if the SYSVOL share is at \\localhost\sysvol ?
Wouldn't that be a trick since localhost always resolves to 127.0.0.1?
How could you even join a computer to the domain?

If he munged his domain name one would think of a better name more relative
to munge it with. One would think that if he did try to name the domain
localhost DCPROMO wouldn't even allow it, if it did could that be considered
a bug?
 
In
Chris Harries said:
So do you know how i can correct this problem. When setting it up it
says when it is its name
and is has "for example (microsoft.com) But i am setting this server
up on this server so what name do i put?

Regards
Chris
Click to expand...

I'm sorry, I can't seem to follow your sentence/question and don't fully
understand what you're asking.

Did you already create the AD domain? Or you are attempting to create the
domain? If during AD setup (dcpromo), that name, microsoft.com, is just an
example to use, like domain.com or domain.local.

Eitherway, don't use a single label name and please don't select localhost
as the name.

Is your actual domain name called 'localhost'? Besides being a single label
name, Kevin gave you a good example of the implications of this reserved
Windows name, unfortunately not a good name to have chosen.

From your previous posts, it looks like you do have AD setup, so if this is
the case, and needing to fix this, here are your options:

1. If this is Windows 2003, there's a rename tool (rendom.exe in the
resource kit tools).

2. If this is Windows 2000 and it's in Mixed mode, install an NT4 BDC into
the
domain, remove the Windows 2000 machine from the network. Then use the same
IP address you were using on the old machine on this machine, promote the
NT4 BDC to a PDC, then set the TCP/IP DNS suffix for eu.local, install DNS,
point to itself and create the eu.local zone, then promote the machine to a
W2k DC this time choosing the right name!

3. If this is WIndows 2000 and it's in Native mode, you can either upgrade
it
to W2003 and use the domain rename tool, or migrate it to a new Win2000
domain, or just trash this and install it from scratch.


--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
Back
Top