July 15th, 2003, 11:57 AM
I tried djbdns and it seems to be working, but I'm apparently not understanding something fundamental here.
This is my data file:
This is what http://checkdns.net says:
DNS server a.ns.mbtimatch.com[220.127.116.11] is alive and authoritative for domain mbtimatch.com
Error fetching SOA from b.ns.mbtimatch.com [18.104.22.168]: Connection reset. Probably DNS server is offline.
Why is b.ns.mbtimatch.com not alive? It seems to be configured just the same as a.ns.mbtimatch.com.
Also, when I ping mbtimatch.com, I'm told that its IP address is 22.214.171.124. When I go to 126.96.36.199 using a web browser, I see my home page, but when I go to mbtimatch.com using a web browser, I get a "cannot find server" error. Why?
I'm sorry if these are stupid questions, but I've been trying to get this to work for about two weeks now, and it doesn't look like I'm going to find better info online than I already have any time soon. It would be a big help if someone more knowledgeable answered my questions directly.
July 15th, 2003, 03:31 PM
checkdns.net speaketh the truth. I can get an SOA response from 188.8.131.52 but not from 184.108.40.206.
Are you using one machine with two IP addresses for a.ns.mbtimatch.com and b.ns.mbtimatch.com, or two separate machines?
When DNS clients try to resolve a domain name, they pick one of the designated authorative servers randomly and send it the query. Evidently, your ping command picked the server that worked, and your browser didn't. The fact that it was a browser that failed is irrelevant - I was able to call up your site (Apache index of rationalromance.com) in my browser by entering mbtimatch.com
July 15th, 2003, 04:19 PM
I'm using one machine with two IP addresses.
July 15th, 2003, 04:44 PM
OK, I'm assuming that you didn't run tinydns-conf a second time for the second IP address (please correct me if I'm wrong).
To do this, run the following commands:
assuming that Gtinydns and Gdnslog are your tinydns and dnslog users respectively (change them if different).
tinydns-conf Gtinydns Gdnslog /etc/tinydns2 220.127.116.11
rm -rf root
ln -s /etc/tinydns/root .
ln -s /etc/tinydns2 /service
The above command will set up a new directory for your second instance of tinydns listening on the second IP address, publishing the same data as the first tinydns instance (hence the symlink to its root).
You can check if it's working correctly with:
This should give you an uptime greater than 1 second for /service/tinydns2
July 15th, 2003, 05:07 PM
You're right, I didn't do that. Your solution worked. Thank you very much.
July 15th, 2003, 06:31 PM