LinuxQuestions.org
Review your favorite Linux distribution.
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 07-15-2005, 11:32 AM   #1
A6Quattro
Member
 
Registered: Jul 2005
Location: SE, PA
Distribution: Fedora Core 3, Suse 9.3 pro(if I can get the NIC's working!!!)
Posts: 111

Rep: Reputation: 15
Can't resolve DNS issues. Am I using the right ones?


I have a Linksys router. It is autp configed with DHCP from the ISP. It gives me my IP, Gateway and 3 DNS's.

I have all my XP boxes set up with the gateway and the DNS as 192.168.1.1 (my router's local addy). I also have my FC3 box set up that way. I tried to set up my Suse 9.3 Pro box that way but it wouldn't work. I did some cheking and checked into my ISP DNS's and found some strange things. Maybe this is normal, I don't know.

My router has 3 DNS's setup with the Auto configuration. Here are my router's given DNS's:
DNS 1: 216.144.187.199
DNS 2: 207.44.96.129
DNS 3: 216.144.187.71

I looked at this site's "linux Answer's" section about DNS's and found the "dig" command, so I did the following:

**************************************************************************************************
$ dig @192.168.1.1 www.ptd.net

; <<>> DiG 9.2.4 <<>> @192.168.1.1 www.ptd.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31871
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 6, ADDITIONAL: 6

;; QUESTION SECTION:
;www.ptd.net. IN A

;; ANSWER SECTION:
www.ptd.net. 84894 IN A 204.186.9.3

;; AUTHORITY SECTION:
ptd.net. 14103 IN NS dns2.ptd.net.
ptd.net. 14103 IN NS dns3.ptd.net.
ptd.net. 14103 IN NS dns4.ptd.net.
ptd.net. 14103 IN NS dns5.ptd.net.
ptd.net. 14103 IN NS dns6.ptd.net.
ptd.net. 14103 IN NS dns1.ptd.net.

;; ADDITIONAL SECTION:
dns1.ptd.net. 84798 IN A 204.186.0.201
dns2.ptd.net. 84798 IN A 207.44.96.129
dns3.ptd.net. 85456 IN A 204.186.0.203
dns4.ptd.net. 171858 IN A 207.44.0.1
dns5.ptd.net. 84798 IN A 198.69.185.1
dns6.ptd.net. 84798 IN A 198.69.184.1

;; Query time: 14 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Fri Jul 15 12:04:53 2005
;; MSG SIZE rcvd: 255

********************************************************************************************

Is this the right way to find DNS's? None of the DNS's listed from "dig" are the same as the ones on my router. Is this normal? Am I doing something wrong? Which are the ones I should use for my resolv.conf file in SuSE?

Any help is GREATLY appreciated!
 
Old 07-15-2005, 01:03 PM   #2
demian
Member
 
Registered: Apr 2001
Location: Bremen, Germany
Distribution: Debian
Posts: 303

Rep: Reputation: 30
That looks pretty normal to me. The authority section tells you about the dns servers that are authorative for the domain ptd.net. You can see what happens during a query when you use a non-recursive lookup. Try some domain that you haven't looked up already (or else the answer might come from the router's dns cache).

For instance

dig +norecurse www.gsss.uni-bremen.de

This answers with a whole bunch of root servers. Now ask one of them:

dig +norecurse www.gsss.uni-bremen.de @192.58.128.30

This gets you the servers for the TLD .de

dig +norecurse www.gsss.uni-bremen.de @217.51.137.213

Now you know the nameservers for uni-bremen.de

dig +norecurse www.gsss.uni-bremen.de @134.102.200.14

Finally you've got your answer.

This is what your router does for you. It obviuosly doesn't know all the ip addresses on the internet, but it does know where to ask. Your ISP's dns server in turn only knows the ip addresses for the ISP's domain. If you ask for another address it starts from right to left: Get the server authorative for the root domain . These servers will tell you which servers are responsible for top level domains like .de .com .net,... and so on until you find the server that knows the answer.

Since your router is capable of dns forwarding just stick in 192.168.1.1 in your resolv.conf file.
 
Old 07-15-2005, 06:25 PM   #3
A6Quattro
Member
 
Registered: Jul 2005
Location: SE, PA
Distribution: Fedora Core 3, Suse 9.3 pro(if I can get the NIC's working!!!)
Posts: 111

Original Poster
Rep: Reputation: 15
Any idea why Suse 9.3 won't accept my router's IP as the Name server?
 
Old 07-15-2005, 06:59 PM   #4
demian
Member
 
Registered: Apr 2001
Location: Bremen, Germany
Distribution: Debian
Posts: 303

Rep: Reputation: 30
What do you mean it won't accept it? I'm not familiar with SuSE but isn't there a place in yast where you can enter things like DNS servers and gateway etc.?
 
Old 07-15-2005, 07:14 PM   #5
A6Quattro
Member
 
Registered: Jul 2005
Location: SE, PA
Distribution: Fedora Core 3, Suse 9.3 pro(if I can get the NIC's working!!!)
Posts: 111

Original Poster
Rep: Reputation: 15
When I put the router's IP in for the Name server, the browser comes back and says that the connection was refused.

Maybe there is something not configured correctly but I think I have it set up right. I posted before in the Suse forum and I was told I had to have my ISP's DNS's in the name server's... That was the only way it was going to work.

I'll see if anyone there can tell me more. Thanks for the help though.
 
Old 07-15-2005, 07:29 PM   #6
mcd
Member
 
Registered: Aug 2003
Location: Denver, CO
Distribution: CentOS, Debian
Posts: 825

Rep: Reputation: 33
if you have an /etc/resolv.conf file, you can put it in there and see if it works, as someone said earlier. otherwise, maybe it's something stupid like a firewall blocking outbound udp traffic on port 53? that needs to be open for name resolution to work.
 
Old 07-15-2005, 08:59 PM   #7
A6Quattro
Member
 
Registered: Jul 2005
Location: SE, PA
Distribution: Fedora Core 3, Suse 9.3 pro(if I can get the NIC's working!!!)
Posts: 111

Original Poster
Rep: Reputation: 15
it is in my resolv.conf file....
I have the firewall on my conputer turned off...
 
  


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
dns client cannot resolve on dns server jtvillegas Linux - Software 3 03-12-2016 03:30 PM
slow DNS resolve phkhoury Slackware 3 12-21-2003 12:37 AM
unable to resolve dns fivenics3cablem Slackware 7 12-03-2003 03:26 PM
[DNS] Resolve but can't get a result? Sir.Del Linux - Networking 4 08-18-2003 04:05 AM
if no DNS in /etc/resolve.conf then??? farhan Linux - General 4 03-14-2003 06:45 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 03:41 AM.

Main Menu
Advertisement
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
Open Source Consulting | Domain Registration