answer when our own local nameserver can't figure
> it out.
>
>
>
> Date: Tue, 18 Sep 2012 11:18:58 -0400
> From: k...@chrysler.com
> To: bind-users@lists.isc.org
> Subject: Re: question about how a particular dig works ...
>
> On 9/18/2012 9:45 AM, M. Me
-0400
From: k...@chrysler.com
To: bind-users@lists.isc.org
Subject: Re: question about how a particular dig works ...
On 9/18/2012 9:45 AM, M. Meadows wrote:
dig www.careerone.com.au <http://www.careerone.com.au> +short @8.8.8.8
www.careerone.com.au.edgesuite.net
<ht
results? Just curious why google and some other public facing dns servers get
an answer when our own local nameserver can't figure it out.
Date: Tue, 18 Sep 2012 11:18:58 -0400
From: k...@chrysler.com
To: bind-users@lists.isc.org
Subject: Re: question about how a particular dig works ...
On 9/18/2012 9:45 AM, M. Meadows wrote:
dig www.careerone.com.au +short @8.8.8.8
www.careerone.com.au.edgesuite.net.
a903.g.akamai.net.
208.44.23.99
208.44.23.121
Why does the above dig work when
dig careerone.com.au +nssearch @8.8.8.8
SOA dns0.news.com.au. hostmaster.news.com.au. 2012082200 3
On Tue, Sep 18, 2012 at 10:43:47AM -0400, M. Meadows wrote:
> And as you point out it has a cname at the apex ... which I thought
> was not allowed.
named will not accept it, and indeed, it is a violation of DNS
standards. Other DNS implementations might allow it, however.
> Isn't it true that
ile is for www.careerone.com.au ... how does
the cname record get defined and loaded successfully?
> Subject: Re: question about how a particular dig works ...
> From: niall.orei...@ucd.ie
> Date: Tue, 18 Sep 2012 15:22:40 +0100
> CC: bind-users@lists.isc.org
> To: sun-g...@live.c
On 18 Sep 2012, at 14:45, M. Meadows wrote:
> dig www.careerone.com.au +short @8.8.8.8
> www.careerone.com.au.edgesuite.net.
> a903.g.akamai.net.
> 208.44.23.99
> 208.44.23.121
>
> Why does the above dig work when
If you try
dig +trace www.careerone.com.au
you'll find that t
7 matches
Mail list logo
