workstation DNS issue

My BSD workstation can't resolve names fast. It used to work
immediately but all of a sudden it slowed down. The Windows machines
are able to resolve names fast.

From the looks of "dig", it's not reading in the nameservers from
resolv.conf. Help please.



I have FreeBSD 6.0-RELEASE.


%less /etc/resolv.conf
#search 192.168.1.1
nameserver 204.127.202.19
nameserver 216.148.227.79
nameserver 68.87.68.162






# dig

; <<>> DiG 9.3.1 <<>>
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48493
;; flags: qr rd ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 13

;; QUESTION SECTION:
;. IN NS

;; ANSWER SECTION:
. 447965 IN NS a.root-servers.net.
. 447965 IN NS h.root-servers.net.
. 447965 IN NS c.root-servers.net.
. 447965 IN NS g.root-servers.net.
. 447965 IN NS f.root-servers.net.
. 447965 IN NS b.root-servers.net.
. 447965 IN NS j.root-servers.net.
. 447965 IN NS k.root-servers.net.
. 447965 IN NS l.root-servers.net.
. 447965 IN NS m.root-servers.net.
. 447965 IN NS i.root-servers.net.
. 447965 IN NS e.root-servers.net.
. 447965 IN NS d.root-servers.net.

;; ADDITIONAL SECTION:
h.root-servers.net. 569691 IN A 128.63.2.53
c.root-servers.net. 569691 IN A 192.33.4.12
g.root-servers.net. 569691 IN A 192.112.36.4
f.root-servers.net. 569691 IN A 192.5.5.241
b.root-servers.net. 569691 IN A 192.228.79.201
j.root-servers.net. 569691 IN A 192.58.128.30
k.root-servers.net. 569691 IN A 193.0.14.129
l.root-servers.net. 569691 IN A 198.32.64.12
m.root-servers.net. 569691 IN A 202.12.27.33
i.root-servers.net. 569691 IN A 192.36.148.17
e.root-servers.net. 569691 IN A 192.203.230.10
d.root-servers.net. 569691 IN A 128.8.10.90
a.root-servers.net. 569691 IN A 198.41.0.4

;; Query time: 12 msec
;; SERVER: 68.87.68.162#53(68.87.68.162)
;; WHEN: Tue Apr 25 20:21:38 2006
;; MSG SIZE rcvd: 436





--
Ashok Shrestha
_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: resolver problem
    ... If this isn't a Linux distro of some sort, ... nameserver 1.2.3.4 ... domain name of wherever you are, and if you try to resolve "machine", ... your DNS machine, talk to your sysadmin and find out. ...
    (comp.os.linux.networking)
  • Re: resolver problem
    ... If this isn't a Linux distro of some sort, ... nameserver 1.2.3.4 ... domain name of wherever you are, and if you try to resolve "machine", ... your DNS machine, talk to your sysadmin and find out. ...
    (comp.os.linux.misc)
  • Re: Re.: Modem Problem.
    ... hostname into /etc/hosts. ... starting when the systems tries to boot. ... If your system can not resolve the FULL hostname from the /etc/hosts file, ... The nameserver has to be reachable NOW ...
    (comp.os.linux.misc)
  • Re: Squid blocking server hostname?
    ... MA> nameserver 127.0.0.1 ... "Gateway" probably tries to resolve outside addresses, ... The host file has every network address on the LAN in it a)to simplify connectivity within the LAN and b) I've got wacky stuff going on where hostnames are not being properly resolved. ...
    (comp.os.linux.networking)
  • Re: OT: Evacuations are not feasable
    ... >Yeah, I'm the sysop at www.abiengr.com, which is my client's website. ... >IP, that uses http://www.zoneedit.com for a nameserver, that can ... >that http://www.neodruid.org should resolve to ...
    (sci.electronics.design)
Quantcast