no ip from nslookup

Tom Douglas · 12-28-2007, 07:32 PM

Hi, Y'all!

I'm using a Fedora 8 box as a name server. I been on several websites, such as yolinux (http://www.yolinux.com/TUTORIALS/Lin...etworking.html). I can ping a host name but not locate a domain name.

From the name server box, I can ping another server with the host name using:
$ ping snow-white
PING snow-white (192.168.1.51) 56(84) bytes of data.
64 bytes from snow-white (192.168.1.51): icmp_seq=1 ttl=64 time=0.961 ms
64 bytes from snow-white (192.168.1.51): icmp_seq=2 ttl=64 time=0.336 ms
....
....so this tells me that my hosts file is set up correctly.

However I run a ping using a domain name:
$ ping snow-white.toms.net
ping: unknown host snow-white.toms.net
$

Running nslookup on either host or domain name offers no response.

named is running and was restarted. Any other servers that I should check?

/etc/resolve.conf has this...
search tomempire.net
nameserver road-runner

/etc/nsswitch.conf (besides a mess of commented lines) has this...
hosts: files dns

/var/named/chroot/var/named/toms.zone has this excerpt...
$TTL 7200
toms.net. IN SOA ns.toms.net. hostmaster.toms.net. (
2007111218 ; Serial # based on date and hour
3H ; Refresh
15M ; Retry
4H ; Expiry
4H ; Minimum
)
road-runner IN A 192.168.1.31
snow-white IN A 192.168.1.51
@ IN NS road-runner

My DNS GUI utility shows snow-white being 192.168.1.51.

What am I missing???

Thanks!

Tom D.

thedonkdonk · 12-29-2007, 01:01 AM

Tom,

Looks like you are trying to access a private network using a public domain name. I am not sure that will work.

Thanks,
James Glenn
www.thedonkdonk.net

Tom Douglas · 12-31-2007, 07:54 AM

Quote:

Originally Posted by thedonkdonk

Tom,

Looks like you are trying to access a private network using a public domain name. I am not sure that will work.

Actually the whole operation is on a private network; no Internet access. So DNS (bind) would not work at all?

Tom D.

trickykid · 12-31-2007, 08:03 AM

If your domain on your private network is toms.net, you'll probably want to have that as your search in your resolv.conf file:

search toms.net
nameserver [ip-address]

And I always put my nameserver IP address instead of the actual hostname. And you need to choose, either use your /etc/hosts file for dns lookups or use your actual name server, it's not always a good idea to have a mixture of both, it can cause confusion and duplicate work for name resolution.

Tom Douglas · 01-01-2008, 03:47 PM

Quote:

Originally Posted by trickykid

If your domain on your private network is toms.net, you'll probably want to have that as your search in your resolv.conf file:

search toms.net
nameserver [ip-address]

And I always put my nameserver IP address instead of the actual hostname. And you need to choose, either use your /etc/hosts file for dns lookups or use your actual name server, it's not always a good idea to have a mixture of both, it can cause confusion and duplicate work for name resolution.

OK, I cleaned out the /etc/hosts file and restarted the network service.

Also changed the resolv.conf server name to an IP address.

Made sure named is running....

Code:

[root@road-runner tom]# service named status
version: 9.5.0a6
number of zones: 14
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/0/1000
tcp clients: 0/100
server is up and running
named (pid  1756) is running...
[root@road-runner tom]#

Still getting "Servers could not be reached" for executing nslookup. This was excuted from the name server box.

The name service GUI utility shows my host domain names and addresses. Any ideas what I'm missing?

A side question from the command prompt above: How would I enable the query logging? (That was why I listed the name server response above.)

Tom D.