On Fri, Dec 6, 2013 at 6:12 PM, Matus UHLAR - fantomas wrote:
> On 06.12.13 15:52, sumsum 2000 wrote:
>
>> I am having only a forward only option in bind configuration.
>> When i dig on some host which has CNAME, the cache contains a longer TTL
>> for the CNAME tha
Hi,
I am having only a forward only option in bind configuration.
When i dig on some host which has CNAME, the cache contains a longer TTL
for the CNAME than the TTL for the final resolution of the IP.
However, in the example below, the CNAME is queried again when the TTL
for a336.g.akamai.net
Yes, i do have other zones beside makemytrip.com. Thanks for the info
On Thu, Aug 22, 2013 at 5:11 PM, Barry Margolin wrote:
> In article ,
> sumsum 2000 wrote:
>
> > This is my configuration for positive and negative cache TTL.
> >
> >
This is my configuration for positive and negative cache TTL.
view "newDNS" IN {
max-cache-ttl 300;
max-ncache-ttl 200;
zone "makemytrip.com" IN {
type forward;
it
is not configured correctly.
On Tue, Aug 20, 2013 at 6:07 PM, Matus UHLAR - fantomas
wrote:
> On 20.08.13 15:42, sumsum 2000 wrote:
>>>
>>>>zone "7.7.7.7.in-addr.arpa" IN {
>>>>type forward;
OAb.in-addr-servers.arpa.
nstld.iana.org. 2011029209 1800 900 604800 3600
;; Query time: 326 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Aug 20 15:49:29 2013
;; MSG SIZE rcvd: 106
On Tue, Aug 20, 2013 at 3:49 PM, Matus UHLAR - fantomas
wrote:
> On 20.08.13 15:42, su
Hi,
I have the following zone configuration for forwarding DNS query
view "default" IN {
max-cache-ttl 604800;
max-ncache-ttl 10800;
zone "." IN {
type forward;
fic case.
Could you please help on this.
On Tue, Jul 9, 2013 at 1:03 PM, Matus UHLAR - fantomas wrote:
> On 09.07.13 11:51, sumsum 2000 wrote:
>
>> I have a reverse lookup zone file configuration as follows:
>> zone "0/24.110.252.173.in-addr.**arpa" {
>>
> [
Thanks for the info
On Tue, Jul 9, 2013 at 1:03 PM, Matus UHLAR - fantomas wrote:
> On 09.07.13 11:51, sumsum 2000 wrote:
>
>> I have a reverse lookup zone file configuration as follows:
>> zone "0/24.110.252.173.in-addr.**arpa" {
>>
> [...]
>
> When
What I am trying to achieve is this:
I am using BIND9 only for forwarding DNS requests to other DNS Servers.
I want the entire hosts in the
network : 173.252.110.0
with the host range: 173.252.110.1 - 173.252.110.254
with a total 254 addresses to be sent for reverse lookup say to DNS :
8.8.8.
I have a reverse lookup zone file configuration as follows:
zone "0/24.110.252.173.in-addr.arpa" {
type forward; forward only;
forwarders {10.10.96.1;};
};
When I do dig -x 172.252.110.27, I expect it to forward it to
10.10.96.1, but instead, it uses the default resolver.
Am I mi
.13.12 for example.. i try 10.10.10.10 - NXDOMAIN
returned.. i want to try 120.10.13.12 before sending NXDOMAIN to my initial
request.
I hope this helps.
Thanks
On Fri, May 31, 2013 at 1:05 PM, Matus UHLAR - fantomas
wrote:
> On 30.05.13 12:56, sumsum 2000 wrote:
>
>> I have zone forw
Hi,
This is a non-standard behavior and I would like to have the following:
In the case where I am working on,
/etc/resolv.conf contains localhost 127.0.0.1 and BIND is listening on
localhost port 53 as non-authoritative DNS
So all the requests are sent through 127.0.0.1 and based on the domai
Hi,
I have the following change to be available from BIND9.
I have zone forwarders as follows with BIND9 setup with forward only option
on a Non Authoritative DNS server
zone "mytestdomain101.com" IN {
type forward;
forwarders {8.8.8.8;4.2.2.1;8.8.4.4};
forward only;
};
14 matches
Mail list logo
