proxy hell..Why does it hacking me.
 

I have a lot of problem in DNS.

i am connected to internet by an proxy server which is an only one server to whole university.
I know the ISP of proxy server.And i know the DNS server's of ISP.


[root@g01 ~]# dig google.com

; <<>> DiG 9.2.4 <<>> google.com
;; global options: printcmd
;; connection timed out; no servers could be reached

[root@g01 ~]# nslookup google.com
;; connection timed out; no servers could be reached

[root@g01 ~]# whois google.com
[Querying whois.internic.net]
[whois.internic.net: Temporary failure in name resolution]
[Unable to connect to remote host]
[root@g01 ~]#

[root@g01 ~]#cat /etc/resolv.conf
nameserver 10.1.1.2
nameserver 10.1.1.1
nameserver 127.0.0.1


Which seems that proxy server Not in a position to translate the hostname.Whose port has been blocked.
Is the any GNU tool or anything to over come this and query the externel world.
And what about externel World DNS server's Can i reach them from my command Line.

please help me.

From man dig..

do dig www.google.com @ip.of.dns.server to put the request directly to the dns server.

You may find the ip numbers you have for dns servers in resolv.conf are incorrect if they don't respond.
Do you get these dns numbers via dhcp or manually?

manually ?Is there any way by an DHCP ?

Actually the ISP nameserver is "ns3.vsnl.com.ns1chn.vsnl.com"


[root@g04 ~]# dig www.google.com @ns3.vsnl.com.ns1chn.vsnl.com
dig: Couldn't find server 'ns3.vsnl.com.ns1chn.vsnl.com': Temporary failure in name resolution
[root@g04 ~]#

look like proxy not alowing me..
That is why i am looking for a tool to overcome this...

I think the dns servers are ns3.vsnl.com (203.197.12.42) and ns1chn.vsnl.com (202.54.6.60)

Use the ip numbers, coz without a dns server you can't resolve names..

Manually means you set your ip number, and dhcp means you find a server to set your ip number.
dhcp can also set many other numbers, eg dns, time, gateway etc

okey

pls look at my result.

linux:~ # dig @203.197.12.42 google.com

; <<>> DiG 9.2.3 <<>> @203.197.12.42 google.com
;; global options: printcmd
;; connection timed out; no servers could be reached
linux:~ # dig @202.54.6.60 google.com

; <<>> DiG 9.2.3 <<>> @202.54.6.60 google.com
;; global options: printcmd
;; connection timed out; no servers could be reached
linux:~ #

wha was wrong with that?

hehehe..

dig google.com @203.197.12.42

Either way works for me, though man dig suggests [ @server ] should be placed *before* [ name ].

In this case it seems tcp port 53 traffic to destinations outside the LAN is blocked - bruse will only be able to dig nameservers on the LAN. I suggest checking the configuration of a computer with working proxy access. If other machines are configured to use DHCP, this one should be too (unless it's a server or the network admin has given you a static IP address to use, in which case ask the admin for nameserver IP address(es) to use.

If you are needing to use a proxy there is no need to resolve the address. Just let the proxy do that.

It is entirely possible that you can't get directly to a DNS server that will resolve the outside world.

Mike K.