new here

2012-05-02 Thread David
Hello All, I am new here but have been watching the list for a while. I run a small WISP and we have just moved to a new carrier. They have provided us with a cdir ipv4 block of /22 and a /23. I am trying to get my reverse DNS working correctly but they will not point their servers to my

Re: new here

2012-05-02 Thread btb
On 2012.05.02 13.01, David wrote: Hello All, I am new here but have been watching the list for a while. I run a small WISP and we have just moved to a new carrier. They have provided us with a cdir ipv4 block of /22 and a /23. I am trying to get my reverse DNS working correctly

Re: new here

2012-05-02 Thread Ben Croswell
than you are loading it as. You load 104.16.98.in-addr.arpa. they are transferring 104-22.16.98.in-addr.arpa. -Ben Croswell On May 2, 2012 1:18 PM, David dmilho...@wletc.com wrote: ** Hello All, I am new here but have been watching the list for a while. I run a small WISP and we have just moved

Re: new here

2012-05-02 Thread john
Hi David, I think first your ISP needs to fix there delegation. If we look at their chain we see dig ns 16.98.in-addr.arpa +short ns2-auth.windstream.net. ns1-auth.windstream.net. ns4-auth.windstream.net. ns3-auth.windstream.net. however the authoritive server has a different set dig ns

Re: new here

2012-05-02 Thread btb
On May 02, 2012, at 14.41, David wrote: so far they are telling me that their systems require the forwards. I think they have it backwards.. please keep replies on the list. yes, it certainly seems so. if you indeed have been assigned a /22 and a /23, then a number of things should happen

new here

2012-04-22 Thread David Milholen
I am a Wisp admin and I have just configured a couple of new Bind9 servers. They will resolve using dig google.com @9x.1xx.104.14 I am having some trouble getting them to answer themselves on 127.0.0.1 for example: [root@ns4 named]# dig google.com @127.0.0.1 +trace ; DiG

Re: new here

2012-04-22 Thread Larry Brower
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 04/22/2012 10:05 PM, David Milholen wrote: listen-on { 9x.1xx.104.14; }; Perhaps add 127.0.0.1; into the listen on clause. - -- Larry Brower, CCENT Fedora Ambassador - North America Fedora Quality Assurance

Re: new here

2012-04-22 Thread Ben Croswell
You set a listen-on that does not include 127.0.0.1. On Apr 22, 2012 11:08 PM, David Milholen dmilho...@wletc.com wrote: I am a Wisp admin and I have just configured a couple of new Bind9 servers. They will resolve using dig google.com @9x.1xx.104.14 I am having some trouble getting them to