Re: Reverse DNS problem after bind upgrade(?)

1999-12-31 Thread aphro
yeah.. what caught me off gaurd was the fact that there was other machines (at the isp that gives us service) that need to get the zone info from *us* for our reverse ns lookups. they changed ips on me without telling and my acl's were denying the zone transfers from happening. bastards! thanks!

Re: Reverse DNS problem after bind upgrade(?)

1999-12-31 Thread Nate Duehr
Hi Nate, Don't have any answers for your BIND issue with reverse lookups, but you've been kind enough to help me on a couple of things in the past, and I wanted to mention that you should probably look into the "notify" stuff, specifically the "also-notify" statement for named.conf so your serv

Re: Reverse DNS problem after bind upgrade(?)

1999-12-28 Thread aphro
On Mon, 27 Dec 1999, Alvin Oga wrote: aoga >a. did you check resolv.conf yes.. aoga > aoga >b. did you restart named ? many times..updated the serial numbers etc etc.. aoga > aoga >c. if you only use 208.222.179.31 as your dns server... aoga >than does reverse work ?? yes aoga > aog

Re: Reverse DNS problem after bind upgrade(?)

1999-12-27 Thread Alvin Oga
hi... a. did you check resolv.conf b. did you restart named ? c. if you only use 208.222.179.31 as your dns server... than does reverse work ?? d. are you running secondary on localhost from 208.222.179.31 e. was it using named.boot before and now its using named.conf ? have fun

Reverse DNS problem after bind upgrade(?)

1999-12-27 Thread aphro
for some reason other servers cannot reverse resolve my ips anymore after a recent bind upgrade, however when asking my server it works fine.. [EMAIL PROTECTED] /usr/local/games] nslookup Default Server: localhost Address: 127.0.0.1 > 208.222.179.1 Server: localhost Address: 127.0.0.1 *** lo