Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

Wild card for IPV6 reverse configuration

931 views

Skip to first unread message

hugo hugoo

unread,

Jun 12, 2012, 4:57:06 PM6/12/12

to bind-...@lists.isc.org

Dear all,

I have tried to configure a zone containing a range of IPV6 PTR records.

My target was to see how it is possible to configure such a zone to always return the same answer for all the IPV6 IP’s in the range.

And if possible to return specifi names for specific IP’s.

Example of a IPV6 range:

1234:5678:90ab:00cd::/56

Creation of the zone è “0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa.”

In the zone, I have put the following PTR record:

*.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. 3600 IN PTR 123.lebrol.be.

It seems (according to some of my tests) that for all IP’s in the range, the reverse is “123.lebrol.be.”

Question è is this a correct way to configure reverse IPV6 if we accept the same name for all the IP’s in the range?

Zone modification:

I have tried to add in the zone file the possibility to answer a specific name to a specific IP in the range and keep answering the general name to all the other IP’s in the range.

*.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. 3600 IN PTR 123.lebrol.be.

1.2.3.4.5.6.7.8.9.a.b.c.d.e.f.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. 3600 IN PTR nombre.de.cerise.be. è specific IP

It works when the specific IP is used:

lennydnstest01:~# dig @localhost -x 1234:5678:90ab:0021:0fed:cba9:8765:4321

;; QUESTION SECTION:

;1.2.3.4.5.6.7.8.9.a.b.c.d.e.f.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. IN PTR

;; ANSWER SECTION:

1.2.3.4.5.6.7.8.9.a.b.c.d.e.f.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. 3600 IN PTR nombre.de.cerise.be.

But if another IP in the range is used having the following nibbles mapping the specific PTR (here 1.2 ), it do not work and nothing is found!

lennydnstest01:~# dig @localhost -x 1234:5678:90ab:0021::

;; QUESTION SECTION:

;0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. IN PTR

;; AUTHORITY SECTION:

0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. 3600 IN SOA ns1.uat.skynet.be. dnsmaster.skynet.be. 5 10800 3600 3600000 3600

Can someone give an explanation on the use of the wildcard *.
Any other way to obtain the desired result?

Thanks in advance for your feedback,

Hugo,

Mark Andrews

unread,

Jun 13, 2012, 12:15:46 AM6/13/12

to hugo hugoo, bind-...@isc.org

In message <DUB109-W102263F0A3...@phx.gbl>, hugo hugoo writes:
> Dear all=2C
> =20

> I have tried to configure a zone containing a range of IPV6 PTR records.
> My target was to see how it is possible to configure such a zone to

> always return the same answer for all the IPV6 IP=92s in the range.
> And if possible to return specifi names for specific IP=92s.
> =20

> Example of a IPV6 range:

> =20

> 1234:5678:90ab:00cd::/56

> =20
> =20
> Creation of the zone =E8 =930.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa.=94
> =20
> In the zone=2C I have put the following PTR record:
> =20
> *.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. 3600 IN PTR 123.lebrol.be=
> .
> =20
> It seems (according to some of my tests) that for all IP=92s in the range=
> =2C the reverse is =93123.lebrol.be.=94
> =20
> Question =E8 is this a correct way to configure reverse IPV6 if we accept=
> the same name for all the IP=92s in the range?
> =20
> =20
> Zone modification:
> =20
> I have tried to add in the zone file the possibility to answer a=20
> specific name to a specific IP in the range and keep answering the=20
> general name to all the other IP=92s in the range.
> =20
> *.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. 3600 IN PTR 123.lebrol.be=
> .

You need to add a few more records. Wildcards don't work the way you think
they do. The existance of a label, even with no data, disables wildcard
processing.

*.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. PTR 123.lebrol.be.
*.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. PTR 123.lebrol.be.
*.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. PTR 123.lebrol.be.
*.f.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. PTR 123.lebrol.be.
*.e.f.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. PTR 123.lebrol.be.
*.d.e.f.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. PTR 123.lebrol.be.
*.c.d.e.f.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. PTR 123.lebrol.be.
*.b.c.d.e.f.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. PTR 123.lebrol.be.
*.a.b.c.d.e.f.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. PTR 123.lebrol.be.
*.9.a.b.c.d.e.f.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. PTR 123.lebrol.be.
*.8.9.a.b.c.d.e.f.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. PTR 123.lebrol.be.
*.7.8.9.a.b.c.d.e.f.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. PTR 123.lebrol.be.
*.6.7.8.9.a.b.c.d.e.f.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. PTR 123.lebrol.be.
*.5.6.7.8.9.a.b.c.d.e.f.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. PTR 123.lebrol.be.
*.4.5.6.7.8.9.a.b.c.d.e.f.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. PTR 123.lebrol.be.
*.3.4.5.6.7.8.9.a.b.c.d.e.f.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. PTR 123.lebrol.be.
*.2.3.4.5.6.7.8.9.a.b.c.d.e.f.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. PTR 123.lebrol.be.

> 1.2.3.4.5.6.7.8.9.a.b.c.d.e.f.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. =
> 3600 IN PTR nombre.de.cerise.be. =E8 s=
> pecific IP
> =20
> =20

> It works when the specific IP is used:

> =20

> lennydnstest01:~# dig @localhost -x 1234:5678:90ab:0021:0fed:cba9:8765:4321

> =20
> =3B=3B QUESTION SECTION:
> =3B1.2.3.4.5.6.7.8.9.a.b.c.d.e.f.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa=
> . IN PTR
> =3B=3B ANSWER SECTION:
> 1.2.3.4.5.6.7.8.9.a.b.c.d.e.f.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. 3=
> 600 IN PTR nombre.de.cerise.be.
> =20
> =20
> But if another IP in the range is used having the following nibbles mapping=
> the specific PTR (here 1.2 )=2C it do not work and nothing is found!
> =20
> =20
> lennydnstest01:~# dig @localhost -x 1234:5678:90ab:0021::
> =20
> =3B=3B QUESTION SECTION:
> =3B0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa=
> . IN PTR
> =3B=3B AUTHORITY SECTION:
> 0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. 3600 IN SOA ns1.uat.skynet.be. dnsmas=

> ter.skynet.be. 5 10800 3600 3600000 3600

> =20
> =20
> Can someone give an explanation on the use of the wildcard *.Any other way =

> to obtain the desired result?

