DNS forwarding

[Bojan Zivancevic]

I have the following configuration:

- small internal namespace with private addressing, dial-up, win2k
environment, one DNS server
- DNS server has forwarders (my ISP's servers)
- clients have internal DNS server for name resolving

The problem is that sometimes this works and sometimes it doesn't. Sometimes
I have to add ISP's server to the client's server list in order to make
internet work. Shouldn't forwarding be enough?

Why is this happening? What is preventing internal DNS server to forward
queries to the ISP's server? It isn't the firewall, that is positive.

Bojan

 

[Dean Wells [MVP]]

Can you elaborate on "sometimes with works" etc?
Do the offending clients have multiple resolvers configured?
Is there anything in common to those that do not work?

Dean

 

[Kevin D. Goodknecht Sr. [MVP]]

In

I have the following configuration:

- small internal namespace with private addressing, dial-up, win2k
environment, one DNS server
- DNS server has forwarders (my ISP's servers)
- clients have internal DNS server for name resolving

The problem is that sometimes this works and sometimes it doesn't.
Sometimes I have to add ISP's server to the client's server list in
order to make internet work. Shouldn't forwarding be enough?

Yes, it should. Are there any errors in the event log?
Can you post an ipconfig /all with the dial up connection made?

 

[Bojan Zivancevic]

Sorry, I should have been more specific. It isn't the specific method that
causes the problem, it is the specific site. You see, this method works
great at one site, and it doesn't work at another one. Both sites have win2k
environment, and the only difference that I can think of right now is that
on the working site we have two dns servers (both have forwarders), an on
the other one there is only one dns server.

Of those two dns servers on the first site, the first in the client's dns
lists is also the default gateway with RRAS set up to make dial-up calls to
ISP. So, the client list looks sort of like this:

DNS servers
192.168.168.2 (this also the def. gateway)
192.168.168.1
both have forwarders (ISP servers)

The other site (non-working) has leased line and a router. The list look
like this:
192.168.0.1
forwarder are again the ISP servers
def. gateway is the router

I hope I made myself clear. If I think of something else, I'll post it.

Thx anyway

Can you elaborate on "sometimes with works" etc?
Do the offending clients have multiple resolvers configured?
Is there anything in common to those that do not work?

Dean

--
Dean Wells [MVP / Windows platform]
MSEtechnology
[[ Please respond to the Newsgroup only regarding posts ]]
R e m o v e t h e m a s k t o s e n d e m a i l

I have the following configuration:

- small internal namespace with private addressing, dial-up, win2k
environment, one DNS server
- DNS server has forwarders (my ISP's servers)
- clients have internal DNS server for name resolving

The problem is that sometimes this works and sometimes it doesn't. Sometimes
I have to add ISP's server to the client's server list in order to make
internet work. Shouldn't forwarding be enough?

Why is this happening? What is preventing internal DNS server to forward
queries to the ISP's server? It isn't the firewall, that is positive.

Bojan