Re: [CentOS] BIND Setup Issue

2013-03-10 Thread Earl Ramirez
On Sun, 2013-03-10 at 17:27 +0530, Austin Einter wrote: > Dear All > I have a CentOS 6.3 machine. I am trying to setup DNS BIND setup in that > machine. It is having a static global IP. I have done lot of reading , > google search and tried all possible option, but still not able to resolve > the i

Re: [CentOS] BIND Setup Issue

2013-03-10 Thread Austin Einter
Dear All My resolv.conf looks as below search netcloudjobs.com nameserver 10.0.0.1 nameserver 8.8.8.8 nameserver 127.0.0.1 I do not have any error logs. I just did one modification in named.conf. *allow-query { localhost; 10.0.0.1/24; 10.0.0.254/24; }; * *Line I modified to * *allow-query

Re: [CentOS] BIND Setup Issue

2013-03-10 Thread Robert Moskowitz
On 03/10/2013 07:57 AM, Austin Einter wrote: > Dear All > I have a CentOS 6.3 machine. I am trying to setup DNS BIND setup in that > machine. It is having a static global IP. I have done lot of reading , > google search and tried all possible option, but still not able to resolve > the issue. > >

Re: [CentOS] BIND Setup Issue

2013-03-10 Thread Austin Einter
My registrar is Godad.com, looks they have registered nameservers ns1.netcloudjobs.com and ns2.netcloudjobs.com Now I am able to resolve to ns1.netcloudjobs.com I have only 1 IP address that x.x.x.43 , so I can not use x.x.x.44 >From my dedicated server, if I ping to www.netcloudjobs.com , it says

Re: [CentOS] BIND Setup Issue

2013-03-10 Thread Peter Eckel
Hi Austin, since your A record is fine and can be resolved, the issue is obviously not BIND related but lies somewhere in your network/firewall configuration. The last address that is visible in the tracereoute output from here is > 15 ip-208-109-113-174.ip.secureserver.net (208.109.113.174)

Re: [CentOS] BIND Setup Issue

2013-03-10 Thread Arek Czereszewski
Put this in a zone file: netcloudjob.com. IN A 173.201.189.43 Just after a MX line 10 mar 2013 14:51, "Austin Einter" napisaƂ(a): > My registrar is Godad.com, looks they have registered nameservers > ns1.netcloudjobs.com and ns2.netcloudjobs.com > Now I am able to resolve to ns1.netcloudjobs.com

Re: [CentOS] BIND Setup Issue

2013-03-10 Thread Peter Eckel
On 10.03.2013, at 16:14, Arek Czereszewski 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. The name can already be resolved, and the address cannot be pinged either. I checked before I replied. _

Re: [CentOS] BIND Setup Issue

2013-03-10 Thread Robert Moskowitz
On 03/10/2013 10:19 AM, Peter Eckel wrote: > Hi Austin, > > since your A record is fine and can be resolved, the issue is obviously not > BIND related but lies somewhere in your network/firewall configuration. > > The last address that is visible in the tracereoute output from here is > >> 15 ip

Re: [CentOS] BIND Setup Issue

2013-03-10 Thread Tilman Schmidt
Am 10.03.2013 12:57, schrieb Austin Einter: > I have a CentOS 6.3 machine. I am trying to setup DNS BIND setup in that > machine. It is having a static global IP. I have done lot of reading , > google search and tried all possible option, but still not able to resolve > the issue. After reading th

Re: [CentOS] BIND Setup Issue

2013-03-10 Thread Tilman Schmidt
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 --- >

Re: [CentOS] BIND Setup Issue

2013-03-10 Thread Tilman Schmidt
Am 10.03.2013 16:34, schrieb Peter Eckel: > On 10.03.2013, at 16:14, Arek Czereszewski 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 nam

Re: [CentOS] BIND Setup Issue

2013-03-10 Thread Austin Einter
Dear All Thanks for great support. Now the issue is completely resolved. I had to add "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.c