covensa.blogg.se

It is best practice to configure Reverse DNS from the get go, to avoid troubleshooting headaches. In most cases when you do this things will work fine, however some applications require doing Reverse DNS lookups in which case you could run into latency issues and a whole slew of other issues.Ĭommon applications and protocols such as IRC, SMTP, Backup utilities, and Databases sometimes use Reverse DNS. 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.Ī lot of Systems Administrators configure Forward DNS but not Reverse DNS. You can setup Reverse DNS on your own name servers if you choose which we will cover in this article. You would simply send them what Hostname resolves to what IP, and they would setup the PTR records. In the case of Reverse DNS most likely your ISP supplying your IP information will have responsibility. Typically you or a DNS provider is in charge of Forward DNS. This is in different to Forward DNS, which are configured with A records (Address Records). Reverse DNS is setup by configuring PTR records (Pointer Records) on your DNS server. name = .Īuthoritative answers can be found ~]$ nslookup