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
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 16.98.in
Allow-transfer is not the same as forwarding.
Are they wanting to secondary from you?
If so you need to ensure they can do queries against your master for the
zones so they can request soa to check the serial number.
Also it appears they are trying to xfer the cidr block with a different
name th
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 but they will no
You set a listen-on that does not include 127.0.0.1.
On Apr 22, 2012 11:08 PM, "David Milholen" 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 answer themsel
-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
lbro..
6 matches
Mail list logo
