[HLUG] Test web server

[paul.maddox.mail-list at synth.net]

Hi,

>> *** 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

ok, good, you're on the same subnet :-)
Just had to check.

>> *** IPCONFIG (unused connections not shown) ***
>>
>> C:\Windows\system32>ipconfig /all
>>
>> Windows IP Configuration
>>
>>     Host Name . . . . . . . . . . . . : Paul-Vista
>>     Primary Dns Suffix  . . . . . . . :

ok, this concerns me...
Normally I'd set the DNS suffix the same as the name server suffix.
I mean, if your name server is "MyDNS.MyDomain.com" the windows box would
normally be "Paul-Vista.MyDomain.com"

>> 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

There's your problem!
your DNS server is a secndary DNS server in your config.

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

This proves it.
At the > prompt try typeing - server 192.168.0.210
then type in the name of the machine you're trying to resolve.

>> It looks like it only does the lookup on the primary name server.

indeed, why try the secondary if the primary is giving you a reponse?
this is a valid behaviour, even if the response is "sorry I don't know
that name", it's still a valid response.
You need to make your internal DNS server the primary, and get to refer
it's queries out to your ISPs DNS (212.23.3.100).
That way, if your local one knows the answer, it will give it you, if not,
it'll pass the query to the ISP DNS.

Paul