Oh yeah, here is the archive with that diff. http://www.mail-archive.com/[email protected]/msg00373.html
Basically I just added this...
".".$domain.":".$soa['tldhost']."::".$soa['ttl']."\n".
in front of the "Z" export line in src/functions.php line 613.
On Apr 19, 2005, at 9:55 PM, David Bryan wrote:
In the previous post, and from the first link here, your missing something possible very crucial, the reverse has to authoritative data.
EG:
.4.3.2.1.in-addr.arpa ^ | -------- the first dot is important.
I sent a diff to the list for 1.1.3 code that just sticks a "." entry in for each domain so that tinydns knows that it should hand out information for that domain. This is really a poor hack, but should also include all nameservers, not just the one in the SOA. The SOA does not really tell tinydns that it should hand out the dns info...
If you could send us some logs from the dns query that would be great! ( http://dqd.com/~mayoff/notes/djbdns/tinydns-log.html )
On Apr 19, 2005, at 8:43 PM, Jeremy Gray wrote:
I think my problem has to do with what is mentioned about HE.net requirements here:
http://www.futurahost.it/webs.new/main/info/tec/tinydns_reverse.php? select_language=it
Here is guide on getting reverse DNS working with HE.net:
http://www.he.net/adm/reverse.dns.html
On that note... is it possible to add manual entries to the data file & still be able to use VegaDNS?
