troubleshooting Question

ping request could not find host. Please check the name and try again

Avatar of sam kalinguappa
sam kalinguappa asked on
DNS* CentOS* vps
7 Comments1 Solution2215 ViewsLast Modified:
I bought A vps and somehow i configured the nameservers wrong ON CentsOS 7. so i installed the bind and followed the instructions on this link http://www.unixmen.com/setting-dns-server-centos-7/ . when i ssh the server and ping the host i get this result.<br/>
ping livedigix.us<br/>
PING livedigix.us (67.21.78.228) 56(84) bytes of data.<br/>
64 bytes from mail.livedigix.us (67.21.78.228): icmp_seq=1 ttl=64 time=0.024 ms<br/>
64 bytes from mail.livedigix.us (67.21.78.228): icmp_seq=2 ttl=64 time=0.053 ms<br/>
64 bytes from mail.livedigix.us (67.21.78.228): icmp_seq=3 ttl=64 time=0.052 ms<br/>
64 bytes from mail.livedigix.us (67.21.78.228): icmp_seq=4 ttl=64 time=0.047 ms<br/>
64 bytes from mail.livedigix.us (67.21.78.228): icmp_seq=5 ttl=64 time=0.276 ms<br/>
64 bytes from mail.livedigix.us (67.21.78.228): icmp_seq=6 ttl=64 time=0.053 ms<br/>
64 bytes from mail.livedigix.us (67.21.78.228): icmp_seq=7 ttl=64 time=0.073 ms<br/>
64 bytes from mail.livedigix.us (67.21.78.228): icmp_seq=8 ttl=64 time=0.047 ms<br/>
64 bytes from mail.livedigix.us (67.21.78.228): icmp_seq=9 ttl=64 time=0.054 ms<br/>


and when i check the nslookup i get this result while sshing the server.<br/>
nslookup livedigix.us<br/>
Server:         67.21.78.228<br/>
Address:        67.21.78.228#53<br/>
<br/>
Name:   livedigix.us<br/>
Address: 67.21.78.228<br/>
<br/>
my named.conf file consist this<br/>
<br/>
//<br/>
// named.conf<br/>
//<br/>
// Provided by Red Hat bind package to configure the ISC BIND named(8) DNS<br/>
// server as a caching only nameserver (as a localhost DNS resolver only).<br/>
//<br/>
// See /usr/share/doc/bind*/sample/ for example named configuration files.<br/>
//<br/>
// See the BIND Administrator's Reference Manual (ARM) for details about the<br/>
// configuration located in /usr/share/doc/bind-{version}/Bv9ARM.html<br/>
<br/>
options {<br/>
      listen-on port 53 { 127.0.0.1; 67.21.78.228; };<br/>
      listen-on-v6 port 53 { ::1; };<br/>
      directory       "/var/named";<br/>
      dump-file       "/var/named/data/cache_dump.db";<br/>
      statistics-file "/var/named/data/named_stats.txt";<br/>
      memstatistics-file "/var/named/data/named_mem_stats.txt";<br/>
      allow-query     { localhost; 67.21.78.0/24; };<br/>
        allow-transfer{ localhost; 67.21.78.228; }; <br/>
      /* <br/>
       - If you are building an AUTHORITATIVE DNS server, do NOT enable recursion.<br/>
       - If you are building a RECURSIVE (caching) DNS server, you need to enable
         recursion. <br/>
       - If your recursive DNS server has a public IP address, you MUST enable access <br/>
         control to limit queries to your legitimate users. Failing to do so will
         cause your server to become part of large scale DNS amplification
         attacks. Implementing BCP38 within your network would greatly
         reduce such attack surface <br/>
      */<br/>
      recursion yes;<br/>

      dnssec-enable yes;<br/>
      dnssec-validation yes;<br/>
<br/>
      /* Path to ISC DLV key */<br/>
      bindkeys-file "/etc/named.iscdlv.key";<br/>
<br/>
      managed-keys-directory "/var/named/dynamic";<br/>
<br/>
      pid-file "/run/named/named.pid";<br/>
      session-keyfile "/run/named/session.key";<br/>
};<br/>

logging {<br/>
        channel default_debug {<br/>
                file "data/named.run";<br/>
                severity dynamic;<br/>
        };<br/>
};<br/>
<br/>
zone "livedigix.us" IN {<br/>
type master;<br/>
file "forward.livedigix";<br/>
allow-update { none; };<br/>
};<br/>
zone "78.21.67.in-addr.arpa" IN {<br/>
type master;<br/>
file "reverse.livedigix";<br/>
allow-update { none; };<br/>
};<br/>

<br/>

<br/>
include "/etc/named.rfc1912.zones";<br/>
include "/etc/named.root.key";<br/>

<br/>
<br/>
and the forward.livedigix file consist of this <br/>
vi /var/named/forward.livedigix<br/>
<br/>
$TTL 86400<br/>
@   IN  SOA     ns1.livedigix.us. root.livedigix.us. (<br/>
        2011071001  ;Serial<br/>
        3600        ;Refresh<br/>
        1800        ;Retry<br/>
        604800      ;Expire<br/>
        86400       ;Minimum TTL<br/>
)<br/>
@       IN  NS          ns1.livedigix.us.<br/>
@       IN  NS          ns2.livedigix.us.<br/>
@       IN  A           67.21.78.228<br/>
@       IN  A           67.21.78.228<br/>
<br/>
and reverse.livedigix file consist of this<br/>
vi /var/named/reverse.livedigix<br/>
$TTL 86400<br/>
@   IN  SOA     ns1.livedigix.us. root.livedigix.us. (<br/>
        2011071001  ;Serial<br/>
        3600        ;Refresh<br/>
        1800        ;Retry<br/>
        604800      ;Expire<br/>
        86400       ;Minimum TTL<br/>
)<br/>
@       IN  NS          ns1.livedigix.us.<br/>
@       IN  NS          ns2.livedigix.us.<br/>
@       IN  PTR         livedigix.us.<br/>
ns1     IN  A           67.21.78.228<br/>
ns2     IN  A           67.21.78.228<br/>
<br/>
228     IN  PTR         ns1.livedigix.us.<br/>
228     IN  PTR         ns2.livedigix.us.<br/>
<br/>
and i have my domain registered with godaddy. i updated the nameserver ns1.livedigix.us and ns2.livedigix.us<br/>
<br/>
but when i ping through any cmd without sshing<br/>
i get this error :<br/>
<br/>
admin@admin-PC ~<br/>
$ nslookup livedigix.us<br/>
*** UnKnown can't find livedigix.us: Server failed<br/>
Server:  UnKnown<br/>
Address:  192.168.1.1<br/>
<br/>
and when i ping the server i get this :<br/>
admin@admin-PC ~<br/>
$ ping livedigix.us<br/>
Ping request could not find host livedigix.us. Please check the name and try again.<br/>
<br/>
and yes i have created two host name on godaddy with ns1 and ns2. and pointed it to the ip address.<br/>
All i am trying is to point the domain to the vps. I am a newbie and i dont know where is the probelm. Any help would be appreciated. Thanks<br/>
ASKER CERTIFIED SOLUTION
nociSoftware Engineer
Join our community to see this answer!
Unlock 1 Answer and 7 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 7 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros