7 Jun
2024
7 Jun
'24
1:13 p.m.
Hello everyone,
I have a question for those of you who have BGP announced subnets from
44Net, specifically regarding the configuration of rDNS (PTR) records
for each IP address within the subnet.
Recently, I received an allocation of a /24 subnet, which is announced
via my Data Center's ASN. Everything is functioning correctly, but I
need to configure rDNS for each IP address. This configuration is
essential for hosting email servers to prevent potential issues.
Here is a dlint output for my gateway's IP address:
root@eye:~# dlint 1.77.32.44.in-addr.arpa
;; dlint version 1.4.0, Copyright (C) 1998 Paul A. Balyoz
<pab(a)domtools.com>
;; Dlint comes with ABSOLUTELY NO WARRANTY.
;; This is free software, and you are welcome to redistribute it
;; under certain conditions. Type 'man dlint' for details.
;; command line: /usr/bin/dlint 1.77.32.44.in-addr.arpa
;; flags: inaddr-domain recursive.
;; using dig version 9.9.5
;; run starting: Fri Jun 7 15:10:37 EEST 2024
;; ============================================================
;; Now linting 1.77.32.44.in-addr.arpa
ERROR: no name servers found for domain 1.77.32.44.in-addr.arpa
===
;; Now linting 32.44.in-addr.arpa
;; Checking serial numbers per nameserver
;; 2024060700 ns1.de.ardc.net.
;; 2024060700 ns.ardc.net.
;; 2024060700 a.gw4.uk.
;; 2024060700 ns2.us.ardc.net.
===
Based on this output, I believe that the rDNS setup needs to be handled
by the ARDC staff. However, I wanted to confirm this to ensure I proceed
correctly.
I reached out to Chris off-list and received the following response:
"You already have the subdomain yo6rzv.ampr.org setup; you can add DNS
records under there. For each A record, a PTR record is automatically
added in the reverse zone."
From my understanding, this does not fully address my requirements,
since for example, if IP Address 44.32.77.2 needs to have the rDNS set
to -> something.yo44.net, this will not help.
I am aware that Chris and the ARDC staff are currently handling a high
volume of tickets and requests through the portal. Therefore, I am
turning to the community for assistance to avoid adding more to their
workload.
I appreciate any guidance you can provide and apologize in advance if
this question has been addressed previously. I could not find relevant
information in my email archive.
Thank you for your assistance.
Best regards,
Razvan - YO6RZV
7 Jun
7 Jun
1:39 p.m.
Hi Razvan,
You can either use the subdomain that you requested and received via the portal:
yo6rzv.ampr.org <http://yo6rzv.ampr.org/>
Any A records you add under that will automatically create a PTR record in the reverse
zonefile.
However if you wish to use your own domain then you will need to request reverse DNS is
delegated to your servers by opening a ticket on the portal: “Help with DNS"
73,
Chris - G1FEF
—
ARDC Administrator
Web: https://www.ardc.net
On 7 Jun 2024, at 14:13, Razvan YO6RZV via 44net
<44net(a)mailman.ampr.org> wrote:
Hello everyone,
I have a question for those of you who have BGP announced subnets from 44Net,
specifically regarding the configuration of rDNS (PTR) records for each IP address within
the subnet.
Recently, I received an allocation of a /24 subnet, which is announced via my Data
Center's ASN. Everything is functioning correctly, but I need to configure rDNS for
each IP address. This configuration is essential for hosting email servers to prevent
potential issues.
Here is a dlint output for my gateway's IP address:
root@eye:~# dlint 1.77.32.44.in-addr.arpa
;; dlint version 1.4.0, Copyright (C) 1998 Paul A. Balyoz <pab(a)domtools.com>
;; Dlint comes with ABSOLUTELY NO WARRANTY.
;; This is free software, and you are welcome to redistribute it
;; under certain conditions. Type 'man dlint' for details.
;; command line: /usr/bin/dlint 1.77.32.44.in-addr.arpa
;; flags: inaddr-domain recursive.
;; using dig version 9.9.5
;; run starting: Fri Jun 7 15:10:37 EEST 2024
;; ============================================================
;; Now linting 1.77.32.44.in-addr.arpa
ERROR: no name servers found for domain 1.77.32.44.in-addr.arpa
===
;; Now linting 32.44.in-addr.arpa
;; Checking serial numbers per nameserver
;; 2024060700 ns1.de.ardc.net.
;; 2024060700 ns.ardc.net.
;; 2024060700 a.gw4.uk.
;; 2024060700 ns2.us.ardc.net.
===
Based on this output, I believe that the rDNS setup needs to be handled by the ARDC
staff. However, I wanted to confirm this to ensure I proceed correctly.
I reached out to Chris off-list and received the following response:
"You already have the subdomain yo6rzv.ampr.org setup; you can add DNS records under
there. For each A record, a PTR record is automatically added in the reverse zone."
From my understanding, this does not fully address my requirements, since for example, if
IP Address 44.32.77.2 needs to have the rDNS set to -> something.yo44.net, this will
not help.
I am aware that Chris and the ARDC staff are currently handling a high volume of tickets
and requests through the portal. Therefore, I am turning to the community for assistance
to avoid adding more to their workload.
I appreciate any guidance you can provide and apologize in advance if this question has
been addressed previously. I could not find relevant information in my email archive.
Thank you for your assistance.
Best regards,
Razvan - YO6RZV
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
1:43 p.m.
Razvan,
The easiest way to do this is to request that ARDC staff delegate your rDNS
zone to a set of nameservers that you control. That is, set NS records on
77.32.44.in-addr.arpa pointing to your nameservers. Then, you can set them
however you want.
You'll need to open a support ticket requesting rDNS delegation. They will
send you a document listing the requirements for your nameservers. I would
share it, but they haven't published it for some reason, so I'm not sure if
they're trying to keep it within a closed group. Once your nameservers are
compliant with those requirements, you can provide them your nameserver
addresses and the address of at least one PTR record to test and they will
(eventually) delegate the zone.
Forewarning: this process has taken an extremely long time in my experience
(I just got mine delegated the other day after 5 months of waiting).
73,
Eric AE0JE
On Fri, Jun 7, 2024, 9:14 AM Razvan YO6RZV via 44net <44net(a)mailman.ampr.org>
wrote:
Hello everyone,
I have a question for those of you who have BGP announced subnets from
44Net, specifically regarding the configuration of rDNS (PTR) records
for each IP address within the subnet.
Recently, I received an allocation of a /24 subnet, which is announced
via my Data Center's ASN. Everything is functioning correctly, but I
need to configure rDNS for each IP address. This configuration is
essential for hosting email servers to prevent potential issues.
Here is a dlint output for my gateway's IP address:
root@eye:~# dlint 1.77.32.44.in-addr.arpa
;; dlint version 1.4.0, Copyright (C) 1998 Paul A. Balyoz
<pab(a)domtools.com>
;; Dlint comes with ABSOLUTELY NO WARRANTY.
;; This is free software, and you are welcome to redistribute it
;; under certain conditions. Type 'man dlint' for details.
;; command line: /usr/bin/dlint 1.77.32.44.in-addr.arpa
;; flags: inaddr-domain recursive.
;; using dig version 9.9.5
;; run starting: Fri Jun 7 15:10:37 EEST 2024
;; ============================================================
;; Now linting 1.77.32.44.in-addr.arpa
ERROR: no name servers found for domain 1.77.32.44.in-addr.arpa
===
;; Now linting 32.44.in-addr.arpa
;; Checking serial numbers per nameserver
;; 2024060700 ns1.de.ardc.net.
;; 2024060700 ns.ardc.net.
;; 2024060700 a.gw4.uk.
;; 2024060700 ns2.us.ardc.net.
===
Based on this output, I believe that the rDNS setup needs to be handled
by the ARDC staff. However, I wanted to confirm this to ensure I proceed
correctly.
I reached out to Chris off-list and received the following response:
"You already have the subdomain yo6rzv.ampr.org setup; you can add DNS
records under there. For each A record, a PTR record is automatically
added in the reverse zone."
From my understanding, this does not fully address my requirements,
since for example, if IP Address 44.32.77.2 needs to have the rDNS set
to -> something.yo44.net, this will not help.
I am aware that Chris and the ARDC staff are currently handling a high
volume of tickets and requests through the portal. Therefore, I am
turning to the community for assistance to avoid adding more to their
workload.
I appreciate any guidance you can provide and apologize in advance if
this question has been addressed previously. I could not find relevant
information in my email archive.
Thank you for your assistance.
Best regards,
Razvan - YO6RZV
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
4:01 p.m.
On 2024-06-07 16:43, Eric Johnson via 44net wrote:
Razvan,
The easiest way to do this is to request that ARDC staff delegate your
rDNS zone to a set of nameservers that you control. That is, set NS
records on 77.32.44.in-addr.arpa pointing to your nameservers. Then,
you can set them however you want.
You'll need to open a support ticket requesting rDNS delegation. They
will send you a document listing the requirements for your
nameservers. I would share it, but they haven't published it for some
reason, so I'm not sure if they're trying to keep it within a closed
group. Once your nameservers are compliant with those requirements,
you can provide them your nameserver addresses and the address of at
least one PTR record to test and they will (eventually) delegate the
zone.
Forewarning: this process has taken an extremely long time in my
experience (I just got mine delegated the other day after 5 months of
waiting).
73,
Eric AE0JE
On Fri, Jun 7, 2024, 9:14 AM Razvan YO6RZV via 44net
<44net(a)mailman.ampr.org> wrote:
Hello Chris, Eric,
I really appreciate your fast responses to my questions.
Chris, I want to apologize for any trouble I've had understanding how
the portal works. I’ve added a test A record for an IP address within my
subnet, and it’s already updated with rDNS added. This is great.
In the meantime, I have opened a ticket as Eric suggested, and until
that is resolved, I will use this method. The new portal features are
really cool.
Thank you!
--
73's
Thanks,
Razvan - YO6RZV
Hello everyone,
I have a question for those of you who have BGP announced subnets
from
44Net, specifically regarding the configuration of rDNS (PTR)
records
for each IP address within the subnet.
Recently, I received an allocation of a /24 subnet, which is
announced
via my Data Center's ASN. Everything is functioning correctly, but I
need to configure rDNS for each IP address. This configuration is
essential for hosting email servers to prevent potential issues.
Here is a dlint output for my gateway's IP address:
root@eye:~# dlint 1.77.32.44.in-addr.arpa
;; dlint version 1.4.0, Copyright (C) 1998 Paul A. Balyoz
<pab(a)domtools.com>
;; Dlint comes with ABSOLUTELY NO WARRANTY.
;; This is free software, and you are welcome to redistribute it
;; under certain conditions. Type 'man dlint' for details.
;; command line: /usr/bin/dlint 1.77.32.44.in-addr.arpa
;; flags: inaddr-domain recursive.
;; using dig version 9.9.5
;; run starting: Fri Jun 7 15:10:37 EEST 2024
;; ============================================================
;; Now linting 1.77.32.44.in-addr.arpa
ERROR: no name servers found for domain 1.77.32.44.in-addr.arpa
===
;; Now linting 32.44.in-addr.arpa
;; Checking serial numbers per nameserver
;; 2024060700 ns1.de.ardc.net [1].
;; 2024060700 ns.ardc.net [2].
;; 2024060700 a.gw4.uk [3].
;; 2024060700 ns2.us.ardc.net [4].
===
Based on this output, I believe that the rDNS setup needs to be
handled
by the ARDC staff. However, I wanted to confirm this to ensure I
proceed
correctly.
I reached out to Chris off-list and received the following response:
"You already have the subdomain yo6rzv.ampr.org [5] setup; you can
add DNS
records under there. For each A record, a PTR record is
automatically
added in the reverse zone."
From my understanding, this does not fully address my requirements,
since for example, if IP Address 44.32.77.2 needs to have the rDNS
set
to -> something.yo44.net [6], this will not help.
I am aware that Chris and the ARDC staff are currently handling a
high
volume of tickets and requests through the portal. Therefore, I am
turning to the community for assistance to avoid adding more to
their
workload.
I appreciate any guidance you can provide and apologize in advance
if
this question has been addressed previously. I could not find
relevant
information in my email archive.
Thank you for your assistance.
Best regards,
Razvan - YO6RZV
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
Links:
------
[1] http://ns1.de.ardc.net
[2] http://ns.ardc.net
[3] http://a.gw4.uk
[4] http://ns2.us.ardc.net
[5] http://yo6rzv.ampr.org
[6] http://something.yo44.net
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
11 Jun
11 Jun
1:27 p.m.
On 2024-06-07 16:43, Eric Johnson via 44net wrote:
Razvan,
The easiest way to do this is to request that ARDC staff delegate your
rDNS zone to a set of nameservers that you control. That is, set NS
records on 77.32.44.in-addr.arpa pointing to your nameservers. Then,
you can set them however you want.
You'll need to open a support ticket requesting rDNS delegation. They
will send you a document listing the requirements for your
nameservers. I would share it, but they haven't published it for some
reason, so I'm not sure if they're trying to keep it within a closed
group. Once your nameservers are compliant with those requirements,
you can provide them your nameserver addresses and the address of at
least one PTR record to test and they will (eventually) delegate the
zone.
Forewarning: this process has taken an extremely long time in my
experience (I just got mine delegated the other day after 5 months of
waiting).
73,
Eric AE0JE
On Fri, Jun 7, 2024, 9:14 AM Razvan YO6RZV via 44net
<44net(a)mailman.ampr.org> wrote:
Hi all,
I'm writing up this as a follow up email on my initial request, to let
you know that this was resolved as Eric pointed out, the rDNS zone was
delegated to myself, and now I'm able to handle my rDNS for each of my
IP's within the allocated subnet.
Kudos to Chris, which handled the ticket with professionalism and
treated the issue very promptly. Had a very pleasant experience.
So if anybody else is in this sittuation, just raise a ticket, and ARDC
Staff will handle it so you can play with the rDNS, but you will need to
meet some strict requirements imposed by ARDC (which is normal).
If anybody has any other questions related to this, please feel free to
email me directly and I'll provide assistance if needed with the whole
process.
Have a great day everyone.
--
73's
Thanks,
Razvan - YO6RZV
Hello everyone,
I have a question for those of you who have BGP announced subnets
from
44Net, specifically regarding the configuration of rDNS (PTR)
records
for each IP address within the subnet.
Recently, I received an allocation of a /24 subnet, which is
announced
via my Data Center's ASN. Everything is functioning correctly, but I
need to configure rDNS for each IP address. This configuration is
essential for hosting email servers to prevent potential issues.
Here is a dlint output for my gateway's IP address:
root@eye:~# dlint 1.77.32.44.in-addr.arpa
;; dlint version 1.4.0, Copyright (C) 1998 Paul A. Balyoz
<pab(a)domtools.com>
;; Dlint comes with ABSOLUTELY NO WARRANTY.
;; This is free software, and you are welcome to redistribute it
;; under certain conditions. Type 'man dlint' for details.
;; command line: /usr/bin/dlint 1.77.32.44.in-addr.arpa
;; flags: inaddr-domain recursive.
;; using dig version 9.9.5
;; run starting: Fri Jun 7 15:10:37 EEST 2024
;; ============================================================
;; Now linting 1.77.32.44.in-addr.arpa
ERROR: no name servers found for domain 1.77.32.44.in-addr.arpa
===
;; Now linting 32.44.in-addr.arpa
;; Checking serial numbers per nameserver
;; 2024060700 ns1.de.ardc.net [1].
;; 2024060700 ns.ardc.net [2].
;; 2024060700 a.gw4.uk [3].
;; 2024060700 ns2.us.ardc.net [4].
===
Based on this output, I believe that the rDNS setup needs to be
handled
by the ARDC staff. However, I wanted to confirm this to ensure I
proceed
correctly.
I reached out to Chris off-list and received the following response:
"You already have the subdomain yo6rzv.ampr.org [5] setup; you can
add DNS
records under there. For each A record, a PTR record is
automatically
added in the reverse zone."
From my understanding, this does not fully address my requirements,
since for example, if IP Address 44.32.77.2 needs to have the rDNS
set
to -> something.yo44.net [6], this will not help.
I am aware that Chris and the ARDC staff are currently handling a
high
volume of tickets and requests through the portal. Therefore, I am
turning to the community for assistance to avoid adding more to
their
workload.
I appreciate any guidance you can provide and apologize in advance
if
this question has been addressed previously. I could not find
relevant
information in my email archive.
Thank you for your assistance.
Best regards,
Razvan - YO6RZV
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
Links:
------
[1] http://ns1.de.ardc.net
[2] http://ns.ardc.net
[3] http://a.gw4.uk
[4] http://ns2.us.ardc.net
[5] http://yo6rzv.ampr.org
[6] http://something.yo44.net
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
110
days inactive
114
days old
4 comments
3 participants
participants (3)
-
Chris -
Eric Johnson -
Razvan YO6RZV