SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-15-2008, 02:00 PM
| ||||
| ||||
 Re: Nameserver Problems In article <406B5974.6B919FFA@tkg.ca>, mike@tkg.ca says... > Alex Threlfall wrote: > > > > Hi, > > > > I'm having one or two problems getting my box to resolve names. > > > > I've created and chmoded /etc/resolv.conf to read: > > hostresorder local bind > > nameserver 192.168.0.102 > > and i've added an entry in /etc/hosts for 192.168.0.102 > > however I get the error: > > # nslookup cyberprog.net > > *** Can't find server name for address 192.168.0.102: Non-existent > > host/domain > > *** Default servers are not available > > # nslookup 192.168.0.102 > > *** Can't find server name for address 192.168.0.102: Non-existent > > host/domain > > *** Default servers are not available > > > > Tearing my hair out here! Any ideas? > > -- > > Alex Threlfall > > Cyberprog New Media > > www.cyberprog.net > > tel - 0870 446 0789 > > fax - 0870 446 1789 > > What is the IP address and default route of the server? > There is no need to have the name of the 192.168.0.102 DNS server > in the hosts file, the first error message you are getting is a > bit misdirecting. The DNS lookup is not being responded to, so it > is not getting any information. It reports that it is not > getting the name back from the DNS server, hence the error. > > What do you get from "ping 192.168.0.102"? That should give the > name from the hosts file. > > Mike > > well in the end i sorted it by using the public nameservers rather than the dns forwarder on the router. it would appear that despite the entry in the hosts file that it couldn't resolve the nameserver. the dns forwarder worked fine for the windows machines on the lan, so that wasn't the problem, and the machine had a default route to the internet (using the method i described a few posts down). Hey ho, works now  -- Alex Threlfall Cyberprog New Media www.cyberprog.net tel - 0870 446 0789 fax - 0870 446 1789      |
|
02-15-2008, 02:01 PM
| ||||
| ||||
| Re: Nameserver Problems Alex Threlfall wrote: > -snip- > > well in the end i sorted it by using the public nameservers rather than > the dns forwarder on the router. > > it would appear that despite the entry in the hosts file that it > couldn't resolve the nameserver. the dns forwarder worked fine for the > windows machines on the lan, so that wasn't the problem, and the machine > had a default route to the internet (using the method i described a few > posts down). Hey ho, works now > -- > Alex Threlfall > Cyberprog New Media > www.cyberprog.net > tel - 0870 446 0789 > fax - 0870 446 1789 The hosts file entry really does nothing as far as your problem is concerned, the error was telling you that the DNS server did not resolve itself. It may be that the windows machines are getting the info from DHCP, and in reality are using your ISPs DNS servers. You may be able to test what is happening from the router by using dig @ip_address_of_router www.sco.com There should be a question, authority and answer section in the response. If the command hangs, then the router is simply not a DNS anything. If the command returns a question and authority section, the router is responding but may not be configured correctly. Try it and post the response. Mike -- Michael Brown The Kingsway Group |
Linear Mode
