Re: Another Reverse lookup problem
Chris Hastie <[email protected]>
| Newsgroups | gmane.network.dns.bind9.dlz |
|---|---|
| Message-ID | <[email protected]> |
On 03/09/08 15:53, Rémy Cloutier wrote: > Hello, > I haven't found clues or answers in the archives so here's my situation. > My entries for reverse lookup in the std config of named look like that and > work fine: > > [...] > 66.64/26.78.15.64.in-addr.arpa. IN PTR parcometre.ca. > 67.64/26.78.15.64.in-addr.arpa. IN PTR ns1.parcometre.ca. > [...] > > Now i'm trying to reproduce the same config in the mysql DB using dlz and > it's not working. > The result is: ** server can't find 66.78.15.64.in-addr.arpa: NXDOMAIN > > It works only if i use this format: > 66 IN PTR parcometre.ca. > but i would have to use the $ORIGIN symbol witch is not supported, i think > due to third level dns. > So far as I can make out, the zone 64/26.78.15.64.in-addr.arpa. is delegated to your nameserver. You need to set up the records such that the zone is 64/26.78.15.64.in-addr.arpa and the host is 66. How you do this depends on your database schema, but it is no different to how you would set up a zone parcometre.ca with a host ns1, or a host @. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/