Strange problem with DNS resolving on Squeeze
Im experiencing strange DNS resolution problems with a Squeeze desktop
system on our simple LAN which has an internal DNS server for local
hosts, and which also proxies DNS requests for public IP addresses
needed by internal clients.
The other clients on our network can resolve names fine.
First of all, if I try and SSH into one of our internal servers (which
works from other clients) I get:
andrew@debian:/$ ssh firstname.lastname@example.org
ssh: Could not resolve hostname sambatest1.wrinehillvilla.local: Name or
service not known
but if I do a DNS query it resolves:
andrew@debian:/$ host sambatest1.wrinehillvilla.local
sambatest1.wrinehillvilla.local has address 192.168.253.203
If I then substitute the IP address into the SSH command it works fine.
Also I have been unable for weeks to access the UK Government Tax
website with Firefox on Squeeze even tho all other sites are working
fine and again other clients on our network can access it. On squeeze I
get the following:
===Firefox error page====
Server not found
Firefox can't find the server at www.hmrc.gov.uk.
Check the address for typing errors such as
ww.example.com instead of
If you are unable to load any pages, check your computer's network
If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.
but again if I do a DNS query from the command line it resolves:
andrew@debian:/$ host www.hmrc.gov.uk
www.hmrc.gov.uk has address 188.8.131.52
As I say the site is accessible from our Mac clients so it cant be a
problem with the site itself.
There doesnt seem to be any logic to this. Its as if the host command
can query the DNS no problem but applications like Firefox and the SSH
client cant for some domain names, yet they can for others.
Our DNS server is running Windows Server 2003.
Im totally perplexed by this. Anyone got any ideas?