DNS problem?

  • Thread starter Thread starter Gavin
  • Start date Start date
G

Gavin

Here is the problem I am having. I have a multihomed Server acting as an AD
DC, also using as VPN and Proxy. Config is as followes:

Nic1 - 192.168.1.1 DNS 192.168.1.1
Nic2 - 63.XX.XX.XX DNS 206.13.29.12 GW 63.XX.XX.XX
forwarding is setup in the DNS to point to 206.13.29.12

The problem is when I try and ping a public address it will time out. I can
ping the address on the server but not on any workstation. The workstations
can get on the internet through the proxy but does not seem to resolve any
intenet names.

Anyone have any suggestions? Is this a routing issue or DNS?

Thanks
Gavin...
 
Here is the problem I am having. I have a multihomed Server acting as an
AD
DC, also using as VPN and Proxy. Config is as followes:

Nic1 - 192.168.1.1 DNS 192.168.1.1
Nic2 - 63.XX.XX.XX DNS 206.13.29.12 GW 63.XX.XX.XX
forwarding is setup in the DNS to point to 206.13.29.12
Click to expand...

What are the Server's CLIENT settings on BOTH NICs?

You need to OVERRIDE The external NIC pointing to an external
DNS (the forward takes care of that) and either use the same OR ONLY
the Internal NIC to point to itself as DNS.
The problem is when I try and ping a public address it will time out. I can
ping the address on the server but not on any workstation.
Click to expand...

Ping from where to where? ("I can ping.." doesn't say FROM WHERE?)
The workstations
can get on the internet through the proxy but does not seem to resolve any
intenet names.
Click to expand...

What address do the workstations use for DNS (should be the DC/DNS ONLY.)
Anyone have any suggestions? Is this a routing issue or DNS?
Click to expand...

Probably. <grin>

The way you determine this is by comparing Ping by number with Ping
by Name.

Use NSLookup (or another tool like Dig) and TraceRt or PathPing to
isolate the problem.
 
Back
Top