Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I'm trying to move all my websites to a VPS that I hired.
(CentOS Linux 5.4)
To create my DNS server I'm using co.cc addresses (free domains) for test until I get a correct configuration.
What I am trying to do is this:
I create in co.cc site the domain aaa.co.cc and configure the ZONE RECORD:
aaa.co.cc A 111.111.111.111
ns1.aaa.co.cc A 111.111.111.111
ns2.aaa.co.cc A 111.111.111.111
(names and ips showed here are fictitious, of course)
Also I create bbb.co.cc domain and configure the Service Type as "name server DNS" to:
ns1.aaa.co.cc
ns2.aaa.co.cc
In my VPS server configure BIND:
Create MASTER ZONE aaa.co.cc:
aaa.co.cc. A 111.111.111.111
ns1.aaa.co.cc. A 111.111.111.111
ns2.aaa.co.cc. A 111.111.111.111
aaa.co.cc. NS Default ns1.aaa.co.cc.
Create MASTER ZONE bbb.co.cc:
bbb.co.cc A 111.111.111.111
bbb.co.cc NS Default ns1.aaa.co.cc.
And I create in my Apache 2 Virtual Hosts, one for aaa.co.cc and another for bbb.co.cc. Each with its path and a test index.html file in each home.
I also open port 53 for TCP and UDP on firewall.
Obviously I can "dig" to aaa.co.cc and all is right, but when I dig bbb.co.cc it says:
;; Connection timed out, no servers could be reached
When I dig @localhost everything seems to be ok...
Am I making a big mistake?
I already know that ns1 and ns2 have the same IP, but I want to see if my idea works before "buying" another IP.
Any idea for me?
Thank you very much for your patience and sorry for my accent.
Can you provide us with your named.conf and the complete zone files, not just parts of it. What you put in your post shows that you have records in your zone file, but there should be a lot more.
Thank you very much for your interest, but last night (about 2:30 h) after 10 days working arround this problem I had a good idea.... I scaned the port 53 and guess what....
The VPS provider has filtered this port.
Well, it's a 5$ /mo VPS so I will look for another system.
Any way, to scan the port should have been first thing to do, isn't it?
Well, I guess you better checked with the provider if they supported this. But it is always a good thing to check your configurations, especially when it is about firewalls.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.