Subdomains Multi Server Setup

chrisrandell

Verified User
Joined
Mar 14, 2007
Messages
24
Hi there, i have a really interesting mind boggeling issue with my DNS,

Yesterday we brought a second server online.. so i moved my ns2 to the second server... corrected the entries in my name registrar, updated my A records on both servers... and turned the multi server option ON .

Then i sat back and waited... last night i had a client tell me his site was up and down... so i checked and sure enough up and down up and down... at first thought i concluded it was a propergation error with the new name servers. and left it for the night, this morning i decided to check, seems that all my clients who are sub domained arent working correctly.....

i did some tests from dnsstuff.com

------------

Generated by www.DNSstuff.com at 18:01:02 GMT on 03 Jul 2007.

How I am searching:

Searching for freelancer-discovery.real-hosts.ca A record at g.root-servers.net [192.112.36.4]: Got referral to CA01.CIRA.ca. (zone: ca.) [took 41 ms]
Searching for freelancer-discovery.real-hosts.ca A record at CA01.CIRA.ca. [192.228.27.11]: Got referral to ns2.real-hosts.ca. (zone: real-hosts.ca.) [took 54 ms]
Searching for freelancer-discovery.real-hosts.ca A record at ns2.real-hosts.ca. [195.178.107.75]: Reports that no A records exist. [took 115 ms] Response: No A records exist for freelancer-discovery.real-hosts.ca, and freelancer-discovery.real-hosts.ca does not exist. [Neg TTL=14400 seconds] Details: ns2.real-hosts.ca. (an authoritative nameserver for real-hosts.ca.) says that there are no A records for freelancer-discovery.real-hosts.ca, and that the hostname freelancer-discovery.real-hosts.ca does not exist. The E-mail address in charge of the real-hosts.ca. zone is: [email protected].
There is no need to refresh the page -- to see the DNS traversal, to make sure that all DNS servers are reporting the same results, you can Click Here. Note that these results are obtained in real-time, meaning that these are not cached results. These results are what DNS resolvers all over the world will see right now (unless they have cached information).


---------

I refresh acouple of times and get

How I am searching:

Searching for freelancer-discovery.real-hosts.ca A record at a.root-servers.net [198.41.0.4]: Got referral to CA01.CIRA.ca. (zone: ca.) [took 39 ms]
Searching for freelancer-discovery.real-hosts.ca A record at CA01.CIRA.ca. [192.228.27.11]: Got referral to ns1.real-hosts.ca. (zone: real-hosts.ca.) [took 54 ms]
Searching for freelancer-discovery.real-hosts.ca A record at ns1.real-hosts.ca. [195.178.106.20]: Reports freelancer-discovery.real-hosts.ca. [took 113 ms] Response:
Domain Type Class TTL Answer
freelancer-discovery.real-hosts.ca. A IN 14400 195.178.106.20
freelancer-discovery.real-hosts.ca. NS IN 14400 ns2.real-hosts.ca.
freelancer-discovery.real-hosts.ca. NS IN 14400 ns1.real-hosts.ca.
ns1.real-hosts.ca. A IN 14400 195.178.106.20
ns2.real-hosts.ca. A IN 14400 195.178.107.75


--------------------------


any insight into this problem would be greatly apperciated :)


Chris
 
After reading more and more problems with DNS's , searching the forums i came across a thread that had this code

echo "action=rewrite&value=named" >> /usr/local/directadmin/data/task.queue


and it seems to have helped but i will keep you guys informed
 
Back
Top