Is it possible to set query-source to all? I'm using AMAZON EC2 and I want to setup a DNS Server. I just notice it was
bind to private ip address. Since the public ip address was not on the OS ( probably a NAT define by AMAZON), I cannot
connect to it even just a telnet. When I do netstat:
tcp
From the lack of response, I take it that there is no good way to have BIND
trigger an external database update (or other action) when it receives a DDNS
update. At least not without significantly customizing BIND, similar to what
Quadritec / Lucent / Alcatel-Lucent did with QIP.
Enhancing
Hi all,
This is probably somewhat of an un-legit way of using whois but I'm
curious as to whether it would be possible to install an internal
whois server that responds with the appropriate prefix-data upon
request for internal ip-numbers/domains while forwarding unknown
requests to external
We are having 2 sites at different locations now with a DNS resolver on
each site. Internet speed between those two different ISPs is very fast,
and the hosts to resolve will be about the same because of similar
services.
My idea is to use
forward X;
on site Y and
forward Y;
on site X, but,
E Johnson wrote:
From what I have read so far, I can see that this might be a very
flame-worthy question, so please don't hurt me, I'm just a beginner...
I have read every howto that I can find on setting up a DNS server for
a very small, 12 seats, network. The DNS server just needs to be
Problem solved. It was misconfigured on the AMAZON EC2. I have no access to it
so I have to wait for the manager.
Nelson
Cathy Almond wrote:
Nelson Serafica wrote:
Is it possible to set query-source to all? I'm using AMAZON EC2 and I
want to setup a DNS Server. I just notice it was bind to
Currently I have primary (ns1) and secondary (ns2) dns on the same network. I'm now doing redundancy and planning to put
secondary to another isp. I have now setup the new secondary dns on the another network.
I change the allow-transfer { 1.2.3.4; localhost; }; to allow-transfer { 5.6.7.8;
In message 4a808228.2080...@dougbarton.us, Doug Barton writes:
Michael Monnerie wrote:
We are having 2 sites at different locations now with a DNS resolver on
each site. Internet speed between those two different ISPs is very fast,
and the hosts to resolve will be about the same because
Last year, there was a global threat about cache poisoning so I updated immediately my bind. I update it to BIND
9.5.0-P1 and did nothing to its named.conf
Now, I'm setting up a secondary dns (in my previous emails) and I used BIND 9.6.1-P1. But when I do dig +short @NS2 IP
In message 4a80e783.4090...@gmail.com, Nelson Serafica writes:
Last year, there was a global threat about cache poisoning so I updated immed
iately my bind. I update it to BIND
9.5.0-P1 and did nothing to its named.conf
You should have at least checked the query-source clauses
Thanks Mark! it works. I change my query source to one of the entry below and
it works.
Mark Andrews wrote:
query-source * port 53; // bad
query-source 10.53.0.1; // ok
query-source *; // ok (default)
query-source-v6 * port 53; // bad
On Aug 10, 2009, at 10:06 PM, Nelson Serafica wrote:
Thanks Mark! it works. I change my query source to one of the entry
below and it works.
Maybe a strange question. Why did you have a query source statement
in your configuration in the first place?
Bill Larson
Mark Andrews wrote:
I need to set bind to listen to all address. I'm using AMAZON EC2
Maybe a strange question. Why did you have a query source statement in
your configuration in the first place?
___
bind-users mailing list
bind-users@lists.isc.org
13 matches
Mail list logo
