Quote:
Originally Posted by HasC
dig and nslookup
|
dig gives me this:
is it configured correctly?
Is there any possibility of a dns timeout that might fix itself when squid is restarted?
Not sure what is causing the issue of squid not being able to lookup some websites.
I tried nslookup
www.skyplayer.com and it worked successfully.
Is it worth restarting the BIND server nightly: /etc/init.d/named restart
Code:
[root@server]# dig
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>>
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15604
;; flags: qr rd ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 13
;; QUESTION SECTION:
;. IN NS
;; ANSWER SECTION:
. 261039 IN NS e.root-servers.net.
. 261039 IN NS j.root-servers.net.
. 261039 IN NS c.root-servers.net.
. 261039 IN NS f.root-servers.net.
. 261039 IN NS i.root-servers.net.
. 261039 IN NS g.root-servers.net.
. 261039 IN NS h.root-servers.net.
. 261039 IN NS d.root-servers.net.
. 261039 IN NS k.root-servers.net.
. 261039 IN NS b.root-servers.net.
. 261039 IN NS l.root-servers.net.
. 261039 IN NS m.root-servers.net.
. 261039 IN NS a.root-servers.net.
;; ADDITIONAL SECTION:
i.root-servers.net. 3598798 IN A 192.36.148.17
h.root-servers.net. 3598798 IN A 128.63.2.53
c.root-servers.net. 3598798 IN A 192.33.4.12
k.root-servers.net. 3598798 IN A 193.0.14.129
a.root-servers.net. 3598798 IN A 198.41.0.4
g.root-servers.net. 3598798 IN A 192.112.36.4
l.root-servers.net. 3598798 IN A 199.7.83.42
b.root-servers.net. 3598798 IN A 192.228.79.201
f.root-servers.net. 3598798 IN A 192.5.5.241
e.root-servers.net. 3598798 IN A 192.203.230.10
m.root-servers.net. 3598798 IN A 202.12.27.33
d.root-servers.net. 3598798 IN A 128.8.10.90
j.root-servers.net. 3598798 IN A 192.58.128.30
;; Query time: 7 msec
;; SERVER: 213.171.192.249#53(213.171.192.249)
;; WHEN: Sat Jan 30 22:10:38 2010
;; MSG SIZE rcvd: 449