> =20
> =20
> Thanks in advance for your feedback=2C
> =20
> Hugo=2C =
>
> --_8940b2fd-a732-48b4-8129-33249f29de87_
> Content-Type: text/html; charset="Windows-1252"
> Content-Transfer-Encoding: quoted-printable
>
> <html>
> <head>
> <style></style></head>
> <body class=3D'hmmessage'><div dir=3D'ltr'>
> <font style=3D"font-size: 10pt=3B" face=3D"Calibri" size=3D"2"><span style=
> =3D"font-size:11pt"><div>Dear all=2C</div>
> <div>&nbsp=3B</div>
> <div>I have tried to configure a zone containing a range of IPV6 PTR record=
> s.</div>
> <div>My target was to see how it is possible to configure such a zone to
> always return the same answer for all the IPV6 IP=92s in the range.</div>
> <div>And if possible to return specifi names for specific IP=92s.</div>
> <div>&nbsp=3B</div>
> <div><u>Example of a IPV6 range:</u></div>
> <div>&nbsp=3B</div>
> <div>1234:5678:90ab:00cd::/56</div>
> <div>&nbsp=3B</div>
> <div>&nbsp=3B</div>
> <div><b><u>Creation of the zone&nbsp=3B </u></b><font face=3D"Wingdings">=
> =E8</font><b><u>&nbsp=3B =930.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa.=94</u></b=
> ></div>
> <div>&nbsp=3B</div>
> <div>In the zone=2C I have put the following PTR record:</div>
> <div>&nbsp=3B</div>
> <div>*.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. 3600&nbsp=3B&nbsp=3B&nbsp=3B&n=
> bsp=3B IN&nbsp=3B&nbsp=3B PTR&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B 123.lebrol.be=
> .</div>
> <div>&nbsp=3B</div>
> <div>It seems (according to some of my tests) that for all IP=92s in the ra=
> nge=2C the reverse is =93123.lebrol.be.=94</div>
> <div>&nbsp=3B</div>
> <div>Question&nbsp=3B <font face=3D"Wingdings">=E8</font>&nbsp=3B is this a=
> correct way to configure reverse IPV6 if we accept the same name for all t=
> he IP=92s in the range?</div>
> <div>&nbsp=3B</div>
> <div>&nbsp=3B</div>
> <div><b><u>Zone modification:</u></b></div>
> <div>&nbsp=3B</div>
> <div>I have tried to add in the zone file the possibility to answer a=20
> specific name to a specific IP in the range and keep answering the=20
> general name to all the other IP=92s in the range.</div>
> <div>&nbsp=3B</div>
> <div>*.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. 3600&nbsp=3B&nbsp=3B&nbsp=3B&n=
> bsp=3B IN&nbsp=3B&nbsp=3B PTR&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B 123.lebrol.be=
> .</div>
> <div>1.2.3.4.5.6.7.8.9.a.b.c.d.e.f.0.<font color=3D"red"><b>1.2</b></font>.=
> 0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
> =3B&nbsp=3B&nbsp=3B 3600&nbsp=3B&nbsp=3B&nbsp=3B IN&nbsp=3B&nbsp=3B&nbsp=3B=
> &nbsp=3B&nbsp=3B PTR&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B nombre.de.cerise.be.&n=
> bsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
> =3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B=
> <font face=3D"Wingdings">=E8</font> specific IP</div>
> <div>&nbsp=3B</div>
> <div>&nbsp=3B</div>
> <div>It works when the specific IP is used:</div>
> <div>&nbsp=3B</div>
> <div>lennydnstest01:~# dig @localhost -x 1234:5678:90ab:0021:0fed:cba9:8765=
> :4321</div>
> <div>&nbsp=3B</div>
> <div>=3B=3B QUESTION SECTION:</div>
> <div>=3B1.2.3.4.5.6.7.8.9.a.b.c.d.e.f.0.1.2.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6=
> .arpa. IN PTR</div>
> <div>=3B=3B ANSWER SECTION:</div>
> <div>1.2.3.4.5.6.7.8.9.a.b.c.d.e.f.0<b>.</b>1.2<font color=3D"red">.</font>=
> 0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. 3600 IN PTR nombre.de.cerise.be.</div=
> >
> <div>&nbsp=3B</div>
> <div>&nbsp=3B</div>
> <div>But if another IP in the range is used having the following nibbles ma=
> pping the specific PTR&nbsp=3B (here <font color=3D"red"><b>1.2</b></font> =
> )=2C&nbsp=3B it do not work&nbsp=3B <font style=3D"" face=3D"Wingdings">and=
> </font> nothing is found!</div>
> <div>&nbsp=3B</div>
> <div>&nbsp=3B</div>
> <div>lennydnstest01:~# dig @localhost -x 1234:5678:90ab:00<font color=3D"re=
> d"><b>21</b></font>::</div>
> <div>&nbsp=3B</div>
> <div>=3B=3B QUESTION SECTION:</div>
> <div>=3B0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.<font color=3D"red"><b>1.2</b></fon=
> t>.0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. IN PTR</div>
> <div>=3B=3B AUTHORITY SECTION:</div>
> <div>0.0.b.a.0.9.8.7.6.5.4.3.2.1.ip6.arpa. 3600 IN SOA ns1.uat.skynet.be. d=
> nsmaster.skynet.be. 5 10800 3600 3600000 3600</div>
> <div>&nbsp=3B</div>
> <div>&nbsp=3B</div>
> <ul style=3D"padding-left:36pt"><li>Can someone give an explanation on the =
> use of the wildcard *.</li><li>Any other way to obtain the desired result?<=
> /li></ul>
> <div>&nbsp=3B</div>
> <div>&nbsp=3B</div>
> <div>Thanks in advance for your feedback=2C</div>
> <div>&nbsp=3B</div>
> <div>Hugo=2C</div></span></font> </div
> ></body>
> </html>=
>
> --_8940b2fd-a732-48b4-8129-33249f29de87_--
>
> --===============2234048116426783658==
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
>
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
> from this list
>
> bind-users mailing list
> bind-...@lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
> --===============2234048116426783658==--
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org

0 new messages