S-251: Vulnerability in DNS Client


 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) S-251: Vulnerability in DNS Client
# 1  
Old 04-09-2008
S-251: Vulnerability in DNS Client

A spoofing vulnerability exists in Windows DNS clients. The vulnerability could allow an unauthenticated attacker to send malicious responses to DNS requests made by vulnerable clients, thereby spoofing or redirecting Internet traffic from legitimate locations. The risk is MEDIUM. Could allow an unauthenticated attacker to send malicious responses to DNS requests made by vulnerable clients, thereby spoofing or redirecting Internet traffic from legitimate locations.


More...
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Solaris

DNS client added to DNS server but not working

Hi, We have built a new server (RHEL VM)and added that IP/hostname into dns zone configs file on DNS server (Solaris 10). Reloaded the configuration using and added nameserver into resolv.conf on client. But when I am trying nslookup, its not getting resolved. The nameserver is not able to... (8 Replies)
Discussion started by: snchaudhari2
8 Replies

2. Solaris

DNS client - what exactly it is

Hi all, I always thought DNS server = provide DNS response (host to ip / ip to host) to DNS client (which send DNS resolve request). So in my solaris 10 box, i setup /etc/resolv/conf, /etc/nsswitch.conf (added in dns) etc. Yes, i am able to dig and nslookup. But.. am i a DNS client ? ... (5 Replies)
Discussion started by: javanoob
5 Replies

3. Linux

How to add a client to DNS server

Hi all, What is the procedure to add a client to a DNS server. what are the settings and files need to be added/changed ? thanks in advance! (6 Replies)
Discussion started by: lramsb4u
6 Replies

4. IP Networking

How to Determine client's DNS server Ip

Is there a way for a server to determine client's DNS ip? I have an application that logs client's IP but in certain cases its desirable to know their DNS too (1 Reply)
Discussion started by: vickylife
1 Replies

5. Solaris

dns client not working

Hi All, I have configured linux server as local dns server (practice level). I have given the IP and hostname details in /etc/hosts -bash-3.00# cat /etc/hosts # # Internet host table # ::1 localhost 127.0.0.1 localhost 192.168.1.78 dummy.set.com loghost 192.168.1.57 cent.set.com #... (3 Replies)
Discussion started by: vaibhav.kanchan
3 Replies

6. Solaris

Solaris DNS Client For Microsoft DNS Server

hey guys, how to add soalris box as a microsoft DNS Client ? and how to register in the microsoft DNS ?? i managed to query from the DNS server after adding /etc/resolve.conf and editing /etc/nsswitch.conf but i need to register the soalris server (dns Client) into Microsoft DNS automatically.... (3 Replies)
Discussion started by: mduweik
3 Replies

7. UNIX for Advanced & Expert Users

DNS client nslookup

Hello, I just got done setting up a DNS server and a client. However, when I do an nslookup with just the hostname, I got this output: Microsoft Windows 2000 (C) Copyright 1985-2000 Microsoft Corp. C:\Documents and Settings\dev9>nslookup dev9 Server: webdev.testsurgemail.com Address:... (3 Replies)
Discussion started by: xnightcrawl
3 Replies
Login or Register to Ask a Question
dnsextd(8)						    BSD System Manager's Manual 						dnsextd(8)

NAME
dnsextd -- BIND Extension Daemon SYNOPSIS
dnsextd DESCRIPTION
dnsextd is a daemon invoked at boot time, running alongside BIND 9, to implement two EDNS0 extensions to the standard DNS protocol. dnsextd allows clients to perform DNS Updates with an attached lease lifetime, so that if the client crashes or is disconnected from the net- work, its address records will be automatically deleted after the lease expires. dnsextd allows clients to perform long-lived queries. Instead of rapidly polling the server to discover when information changes, long-lived queries enable a client to indicate its interest in some set of data, and then be notified asynchronously by the server whenever any of that data changes. dnsextd has no user-specifiable command-line argument, and users should not run dnsextd manually. SEE ALSO
mDNS(1) mDNSResponder(8) For information on Dynamic DNS Update, see RFC 2136 "Dynamic Updates in the Domain Name System (DNS UPDATE)" For information on Dynamic DNS Update Leases, see http://files.dns-sd.org/draft-dns-update-leases.txt For information on Long-Lived Queries, see http://files.dns-sd.org/draft-dns-llq.txt BUGS
dnsextd bugs are tracked in Apple Radar component "mDNSResponder". HISTORY
The dnsextd daemon first appeared in Mac OS X 10.4 (Tiger). Darwin June 1, 2019 Darwin