Need DSL DNS setting used on routed intranet

[RNVPIT]

- LAN A 192.168.1.0 has a DSL line and DNS servers via ISP.
- LAN B 172.30.248.0 is a private network but has a static route to 192.168.1.0
- LAN B has no DNS set up (due to being a private network)
- From a PC on LAN B, I can ping addresses on LAN A but cannot use Internet Explorer to browse web

Can I somehow get LAN B to recognize and use the DNS setting of LAN A? Any other thoughts on how I can get LAN B to browse both private network (via WINS) and internet?

 

[RNVPIT]

Just more info:
- LAN A is supported by a Linksys router running DHCP
- LAN B is support by Eth1 on a Cisco 4500 running IOS 11.2
- DHCP on LAN B is provided by a Windows NT 4 server which does not supply DNS (but does supply WINS) info

 

[sgscit]

you can set your clients to use the DNS of your ISP. I did this while I did not have a functional DNS (we had probs with the W2K network config).

Are you able to bring web sites up using the IP address?
ie

http://xxx.xxx.xxx.xxx

You should be able to as you are able to ping. It will come up with many errors as most links and subsites are via DNS name not IP address, but the basics of the site should appear.

If you can access the sites via IP, add the IP address of a known DNS into your IP config.

If this works and you are now able to browse the web, add the DNS Servers scope option to DHCP. I don't know if the options are the same in NT4, but in DHCP, add the scope option 006 DNS Servers
Enter the IP address of the DNS server you require and your clients should be able to get to it once they refresh thier DHCP settings.

Hop this helps.

Pete

 

[RNVPIT]

sgscit,

Thanks for the feedback.
1) I did not try an internet site from LAN B using an IP address (didn't know any to try). However, I can get to an IIS web page from a LAN A workstation using its 172.30.x.x number. I'll see if I can try it the other way...I'm pretty sure it'll work.

2) I tried entering the DNS search server numbers of the ISP into a LAN B workstation but to no avail. The DNS address are both 64.105.x.x numbers and since there is no way for the Cisco router to tell that those numbers exist, I am assuming it does not know how to route those addresses?

I was wondering if Cisco had anything within their IOS to act as a secondary DNS, but I haven't found anything to that effect.

 

[ChrisAC]

If your router doesn't know how to get to the ISP DNS servers then it needs a default route via the DSL line.

Chris.

**********************
Chris Andrew, CCNA, CCSA
chris@iproute.co.uk
**********************

 

[RNVPIT]

WS B (172.30.250.0) WinNT DHCP Server (172.30.248.11)
|_______________________________| (LAN B - uses WINS)
172.30.248.0 255.255.252.0 |
|
172.30.248.1 (E0 of Cisco 4500)
192.168.1.200 (E1 of Cisco 4500)
_________________________|___
| | (LAN A)
WS A (192.168.1.100) 192.168.1.1 (LAN-Linksys router)
68.xxx.xxx.xxx (WAN-Linksys router)
DNS: 64.xxx.xxx.xxx (x2)

Static routes on Linksys & Cisco to tie together.

I need WS B to access internet via LAN A and DNS on Linksys. Does this help?
I can get to a web page on LAN B from WS a using IP address...still wating to try web page on LAN A from WS B (it's an active network so I have to bide my time to re-wire)