Re: Strange problem with DNS resolving on Squeeze
Le samedi 04 décembre, Pascal Hambourg écrivit : Hello, Andrew Wood a écrit : First of all, if I try and SSH into one of our internal servers (which works from other clients) I get: and...@debian:/$ ssh a...@sambatest1.wrinehillvilla.local ssh: Could not resolve hostname sambatest1.wrinehillvilla.local: Name or service not known but if I do a DNS query it resolves: and...@debian:/$ host sambatest1.wrinehillvilla.local sambatest1.wrinehillvilla.local has address 192.168.253.203 .local is used by mDNS/zeroconf. Don't use it for regular domains. Also, the order of the resolvers are not right by defaut (Personnal opinion). I put only that in my /etc/nsswitch.conf : hosts: files dns I don't use multicast DNS (Zeroconf). signature.asc Description: Digital signature
Re: Strange problem with DNS resolving on Squeeze
On Fri, 03 Dec 2010 21:00:49 +, Andrew Wood wrote: 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. (...) 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? For local domains, I agree with Pascal. Avoid using .local because it can conflict/interfere with avahi-zeroconf: http://en.wikipedia.org/wiki/.local For remote domains, just try using another DNS servers (OpenDNS ones or Google's) and see what happens. If you can browse the web, you'll have to check your local DNS server logs to see what is happening with the requests coming from your Squeeze box. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2010.12.04.09.59...@gmail.com
Re: Strange problem with DNS resolving on Squeeze
Andrew Wood wrote: if I try and SSH into one of our internal servers (which works from other clients) I get: and...@debian:/$ ssh a...@sambatest1.wrinehillvilla.local ssh: Could not resolve hostname sambatest1.wrinehillvilla.local: Name or service not known but if I do a DNS query it resolves: I don't have any good suggestions but I would look in your ~/.ssh/config to see if there are any options set for this host that would in some way affect things. I would run 'ssh -v' and look at the output to see if there are any clues there. As a workaround I would install connect-proxy and set up a ProxyCommand. $ sudo apt-get install connect-proxy Then verify that connect will work and resolve the hostname. (Use control-c to interrupt it to exit the program.) $ connect sambatest1.wrinehillvilla.local 22 Then create a stanza in ~/.ssh/config similar to: Host *.local ProxyCommand connect %h %p Then when you ssh to any host in that pseudo domain it will use the connect program instead of the built in network code. This won't necessarily tell you what is happening but may work around whatever situation you find yourself in. At this point a lot of people will jump in and suggest using 'nc' (netcat) intead of 'connect'. But after using 'nc' a lot I always found problems such as a lot of orphaned nc processes that never exited or nc processes that were orphaned and consuming 100% cpu time. It seems that nc by design is ignoring end-of-file in some cases and for whatever reason I often hit those cases and would end up with ten or twenty nc processes left behind. Using 'connect' avoided all of those issues and I now highly recommend 'connect' over 'nc' for exactly these types of applications. Bob signature.asc Description: Digital signature
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: and...@debian:/$ ssh a...@sambatest1.wrinehillvilla.local ssh: Could not resolve hostname sambatest1.wrinehillvilla.local: Name or service not known but if I do a DNS query it resolves: and...@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 www.example.com If you are unable to load any pages, check your computer's network connection. 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: and...@debian:/$ host www.hmrc.gov.uk www.hmrc.gov.uk has address 195.171.114.170 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? Thanks Andrew -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cf95a81.9060...@theiet.org
Re: Strange problem with DNS resolving on Squeeze
Andrew Wood put forth on 12/3/2010 3:00 PM: 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. ... Im totally perplexed by this. Anyone got any ideas? Yes, turn off SELinux/AppArmor and all iptables rules and see if that helps. AFAIK, all of the applications you mentioned use the same resolver library. If some applications (host) work, and others (ssh, firefox) don't, then it seems clear that something is interfering with the library calls from the failing applications. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cf9673d.5000...@hardwarefreak.com
Re: Strange problem with DNS resolving on Squeeze
Hello, Andrew Wood a écrit : First of all, if I try and SSH into one of our internal servers (which works from other clients) I get: and...@debian:/$ ssh a...@sambatest1.wrinehillvilla.local ssh: Could not resolve hostname sambatest1.wrinehillvilla.local: Name or service not known but if I do a DNS query it resolves: and...@debian:/$ host sambatest1.wrinehillvilla.local sambatest1.wrinehillvilla.local has address 192.168.253.203 .local is used by mDNS/zeroconf. Don't use it for regular domains. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cf97a16.4030...@plouf.fr.eu.org
