Authoritative answers can be found from: 177.132.209.nameserver = ns3. This is in different to Forward DNS, Mining which are configured with A records (Address Records).

XX#53 Non-authoritative answer: name = Reverse DNS is setup by configuring PTR records (Pointer Records) on your DNS server.

SOA serial: 1377691702 SOA refresh: 3600 SOA retry: 900 SOA expire: 1209600 SOA minimum: 3000 SOA time to live: 1800 Active zone: TRUE Allow query: any; Allow transfer: none; To create the reverse zone by its IP network, set the network information to the (forward-style) IP address, with the subnet mask bit count.

Your ISP or hosting provider may delegate your own range of IP addresses, or you may have NAT setup for Private IP space you control, in this case you must configure Reverse DNS thru PTR records on your DNS server.

A lot of Systems Administrators configure Forward DNS but not Reverse DNS.

Typically you or a DNS provider is in charge of Forward DNS.

In the case of Reverse DNS most likely your ISP supplying your IP information will have responsibility. ######## The number 2-6 are the last octect of 192.168.0. STEP 2 Enter the zone into your or as you would a regular zone.

[[email protected] ~]$ kinit admin [[email protected] ~]$ ipa dnszone-disable server.----------------------------------------- Disabled DNS zone "" -----------------------------------------.

A forward-only zone does not check its own name records. If the record does not exist on the configured forwarders, then the zone returns a negative response to the client.We can verify the zone from DNS Management console (dnsmgmt.msc) of Secondary DNS Server. One more thing we should check is that when we make any changes with forward lookup zone on primary name server those changes should immediately appear in secondary forward lookup zone of secondary name server.This is because we have configured primary forward lookup zone to automatically notify all the name servers listed on name servers tab about the changes happening in primary forward lookup zone. A DNS server can be authoritative for multiple DNS zones. A zone contains the resource records for all of the names within the particular zone. A DNS zone can contain one or more contiguous domains.To resolve hostnames within the DNS domain, a DNS client issues a query to the DNS name server.