Greetings, My DNS server ns.teq (an internal only server), resolves names from the clients it serves, eg: login at client - ping FQDN - get response. but it won't resolve on itself eg: login on server physically - ping FQDN - get unknown host error. I must have missed something small in the config files. Some thing pointing named.conf to allow resolving on localhost, but I can't find it anywhere. Can any one help me here Please? -- Chadley Wilson Redhat Certified Technician Cert Number: 603004708291270 Pinnacle Micro Manufacturers of Proline Computers ==================================== Exercise freedom, Use LINUX =====================================
On Mon, 2005-05-09 at 12:54 +0200, Chadley Wilson wrote:
Greetings,
My DNS server ns.teq (an internal only server), resolves names from the clients it serves, eg: login at client - ping FQDN - get response. but it won't resolve on itself eg: login on server physically - ping FQDN - get unknown host error.
I must have missed something small in the config files. Some thing pointing named.conf to allow resolving on localhost, but I can't find it anywhere.
Can any one help me here Please?
Check the /etc/resolv.conf file on the server. Make sure it has a proper search entry and that the dns entries are correct, include one for the server itself if it is not there. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Monday 09 May 2005 13:47, Ken Schneider wrote:
On Mon, 2005-05-09 at 12:54 +0200, Chadley Wilson wrote:
Greetings,
My DNS server ns.teq (an internal only server), resolves names from the clients it serves, eg: login at client - ping FQDN - get response. but it won't resolve on itself eg: login on server physically - ping FQDN - get unknown host error.
I must have missed something small in the config files. Some thing pointing named.conf to allow resolving on localhost, but I can't find it anywhere.
Can any one help me here Please?
Check the /etc/resolv.conf file on the server. Make sure it has a proper search entry and that the dns entries are correct, include one for the server itself if it is not there.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably
domain teq search 192.168.2.1 mmm! it is there and is correct, pointing back to itself. -- Chadley Wilson Redhat Certified Technician Cert Number: 603004708291270 Pinnacle Micro Manufacturers of Proline Computers ==================================== Exercise freedom, Use LINUX =====================================
On Mon, 2005-05-09 at 16:03 +0200, Chadley Wilson wrote:
On Monday 09 May 2005 13:47, Ken Schneider wrote:
On Mon, 2005-05-09 at 12:54 +0200, Chadley Wilson wrote:
Greetings,
My DNS server ns.teq (an internal only server), resolves names from the clients it serves, eg: login at client - ping FQDN - get response. but it won't resolve on itself eg: login on server physically - ping FQDN - get unknown host error.
I must have missed something small in the config files. Some thing pointing named.conf to allow resolving on localhost, but I can't find it anywhere.
Can any one help me here Please?
Check the /etc/resolv.conf file on the server. Make sure it has a proper search entry and that the dns entries are correct, include one for the server itself if it is not there.
<snip> Please trim your replies.
domain teq search 192.168.2.1
mmm! it is there and is correct, pointing back to itself.
Then it would appear you do not have DNS setup correctly or it is not running. Try ps auxww|grep named and see if bind is running. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Monday 09 May 2005 16:54, Ken Schneider wrote:
Then it would appear you do not have DNS setup correctly or it is not running. Try ps auxww|grep named and see if bind is running.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
I would agree with on "you do not have DNS setup correctly" as in my first mail I showed that all the workstations can ping each other and the server using just hostnames. You just can't ping any of them from the server, funny though if I dig ns.teq on the server I do get a respons. The server is ns.teq, just so that you know. :) This is interesting however, just tried this -might shed some light on the situation: Look at these ping results run on the server itself. ++++++++++++++++++++++++++++++++++++ ns:~ # ping chadlap ping: unknown host chadlap ns:~ # ping chadlap.teq PING chadlap.teq (192.168.2.5) 56(84) bytes of data. 64 bytes from chadlap.teq (192.168.2.5): icmp_seq=1 ttl=64 time=0.194 ms 64 bytes from chadlap.teq (192.168.2.5): icmp_seq=2 ttl=64 time=0.191 ms ns:~ # ping ns ping: unknown host ns ns:~ # ping ns.teq PING ns.teq (192.168.2.1) 56(84) bytes of data. 64 bytes from ns.teq (192.168.2.1): icmp_seq=1 ttl=64 time=0.092 ms 64 bytes from ns.teq (192.168.2.1): icmp_seq=2 ttl=64 time=0.079 ms ++++++++++++++++++++++++++++++++++++++++ ^^^^Remember this is on the DNS server itself.^^^^^^ Now here I removed the /etc/hosts entries for my laptop (chadlap.teq) on my laptop. +++++++++++++++++++++++++++++++++++++++ chadlap:~ # ping ns PING ns.teq (192.168.2.1) 56(84) bytes of data. 64 bytes from ns.teq (192.168.2.1): icmp_seq=1 ttl=64 time=0.228 ms chadlap:~ # ping chadlap PING chadlap.teq (192.168.2.5) 56(84) bytes of data. 64 bytes from chadlap.teq (192.168.2.5): icmp_seq=1 ttl=64 time=0.033 ms 64 bytes from chadlap.teq (192.168.2.5): icmp_seq=2 ttl=64 time=0.023 ms ++++++++++++++++++++++++++++++++++++++++ Maybe now we can work out why! the server is not resolving if just the hostname is provided, it requires the FQDN. Which means previous statements to FQDN by me where wrong, SORRY ! It does resolve the FQDN as hostname.domain as you can see. He whispers to himself : "This is going to be a semicolon, I can just feel it?? " :) -- Chadley Wilson Redhat Certified Technician Cert Number: 603004708291270 Pinnacle Micro Manufacturers of Proline Computers ==================================== Exercise freedom, Use LINUX =====================================
On 09.05.05,12:54, Chadley Wilson wrote:
Greetings,
My DNS server ns.teq (an internal only server), resolves names from the clients it serves, eg: login at client - ping FQDN - get response. but it won't resolve on itself eg: login on server physically - ping FQDN - get unknown host error.
I must have missed something small in the config files. Some thing pointing named.conf to allow resolving on localhost, but I can't find it anywhere.
Can any one help me here Please?
Try dnswalk: http://www.visi.com/~barr/dnswalk/ - Jostein
--
Jostein Berntsen
On Monday 09 May 2005 14:05, Jostein Berntsen wrote:
On 09.05.05,12:54, Chadley Wilson wrote:
Greetings,
My DNS server ns.teq (an internal only server), resolves names from the clients it serves, eg: login at client - ping FQDN - get response. but it won't resolve on itself eg: login on server physically - ping FQDN - get unknown host error.
I must have missed something small in the config files. Some thing pointing named.conf to allow resolving on localhost, but I can't find it anywhere. Well my dear friends, I was astonished to find the problem in my resolv.conf file.
ns:/ # cat /etc/resolv.conf domain teq search 192.168.2.1 It now looks like this: ns:/ # cat /etc/resolv.conf domain teq search teq I assumed the "domain teq" would have done the trick by itself, amazing how a small thing causes such troubles in ones life. Got the answer from Thomas Mason on a local mailing list in SA called GLUG. Anyway, thanks to all who contributed, I do appreciate it. :) And by the way dnswalk looks pretty cool! -- Chadley Wilson Redhat Certified Technician Cert Number: 603004708291270 Pinnacle Micro Manufacturers of Proline Computers ==================================== Exercise freedom, Use LINUX =====================================
From: "Chadley Wilson"
Well my dear friends, I was astonished to find the problem in my resolv.conf file.
ns:/ # cat /etc/resolv.conf domain teq search 192.168.2.1
It now looks like this: ns:/ # cat /etc/resolv.conf domain teq search teq
I assumed the "domain teq" would have done the trick by itself,
amazing how a small thing causes such troubles in ones life.
Don't feel so bad Chad, See Google's Little DNS problem...... I know his IQ was only 140, but he said he was Sergey's cousin. Turns out that even the Google Labs Aptitude Test can't filter human error out of the rank and file. That's what Google found out Saturday afternoon when a DNS misconfiguration knocked the search leader and its various Web properties offline for 15 minutes or so. Gmail, Google News, Froogle -- from 3:45 to 4 p.m. PDT, you couldn't access any of them unless you happened to know their IP addresses. Google was typically tight-lipped about the incident, saying only that it was a DNS glitch and nothing sinister that had felled the company's sites. "It was not a hacking or a security issue," said Google spokesperson David Krane. "Google's global properties were unavailable for a short period of time. We've remedied the problem and access to Google has been restored worldwide." -- David C. Rankin, J.D., P.E. RANKIN LAW FIRM, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com --
On Mon, 2005-05-09 at 19:30 +0200, Chadley Wilson wrote:
On Monday 09 May 2005 14:05, Jostein Berntsen wrote: Well my dear friends, I was astonished to find the problem in my resolv.conf file.
ns:/ # cat /etc/resolv.conf domain teq search 192.168.2.1
It now looks like this: ns:/ # cat /etc/resolv.conf domain teq search teq
I assumed the "domain teq" would have done the trick by itself,
amazing how a small thing causes such troubles in ones life.
Got the answer from Thomas Mason on a local mailing list in SA called GLUG.
Anyway, thanks to all who contributed, I do appreciate it. :)
And by the way dnswalk looks pretty cool!
Except you now have -no- dns servers specified. add a line similar to: nameserver 192.168.1.1 use the IP of your nameserver (DNS server) and include the ones from your ISP as well. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
participants (4)
-
Chadley Wilson -
david rankin -
Jostein Berntsen -
Ken Schneider