ttobey
2 Bronze

Why are reverse lookup DNS Pointer(PTR) records needed?

Jump to solution

Why are reverse lookup DNS Pointer (PTR) records need for networker backups?

Is this something that can be changed in our networker environment so that they are not needed?

Thanks

0 Kudos
1 Solution

Accepted Solutions
MoinMansuri
3 Argentum

Re: Why are reverse lookup DNS Pointer(PTR) records needed?

Jump to solution

A NetWorker host must consistently and reliably connect to, and resolve, each destination NetWorker host by fully qualified domain name (FQDN), shortname, and IP address. The NetWorker software requires consistent and predictable forward and reverse name resolution to work correctly. NetWorker performs name resolution checks during the following operations:

• NetWorker daemon startup.

• Client and Device resource configuration.

• Backup, recovery, and device operations.

• NetWorker relies on the operating system to perform the following tasks:

• Handle name resolution requests.

• Resolve hostnames to IP addresses (forward name resolution lookups).

• Resolve IP addresses to hostnames (reverse name resolution lookups)

View solution in original post

0 Kudos
4 Replies
crazyrov
4 Beryllium

Re: Why are reverse lookup DNS Pointer(PTR) records needed?

Jump to solution

NetWorker works mainly on hostname's. In case it is not able to resolve a IP to its respective hostname else the backup for the respective host will fail.

incase you don't have a DNS, you could always use the hosts file for name resolution. NetWorker does nto mind if its your OS is looking up the DNR entry or the hosts file entry as far as there is hostname to IP and IP to hostname resolution.

HTH.

HTH,
For NetWorker related content - https://www.youtube.com/channel/UC4JLsVyXMyjbQ4i1NaJj5IQ

0 Kudos
ttobey
2 Bronze

Re: Re: Why are reverse lookup DNS Pointer(PTR) records needed?

Jump to solution

I may have not made my question clear sometimes I don't.

The situation...

I can successfully ping the hostname of the client from the networker server.

nslookup on the client hostname is successful from the networker server.

(reverse) nslookup on the IP address of the client from the networker server fails.

I did try adding the hostname to the hosts file and that did not fix the issue.

Without the PTR pointer the client backup fails with "Hostname resolution failed"

When I add the PTR record for the client backup is successful.

So my question is why does networker need reverse lookup PTR record needed and \ or what does networker use the PTR pointer record for for?

Is there a change I can make so that the PTR pointer is not needed for successful backup?

Thanks

0 Kudos
ble1
7 Thorium

Re: Why are reverse lookup DNS Pointer(PTR) records needed?

Jump to solution

Yes, you can change - DNS :-D  It is simple security mechanism to prevent certain types of spoofing and keep away wanna be hackers to access data which is supposed to be protected.

0 Kudos
MoinMansuri
3 Argentum

Re: Why are reverse lookup DNS Pointer(PTR) records needed?

Jump to solution

A NetWorker host must consistently and reliably connect to, and resolve, each destination NetWorker host by fully qualified domain name (FQDN), shortname, and IP address. The NetWorker software requires consistent and predictable forward and reverse name resolution to work correctly. NetWorker performs name resolution checks during the following operations:

• NetWorker daemon startup.

• Client and Device resource configuration.

• Backup, recovery, and device operations.

• NetWorker relies on the operating system to perform the following tasks:

• Handle name resolution requests.

• Resolve hostnames to IP addresses (forward name resolution lookups).

• Resolve IP addresses to hostnames (reverse name resolution lookups)

View solution in original post

0 Kudos