For reasons unknown, some old Solaris servers are suddenly seeing connections
to them as ipv4-mapped ipv6 (ie: :::10.20.30.40 ) Which is causing
problems because it needs the reverse lookup to be right.
So while we struggle between spending time to investigate why or continue to
try to get
Getnameinfo and gethostbyaddr are supposed to lookup the in-addr.arpa records
instead of ip6.arpa records for mapped addresses. If you only have a limited
range of addresses one could use $generate to add cname records which map from
ip6.arpa to in-addr.arpa.
Mark
On 09/07/2013, at 8:12, "Lawr
One could also look at the dns64 reverse code to do this. It synthesises cname
records on the fly.
Mark
On 09/07/2013, at 8:27, Mark Andrews wrote:
> Getnameinfo and gethostbyaddr are supposed to lookup the in-addr.arpa records
> instead of ip6.arpa records for mapped addresses. If you only
In message <9efac3c5-c5be-43f8-b7f4-2be8ba30d...@isc.org>, Mark Andrews writes:
> One could also look at the dns64 reverse code to do this. It synthesises
> cname records on the fly.
>
> Mark
>
e.g.
zone "f.f.f.f.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa" {
type
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
Only thing I see to be missing here is actual Class B address space 172.16/12
but instead you are trying to forward from Class A public address space
assigned to FACEBOOK. I don't quite think you will get that to work... That is
unless you are the Facebook authoritative server...
range:
Sorry for top-post.
Your expectation is incorrect.
zone "0/24.110.252.173.in-addr.arpa"
is not the same as
zone "173.252.110.24.in-addr.arpa"
hth,
Len
>
> From: sumsum 2000
>To: bind-users@lists.isc.org
>Sent: Monday, July 8, 2013 11:21 PM
>Subject: Re
Oops mistype
range: 172.16.0.0 > 172.31.255.255
range b10: 2886729728 > 2887778303 range b16: 0xac10 > 0xac1f
hosts: 1048576 prefixlen: 12
mask:255.240.0.0
--
Jason Hellenthal
I
It's not at all clear from your description what you're trying to
accomplish. Particularly it's not clear what you seem to be trying to
accomplish with the 2317 delegation for a /24 zone.
Can you describe what you're trying to do, and why? It may be easier to
help you that way. Please use the
9 matches
Mail list logo
