Re: Question for this IP's PTR

2023-03-25 Thread debian-user
f...@dnsbed.com wrote: > Greetings, > > as you see this PTR, > > $ dig -x 1.1.1.1 +short > one.one.one.one. > > so 2.2.2.2 can have the PTR two.two.two.two? and 3.3.3.3 can have > three.three.three.three? A simple counter example is $ dig -x 8.8.8.8 +short dns.google. > Sorry I am not good a

Re: Question for this IP's PTR

2023-03-25 Thread Joe
On Fri, 24 Mar 2023 20:32:31 -0400 Greg Wooledge wrote: > On Sat, Mar 25, 2023 at 08:28:03AM +0800, f...@dnsbed.com wrote: > > Greetings, > > > > as you see this PTR, > > > > $ dig -x 1.1.1.1 +short > > one.one.one.one. > > > > so 2.2.2.2 can have the PTR two.two.two.two? and 3.3.3.3 can have

Re: Question for this IP's PTR

2023-03-24 Thread fh
On 2023-03-25 08:32, Greg Wooledge wrote: On Sat, Mar 25, 2023 at 08:28:03AM +0800, f...@dnsbed.com wrote: Greetings, as you see this PTR, $ dig -x 1.1.1.1 +short one.one.one.one. so 2.2.2.2 can have the PTR two.two.two.two? and 3.3.3.3 can have three.three.three.three? Any IP address can h

Re: Question for this IP's PTR

2023-03-24 Thread Jeremy Ardley
On 25/3/23 08:32, Greg Wooledge wrote: I didn't know .one was a valid TLD. It looks like .two is not, so if someone were to assign "two.two.two.two" as the PTR value of an IP address, that PTR would not resolve back to any IP address. (An IP address block owner might reject such a petition.)

Re: Question for this IP's PTR

2023-03-24 Thread Greg Wooledge
On Sat, Mar 25, 2023 at 08:28:03AM +0800, f...@dnsbed.com wrote: > Greetings, > > as you see this PTR, > > $ dig -x 1.1.1.1 +short > one.one.one.one. > > so 2.2.2.2 can have the PTR two.two.two.two? and 3.3.3.3 can have > three.three.three.three? Any IP address can have any PTR value. You just

Question for this IP's PTR

2023-03-24 Thread fh
Greetings, as you see this PTR, $ dig -x 1.1.1.1 +short one.one.one.one. so 2.2.2.2 can have the PTR two.two.two.two? and 3.3.3.3 can have three.three.three.three? Sorry I am not good at the DNS knowledge. Regards.