Am 10.03.2013 14:50, schrieb Austin Einter:
From my dedicated server, if I ping to www.netcloudjobs.com , it says
*[root@ip-173-201-189-43 named]# ping www.netcloudjobs.com PING www.netcloudjobs.com (173.201.189.43) 56(84) bytes of data. ^C --- www.netcloudjobs.com ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2217ms*
But if ping to netcloudjobs.com, it says
[root@ip-173-201-189-43 named]#
*[root@ip-173-201-189-43 named]# ping netcloudjobs.com ping: unknown host netcloudjobs.com [root@ip-173-201-189-43 named]#
It seems you already fixed that and just forgot to tell the list.
My corresponding zone file looks as below
*[root@ip-173-201-189-43 named]# vi netcloudjobs.com.fwd $TTL 86400 @ IN SOA ns1.netcloudjobs.com. root.netcloudjobs.com. ( 2041071002 ;Serial 3600 ;Refresh 1800 ;Retry 604800 ;Expire 86400 ;Minimum TTL )
@ IN NS ns1.netcloudjobs.com. @ IN NS ns2.netcloudjobs.com. @ IN MX 0 mail.netcloudjobs.com.
ns1 IN A 173.201.189.43 ns2 IN A 173.201.189.43 www IN A 173.201.189.43 mail IN A 173.201.189.43
This zone file does not contain an A RR for netcloudjobs.com itself, but if I dig netcloudjobs.com now I do get one. So obviously you have added it it the meantime.
Can somebody kindly tell me what I need to do so that, from my dedicated server I can ping to netcloudjobs.com
Generally speaking: 1. fix the name resolution (you already did that) 2. fix the network connectivity and/or firewall issues preventing your ping packets from getting through
HTH T.