[HLUG] Test web server

[Andrew Hodgson]

Hi,

Best to set up a caching DNS server on the LAN.  Some routers also have
DNS proxy functionality, where you can enter local hostnames into the
router config and they will be resolved to the local IP addresses, but
it then forwards everything to the ISP's DNS server.  I never like now
configuring clients on the LAN to talk directly to outside DNS servers.

Andrew.

-----Original Message-----
From: herefordshire-bounces at mailman.lug.org.uk
[mailto:herefordshire-bounces at mailman.lug.org.uk] On Behalf Of Paul
Stenning
Sent: 22 April 2008 17:56
To: Herefordshire Linux Users Group.
Subject: Re: [HLUG] Test web server

Results:


*** PING TO THE SERVER ***

C:\Windows\system32>ping server2

Pinging server2 [192.168.0.210] with 32 bytes of data:
Reply from 192.168.0.210: bytes=32 time=4ms TTL=64
Reply from 192.168.0.210: bytes=32 time=1ms TTL=64
Reply from 192.168.0.210: bytes=32 time=1ms TTL=64
Reply from 192.168.0.210: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.0.210:
     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
     Minimum = 1ms, Maximum = 4ms, Average = 1ms



*** IPCONFIG (unused connections not shown) ***

C:\Windows\system32>ipconfig /all

Windows IP Configuration

    Host Name . . . . . . . . . . . . : Paul-Vista
    Primary Dns Suffix  . . . . . . . :
    Node Type . . . . . . . . . . . . : Broadcast
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wireless Network Connection:

    Connection-specific DNS Suffix  . :
    Description . . . . . . . . . . . : Intel(R) Wireless WiFi Link
4965AGN
    Physical Address. . . . . . . . . : 00-13-E8-**-**-**
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : 
fe80::d9bb:468b:1b90:16fb%12(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.0.3(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : 22 April 2008 16:34:36
    Lease Expires . . . . . . . . . . : 23 April 2008 16:34:35
    Default Gateway . . . . . . . . . : 192.168.0.254
    DHCP Server . . . . . . . . . . . : 192.168.0.254
    DNS Servers . . . . . . . . . . . : 212.23.3.100
                                        192.168.0.210
    NetBIOS over Tcpip. . . . . . . . : Enabled



*** NSLOOKUP ***

C:\Windows\system32>nslookup
Default Server:  dns.hq.svc.zen.net.uk
Address:  212.23.3.100

 > google.co.uk
Server:  dns.hq.svc.zen.net.uk
Address:  212.23.3.100

DNS request timed out.
     timeout was 2 seconds.
Non-authoritative answer:
Name:    google.co.uk
Addresses:  72.14.221.104
           66.249.93.104
           216.239.59.104

 > server2
Server:  dns.hq.svc.zen.net.uk
Address:  212.23.3.100

*** dns.hq.svc.zen.net.uk can't find server2: Non-existent domain
 > ec1.server2
Server:  dns.hq.svc.zen.net.uk
Address:  212.23.3.100

*** dns.hq.svc.zen.net.uk can't find ec1.server2: Non-existent domain
 >
C:\Windows\system32>



It looks like it only does the lookup on the primary name server.  If 
that replies as unknown it doesn't try the secondary

Any thoughts?

Thanks,
Paul.


paul.maddox.mail-list at synth.net wrote:
> Paul,
> 
>> Do you have any info on using nslookup?  If not I'll google it later.
> 
> at the command prompt type 'nslookup'
> 
> so ;-
> 
> c:\>nslookup   [Hit Return]
> 
> it'll then display ;-
> 
> Default Server: blahblah.blah.com
> Address: 192.192.192.192
> 
> where the name and address are the name and address of the server it's
using.
> 
> at the > prompt, just type 'google.com' (or the name of your box) and
hit
> return.
> 
> It's possible that your windows machine network domain name (the
> MyMachine.blah.com) doesn't match that of the name server.
> 
> Paul
> 
> 
> 
> 

-- 
Herefordshire LUG mailing list
Web:  http://www.herefordshire.lug.org.uk
List: https://mailman.lug.org.uk/mailman/listinfo/herefordshire