On Tue, Apr 12, 2011 at 11:21:14AM +0200, Marco Davids (SIDN) wrote:
...
Or do it 'the BIND way':
dig -x 2001:7b8:c05::80:1 | grep ip6.arpa | tail -1 | awk '{print $1}'
...
If things work right, this seems to give the name of the smallest
existing enclosing zone (from the SOA or NS record),
Hi,
we have internal domain called sva.com and address record for this sva.com is
pointed to many IP addresses. When i do nslookup, i am getting below output. I
would like to enable the same configuration in bind.
Let us know how this can be acheived.
#nslookup sva.com
Name:
Hi,
we have internal domain called sva.com and address record for this
sva.com is pointed to many IP addresses. When i do nslookup, i am getting
below output. I would like to enable the same configuration in bind.
Let us know how this can be acheived.
#nslookup sva.com
Name: sva.com
In the bind 8 days people would put the same address multiple times and then
other addresses as well to weight the responses.
-Ben Croswell
On Apr 17, 2011 2:45 PM, Eivind Olsen eiv...@aminor.no wrote:
Hi,
we have internal domain called sva.com and address record for this
sva.com is pointed
In the bind 8 days people would put the same address multiple times and
then
other addresses as well to weight the responses.
Yes, but in the example given it's the same address all the time, no
mention of any other addresses, and that's why I ask - what for?
Regards
Eivind Olsen
5 matches
Mail list logo