Reverse zone not working???
/dev/rob0
rob0 at gmx.co.uk
Tue Aug 9 20:32:31 UTC 2005
On Sunday 2005-August-07 08:57, sharabi2 at gmail.com wrote:
> This is the following I have in my named.conf file
>
>/// zone "134.168.192.IN-ADDR.ARPA" {
I don't agree with Sten about the period. I don't put periods at the
ends of my zone names in named.conf.
> type master;
> file "db.192.168.134";
> allow-update{ update-nets; };
> allow-query{ query-nets;};
> };
Nothing obviously wrong here. But if 'file "db.192.168.134"' does not
exist, and if ACL's update-nets and query-nets have not been defined,
the zone won't load.
> and this is my zone file
>
> $TTL 86400
> @ IN SOA IN SOA ns1.domain.org. nic-admin.domain.org. (
^^^^^^
Why is "IN SOA" repeated? Try named-checkzone(8) on this file. Again,
nothing else leaps out as being wrong, but I imagine that is enough.
> root at sun2:/usr/local/named >host -v 192.168.134.99
> Trying "99.134.168.192.in-addr.arpa"
> Host 99.134.168.192.in-addr.arpa not found: 2(SERVFAIL)
> Received 45 bytes from 192.168.101.103#53 in 2 ms
named logs to a higher priority, I think WARN, when errors occur.
Servfail usually means that your zone did not load, and that error is
in your logs.
--
mail to this address is discarded unless "/dev/rob0"
or "not-spam" is in Subject: header
More information about the bind-users
mailing list