In article ,
John Wobus wrote:
> I will add my +1:
>
> NXDOMAIN does not mean "I don't have a number for that name but
> someone else
> might." It means "The DNS lists this name as having no number (or
> whatever)."
> There's no more reason to look further than if you got a positive
> answe
I will add my +1:
NXDOMAIN does not mean "I don't have a number for that name but
someone else
might." It means "The DNS lists this name as having no number (or
whatever)."
There's no more reason to look further than if you got a positive
answer from one server and still wondered if some oth
On 31.05.13 16:41, sumsum 2000 wrote:
The google DNS server was only examples.. it can be some internal DNS
servers and external DNS servers. For eg 10.10.10.10; 120.10.13.12 etc.
where the DNS requests are being forwarded to..
Then it was bad example. You use "type forward" when you want to as
Hi,
The google DNS server was only examples.. it can be some internal DNS
servers and external DNS servers. For eg 10.10.10.10; 120.10.13.12 etc.
where the DNS requests are being forwarded to..
There are issues with connectivity where the DNS entries are not synced up.
And these entries are all sp
On 30.05.13 12:56, sumsum 2000 wrote:
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;
};
On 30.05.13 15:00, sum
In article ,
Ashok Agarwal wrote:
> Sorry, its not */etc/hosts* file rather its */etc/resolv.conf*.
>
>
> On Thu, May 30, 2013 at 1:25 PM, Ashok Agarwal
> wrote:
>
> > One possible way can also be to set the number of nameservers to be looked
> > upon in the /etc/hosts file.
> >
> > nameserve
So your administrator is breaking DNS if all 3 servers have been added
as NS records but the zone is not available on all 3 servers. Get
him/her to fix your DNS hierarchy first then you wont need to check
which server is hosting the subdomain.
Steve
On 30 May 2013 10:30, sumsum 2000 wrote:
> Hi
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
Well you can do that.
It does not change the fact that NXDOMAIN is a DEFINITIVE answer - it
does not exist, there is no reason to look further.
On 30/05/13 9:56, Ashok Agarwal wrote:
> Sorry, its not */etc/hosts* file rather its */etc/resolv.conf*.
>
>
> On Thu, May 30, 2013 at 1:25 PM, Ashok Ag
Sorry, its not */etc/hosts* file rather its */etc/resolv.conf*.
On Thu, May 30, 2013 at 1:25 PM, Ashok Agarwal
wrote:
> One possible way can also be to set the number of nameservers to be looked
> upon in the /etc/hosts file.
>
> nameserver 8.8.8.8
> nameserver 4.4.2.2
> nameserver 4.1.2.2
>
> R
One possible way can also be to set the number of nameservers to be looked
upon in the /etc/hosts file.
nameserver 8.8.8.8
nameserver 4.4.2.2
nameserver 4.1.2.2
Regards,
Ashok
On Thu, May 30, 2013 at 1:05 PM, Steven Carr wrote:
> It's not possible. NXDOMAIN is NXDOMAIN, it doesn't exist, it d
It's not possible. NXDOMAIN is NXDOMAIN, it doesn't exist, it doesn't
mean try another server to see if you get lucky next time.
Steve
On 30 May 2013 08:26, sumsum 2000 wrote:
> Hi,
> I have the following change to be available from BIND9.
>
> I have zone forwarders as follows with BIND9 setup
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;
};
13 matches
Mail list logo
