DNS maybe problems

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Restart named. ("#/etc/rc.d/init.d/named restart;") Then, test as follows, 
when logged into DNS system: 

nslookup - localhost 
> mydomain.com.

Notice the dot at the end of the domain. It'll either work or tell you that it 
didn't. If it works, your DNS server is set up. If not, your DNS server isn't 
as properly configured as you think.

-Ben

On Thursday 29 December 2005 07:28, Robert Moskowitz wrote:
> I am setting up a new DNS server.  It will be primary for my domain.
> 
> This server is in an active subnet with a real public address.
> 
> It is not setup yet properly in .com, but that is in the works.
> 
> In the var/named/chroot/etc
> 
> I added:
> 
> named.custom   (which I 'included' in named.conf)
> 
> and my various zone files.
> 
> All the log entries look good.
> 
> Oh in /etc/resolv.conf, I added my system as one of the namewervers.
> 
> When I go into nslookup and type any host name I get the error:
> 
> ** server can't find foo:NXDOMAIN
> 
> where foo is whatever I typed in.
> 
> so what else did I forget to change?
> 
> 
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
> 

-- 
"The best way to predict the future is to invent it."
- XEROX PARC slogan, circa 1978

[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux