Re: dns lookup behavior

2022-02-23 Thread Tim via users
On Wed, 2022-02-23 at 08:23 -0800, Mike Wright wrote: > If you are using a hosted nameserver you will have to contact them > and request a PTR record for 172.16.96.20 that points to > centos8-opstcore-vm.homenet172-16-96.com. I don't think you could use that with an external DNS, 172.16.0.0 is on

Re: dns lookup behavior

2022-02-23 Thread Mike Wright
On 2/22/22 16:08, Paolo Galtieri wrote: On 2/21/22 15:56, Jamie Fargen wrote:     dig 172.16.96.20 Do you mean dig -x 172.16.96.20 dig 1.1.1.1 doesn't return the host name: dig -x 172.16.96.20 returns ; <<>> DiG 9.16.24-RH <<>> -x 172.16.96.20 ;; global options: +cmd ;; connection

Re: dns lookup behavior

2022-02-23 Thread Tim via users
Paolo Galtieri wrote: > dig -x 172.16.96.20 > > returns > > ; <<>> DiG 9.16.24-RH <<>> -x 172.16.96.20 > ;; global options: +cmd > ;; connection timed out; no servers could be reached > > but > > dig centos8-opstcore-vm.homenet172-16-96.com > > returns > > ; <<>> DiG 9.16.24-RH <<>> centos8-o

Re: dns lookup behavior

2022-02-22 Thread Paolo Galtieri
On 2/21/22 15:56, Jamie Fargen wrote: dig 172.16.96.20 Do you mean dig -x 172.16.96.20 dig 1.1.1.1 doesn't return the host name: dig -x 172.16.96.20 returns ; <<>> DiG 9.16.24-RH <<>> -x 172.16.96.20 ;; global options: +cmd ;; connection timed out; no servers could be reached

Re: dns lookup behavior

2022-02-21 Thread Jamie Fargen
> > > dig 172.16.96.20 > > Do you mean dig -x 172.16.96.20 dig 1.1.1.1 doesn't return the host name: You can see running dig followed by an IP doesn't return anything, to do a reverse DNS lookup, or to resolve the hostname from the IP, you can see in the second example dig -x followed by the IP

Re: dns lookup behavior

2022-02-21 Thread Paolo Galtieri
On 2/21/22 14:09, Jamie Fargen wrote: On Mon, Feb 21, 2022 at 4:52 PM Barry wrote: > On 21 Feb 2022, at 20:15, Paolo Galtieri wrote: > > Folks, >  I have 3 Linux systems, one running F31 and 2 running F34.  On one of the F34 systems I have a local DNS server runn

Re: dns lookup behavior

2022-02-21 Thread Jamie Fargen
On Mon, Feb 21, 2022 at 4:52 PM Barry wrote: > > > > On 21 Feb 2022, at 20:15, Paolo Galtieri wrote: > > > > Folks, > > I have 3 Linux systems, one running F31 and 2 running F34. On one of > the F34 systems I have a local DNS server running. This has worked fine in > the past, but now I'm se

Re: dns lookup behavior

2022-02-21 Thread Barry
> On 21 Feb 2022, at 20:15, Paolo Galtieri wrote: > > Folks, > I have 3 Linux systems, one running F31 and 2 running F34. On one of the > F34 systems I have a local DNS server running. This has worked fine in the > past, but now I'm seeing strangeness on the 2 F34 systems. > > I added a

Re: dns lookup behavior

2022-02-21 Thread Barry
> On 21 Feb 2022, at 20:15, Paolo Galtieri wrote: > > Folks, > I have 3 Linux systems, one running F31 and 2 running F34. On one of the > F34 systems I have a local DNS server running. This has worked fine in the > past, but now I'm seeing strangeness on the 2 F34 systems. F31 is real ol

dns lookup behavior

2022-02-21 Thread Paolo Galtieri
Folks,  I have 3 Linux systems, one running F31 and 2 running F34.  On one of the F34 systems I have a local DNS server running.  This has worked fine in the past, but now I'm seeing strangeness on the 2 F34 systems. I added a host to the DNS server for normal lookup and reverse lookup.  On t