LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices

Reply
 
Search this Thread
Old 08-09-2005, 04:55 AM   #1
chhansopheaktra
LQ Newbie
 
Registered: May 2004
Location: Cambodia
Posts: 5

Rep: Reputation: 0
Unhappy my bind 8.2.4 sometime can't resolve name


Sorry if this issue has already been posted.
Anyway, I've been having trouble with my dns server running bind 8.2.4.
Sometime with some strange domain, it can only resolve NS record but not other like A or MX. but if i use other dns, it works.
This make me unable to browse that site using my dns.
I really don't know why.
Could any one help me.
 
Old 08-11-2005, 03:18 AM   #2
fur
Member
 
Registered: Dec 2003
Distribution: Debian, FreeBSD
Posts: 310

Rep: Reputation: 35
Is there a reason you are still running that old version of Bind? It is much more susceptible to cache poisoning atacks than Bind 9.

I'm guessing this is just a cache server at this point.

If it can pull the NS record for a domain is it able to perform lookups on that server?

For example lets say you can't get yahoo.com to resolve. Try this on your DNS server..


To get the NS servers...
Code:
# dig yahoo.com NS

; <<>> DiG 9.3.1 <<>> yahoo.com NS
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34790
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 5

;; QUESTION SECTION:
;yahoo.com.                     IN      NS

;; ANSWER SECTION:
yahoo.com.              129491  IN      NS      ns1.yahoo.com.
yahoo.com.              129491  IN      NS      ns2.yahoo.com.
yahoo.com.              129491  IN      NS      ns3.yahoo.com.
yahoo.com.              129491  IN      NS      ns4.yahoo.com.
yahoo.com.              129491  IN      NS      ns5.yahoo.com.

;; ADDITIONAL SECTION:
ns1.yahoo.com.          133520  IN      A       66.218.71.63
ns2.yahoo.com.          137437  IN      A       66.163.169.170
ns3.yahoo.com.          137437  IN      A       217.12.4.104
ns4.yahoo.com.          137442  IN      A       63.250.206.138
ns5.yahoo.com.          137437  IN      A       216.109.116.17
Now we will ask their NS server (ns1.yahoo.com) for the Authoritative record for yahoo.com

Code:
# dig @ns1.yahoo.com yahoo.com A

; <<>> DiG 9.3.1 <<>> @ns1.yahoo.com yahoo.com A
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18021
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 5, ADDITIONAL: 5

;; QUESTION SECTION:
;yahoo.com.                     IN      A

;; ANSWER SECTION:
yahoo.com.              300     IN      A       216.109.112.135
yahoo.com.              300     IN      A       66.94.234.13

;; AUTHORITY SECTION:
yahoo.com.              172800  IN      NS      ns1.yahoo.com.
yahoo.com.              172800  IN      NS      ns2.yahoo.com.
yahoo.com.              172800  IN      NS      ns3.yahoo.com.
yahoo.com.              172800  IN      NS      ns4.yahoo.com.
yahoo.com.              172800  IN      NS      ns5.yahoo.com.

;; ADDITIONAL SECTION:
ns1.yahoo.com.          172800  IN      A       66.218.71.63
ns2.yahoo.com.          172800  IN      A       66.163.169.170
ns3.yahoo.com.          172800  IN      A       217.12.4.104
ns4.yahoo.com.          172800  IN      A       63.250.206.138
ns5.yahoo.com.          172800  IN      A       216.109.116.17

;; Query time: 89 msec
;; SERVER: 66.218.71.63#53(66.218.71.63)
;; WHEN: Thu Aug 11 00:16:52 2005
;; MSG SIZE  rcvd: 229
In the "ANSWER SECTION:" holds the IP for yahoo.com

So knowing if you can do that from the DNS server will help isolate the problem. Your server could just have bad cache for the domain. Is this a public server or is it behind a firewall on a private network?
 
Old 08-11-2005, 06:29 AM   #3
chhansopheaktra
LQ Newbie
 
Registered: May 2004
Location: Cambodia
Posts: 5

Original Poster
Rep: Reputation: 0
Smile

Thank you Fur for your help.
I ever try some test like what you said. let's say the domain is 855greeting.com

I try " dig 855greeting.com NS " I got the NS record for this domain.
but if I asked for A record " dig www.855greeting.com A " it said connection timeout.
If I query that domain's nameserver " dig @server www.855greeting.com A " I got the answer.
It happened like this for just some domain.

Anyway, now I upgrade to Bind 9.3. It works just find. But I wonder what's wrong with the old
version.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
BIND - Locally OK, LAN cleints unable to resolve? Xaque208 Linux - Networking 2 08-08-2005 09:32 AM
BIND/DNS: Some subdomains resolve, some don't natetheros Linux - Networking 0 04-22-2005 06:36 PM
Any way to make bind resolve any request to same IP? fur Linux - Networking 4 07-13-2004 11:18 PM
bind & resolve local hosts jingo_man Linux - Networking 7 07-08-2004 02:56 PM
How to resolve base domain name using bind/named? qidwai Linux - Networking 2 05-08-2004 10:46 AM


All times are GMT -5. The time now is 10:32 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration