Dear All Thanks for great support.
Now the issue is completely resolved.
I had to add "netcloudjob.com http://netcloudjob.com. IN A 173.201.189.43" line in forward zone file. (As suggested by Arzek)perly.
Now from remote locations we are able to ping to www.netcloudjobs.com and netcloudjobs.com .
Thanks a lot all.
Best Regards Austin
On Mon, Mar 11, 2013 at 5:05 AM, Tilman Schmidt < t.schmidt@phoenixsoftware.de> wrote:
Am 10.03.2013 16:34, schrieb Peter Eckel:
On 10.03.2013, at 16:14, Arek Czereszewski arekczer@gmail.com wrote:
Put this in a zone file: netcloudjob.com. IN A 173.201.189.43
Just after a MX line
Austin already did that, and it doesn't help.
Yes it does. The name can now be resolved.
The name can already be resolved,
Only since he added the A RR.
and the address cannot be pinged either. I checked before I replied.
That's a separate problem, and has nothing to do with BIND. What's more, given the complete lack of information about the network topology and involved components, we cannot even guess what may be the issue here. Routing? Firewall? NAT? Hardware? Everything's possible.
-- Tilman Schmidt Phoenix Software GmbH Bonn, Germany
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos