What are the different threats on DNS

[Aloke]

I need factor causing the problem of DNS security. What all options are depend on it. I want some information on different types of DNS attacks and security threats on it. Which is the most common one that is affecting a DNS security most oftenly. what are the precaution measure used to troubleshoot out this problem online. There might be many means of way.

[Milton.J]

Of all malevolent attacks, DNS is most susceptible to spoofing. When any DNS resolver sends a inaccessible inquiry, it tags the inquiry with a 16-bit transaction ID ( XID) value in the DNS packet header and anticipate that the inaccessible DNS server will respond on the same port with the same XID value. The inquiry is characteristically sent over UDP. TCP is used only after a UDP response has been truncated.

[Spyrus]

When the resolver take delivery of a UDP DNS reaction, it can only weakly confirm that the reaction is genuine by matching these limitations. Like for example the first is, inaccessible DNS server address. This check is often put out of action by failure to pay because many network devices make it come into view that valid responses come from an address different from the one the query was sent to. This makes the spoofing of a DNS response even easier.

[Snake08]

Port on which the packet was established. The resolver will characteristically send from an momentary port to port 53. DNS servers take action from port 53 to the foundation port used by the supplicant. The port value is often easy for a malevolent user to guess. Packet XID value. The XID value is set in the request by the resolver and must be matched in the response.

[Zachary]

The different threats on DNS is a powerfully unsystematic value can and should be used for the XID, but it is only 16 bits long. The XID value, like the rest of the DNS packet, is sent in the clear. Query name and type. The DNS server repeats the query name and type in the question section of the DNS reaction.

[Big Fish]

If a malevolent user does not have right to use to a DNS client or server’s network traffic, he might be able to guess that a DNS client or server has sent a DNS query and is waiting for a DNS reaction. When he has resolute this to be true, the attacker can send one or more spoofed DNS reaction packets and endeavor to beat the authentic response back to the requester.