On Monday 29 September 2003 1:17 am, Jacob Anawalt wrote:
>Do you want other computers in the network to look to themselves or the
>dns server for resolution of the reverse dns zone?
>
>@ IN NS server.elkins
>
>I think it's odd that you had to uninstall/reinstall bind I've not yet
>had that issue
Jeff Elkins wrote:
On Saturday 27 September 2003 9:10 am, Jeff Elkins wrote:
What is a missing ptr?
OK, to named.conf I added:
zone "192.in-addr.arpa" {
type master;
file "/etc/bind/db.192";
};
A minor note, I'd write db.192 as db.192.168.0, so that if you have
another p
On Saturday 27 September 2003 9:10 am, Jeff Elkins wrote:
>What is a missing ptr?
OK, to named.conf I added:
zone "192.in-addr.arpa" {
type master;
file "/etc/bind/db.192";
};
and /etc/bind/db.192 contains:
;
; BIND reverse data file for 192.168.0.0
;
$TTL604800
@ IN
On Saturday 27 September 2003 5:43 am, Stephen Patterson wrote:
>On Sat, 27 Sep 2003 04:30:26 +0200, Jeff Elkins wrote:
>> On my personal server, bind has quit working.
>>
>> Previously, I had a caching nameserver running at 192.168.0.1 that also
>> resolved local n
On Sat, 27 Sep 2003 04:30:26 +0200, Jeff Elkins wrote:
> On my personal server, bind has quit working.
>
> Previously, I had a caching nameserver running at 192.168.0.1 that also
> resolved local names on my internal network. I was futzing around with
> fetchmail/mailfilter
On my personal server, bind has quit working.
Previously, I had a caching nameserver running at 192.168.0.1 that also
resolved local names on my internal network. I was futzing around with
fetchmail/mailfilter and decided to reboot the server. On reboot, dns no
longer works, unless I point
On my personal server, bind has quit working.
Previously, I had a caching nameserver running at 192.168.0.1 that also
resolved local names on my internal network. I was futzing around with
fetchmail/mailfilter and decided to reboot the server. On reboot, dns no
longer works, unless I point
7 matches
Mail list logo