@lists.isc.org
Subject: Re: Dig for link-local
Transport has nothing to do with content in DNS. If your client asks for an
record it will get the appropriate answer according to the zone's records
(a value or an error condition) regardless on whether the query was made over
IPv6 or IPv4
-
From: bind-users-bounces+alok.raj=spanservices@lists.isc.org
[mailto:bind-users-bounces+alok.raj=spanservices@lists.isc.org] On Behalf
Of Carlos M. Martinez
Sent: Friday, March 22, 2013 9:57 PM
To: Bryan Harris
Cc: bind-users@lists.isc.org
Subject: Re: Dig for link-local
Transport
: Dig for link-local
One question is whether the server will listen and reply on all addresses or
only on the global address?
I suggest you look into the log file from the server, often there are good
clues there.
On 25/03/13 10:19, Alok Raj wrote:
Hi Guys,
Basically I am trying to do
On 25/03/13 09:19, Alok Raj wrote:
Hi Guys,
Basically I am trying to do the following:
1) If I use link-local ipv6 address (of domain controller) in my
resolv.conf, my resolver routines (glibc 2.13) is not able to resolve a domain
name to an ip address, though I am able to ping that
-Original Message-
From: bind-users-bounces+alok.raj=spanservices@lists.isc.org
[mailto:bind-users-bounces+alok.raj=spanservices@lists.isc.org] On Behalf
Of Phil Mayers
Sent: Monday, March 25, 2013 5:57 PM
To: bind-users@lists.isc.org
Subject: Re: Dig for link-local
On 25/03/13 09:19
, March 25, 2013 5:57 PM
To: bind-users@lists.isc.org
Subject: Re: Dig for link-local
On 25/03/13 09:19, Alok Raj wrote:
Hi Guys,
Basically I am trying to do the following:
1) If I use link-local ipv6 address (of domain controller) in my
resolv.conf, my resolver routines (glibc 2.13
On 25/03/13 16:20, Kevin Darcy wrote:
Works fine for me on RedHat 5.7 without a scope-identifier in
/etc/resolv.conf. I notice, however, that the stock dig
(9.3.6-P1-RedHat-9.3.6-16.P1.el5, yeah, I know I should upgrade) shows
the scope identifier in its output:
;; SERVER:
On 25/03/13 17:13, Phil Mayers wrote:
On 25/03/13 16:20, Kevin Darcy wrote:
Works fine for me on RedHat 5.7 without a scope-identifier in
/etc/resolv.conf. I notice, however, that the stock dig
(9.3.6-P1-RedHat-9.3.6-16.P1.el5, yeah, I know I should upgrade) shows
the scope identifier in its
Hi,
How dig-command is able to resolve an ip using link-local address,
/etc/resolv.conf has only one entry - ipv6-link link local address, if I write
dig www.domain.comhttp://www.domain.com, it is able to resolve that and print
the address.
Can anyone help me out in documentation or code
I'm not sure what you're asking, exactly. Are you surprised that named
would respond on an IPv6 link-local address if configured with
listen-on-v6 { any; };?
- Kevin
On 3/22/2013 5:35 AM, Alok Raj wrote:
Hi,
How dig-command is able to resolve an ip using link-local address,
link-locals are not that special, with the exception of the %interface
decorator... other than that, they work exactly like any other address.
Bind/Apache/insert your server here will listen on link locals and
they can be used as route next-hops too.
regards,
~Carlos
On 3/22/13 1:13 PM, Kevin
Hello,
On Mar 22, 2013, at 12:13 PM, Kevin Darcy k...@chrysler.com wrote:
I'm not sure what you're asking, exactly. Are you surprised that named would
respond on an IPv6 link-local address if configured with listen-on-v6 { any;
};?
Can an ipv4-only server give an ipv6 address as part of
Transport has nothing to do with content in DNS. If your client asks for
an record it will get the appropriate answer according to the
zone's records (a value or an error condition) regardless on whether the
query was made over IPv6 or IPv4.
That said, you can 'hack' around this expected
13 matches
Mail list logo
