DG834 V2 DNS Settings 1

[DanielUK]

I've just bought one of these DG834 V2 ADSL routers to share our BTConnect (UK) broadband connection on our LAN (windows 2000) but am having a bit of trouble getting it to view websites.

The clients have 192.168.0.17 (the router's IP address) set as the default gateway within TCP/IP settings for the LAN. I am able to ping the router and can ping an external ip address through the router. I can also send/receive email (although this seems to be slow).

Problem comes with viewing websites. The initial popup window test in basic settings comes up as a "success" and says it's connected, but it cannot reach any websites -I get "page cannot be found". I have two BTConnect DNS server ip addresses in the configuration which I can ping when connected.

Just wondering what to check now as I'm still thinking it's DNS related.

Thanks

Dan

 

[allteltec]

Ping a ip
ping 68.142.226.47
Then ping a www, like yahoo.com
ping

http://www.yahoo.com

if the 68.142,226,47 passes but the

http://www.yahoo.com

fails you have a dns problem.
You can always set static dns info in you network seting in eash computer. I still have some old cisco PPoA ADSL routers that do not pass DNS info so you have to set it static in each pc.

 

[DanielUK]

Thanks allteltec,

Yes, can ping outside IP but not a domain name. When you say static DNS, each client points to our two Win2k servers for DNS which in turn have forwarders to the Btconnect DNS servers. The router itself is also setup to to get dns from the btconnect servers so in one way or other, it all points to Btconnect for outside DNS queries.

Dan

 

[DanielUK]

Right, progress of sorts.

You were right, I replaced our internal DNS servers with the BTConnect dns server addresses in the TCP/IP properties of the LAN connection. Now I can use the router to connect.

Only (obvious) problem is I can't ping the names on the LAN anymore. I thought that if I had the Forwarders set up correctly in dns, any query the LAN servers caould not handle would go to those IP's instead -looks like this isn't happening.

Thanks

Dan

 

[bcastner]

Win2k/XP differs from previous versions of windows in that it uses DNS as it's primary name resolution method for finding domain controllers:
How Domain Controllers Are Located in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;314861

If DNS is misconfigured, XP will spend a lot of time waiting for it to timeout before it tries using legacy NT4 sytle NetBIOS. (Which may or may not work.)

1. Ensure that the Win2k/XP clients are all configured to point to the local DNS server which hosts the AD domain. That will probably be the Win2k server itself. They should NOT be pointing to an ISP's DNS server. An 'ipconfig /all' on the Win2k/XP box should reveal ONLY the domain's DNS server. You should use the DHCP server to push out the local DNS server address.

2. Ensure DNS server on win2k is configured to permit dynamic updates. Ensure the win2k server points to itself as a DNS server using 127.0.0.1 as the DNS address.

3. For external (internet) name resolution, specify your ISP's DNS server not on the clients, but in the forwarders tab of the local Win2k DNS server. On the DNS server, if you cannot access the 'Forwarders' and 'Root Hints' tabs because they are greyed out, that is because there is a root zone (".") present on the DNS server. You MUST delete this root zone to permit the server to forward unresolved queries to yout ISP or the root servers. Accept any nags etc, and let it delete any corresponding reverse lookup zones if it asks.

The following articles may assist you in setting up DNS correctly:
Setting Up the Domain Name System for Active Directory

http://support.microsoft.com/default.aspx?scid=kb;en-us;237675

HOW TO: Configure DNS for Internet Access in Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

 

[allteltec]

Sorry I did not see you where on a doman, My info was for a none doman home setup, Bill's the man for you problem. thanks bill for the good info I have a 2000 server setup a tec. has been after me to do.

 

[DanielUK]

OK, I got it figured, the gateway on the server was pointing to the wrong router (unplugged) so there was no way for it to resolve external DNS queries (couldn't connect). Everything works fine now, thanks for your help.

Dan