Unix and Linux Discussions Tagged with dns |
|
Thread / Thread Starter |
Last Post |
Replies |
Views |
Forum |
|
|
|
14 |
17,388 |
Cybersecurity |
|
|
|
18 |
21,961 |
UNIX for Beginners Questions & Answers |
|
|
|
6 |
15,435 |
UNIX for Advanced & Expert Users |
|
|
|
1 |
3,011 |
UNIX for Beginners Questions & Answers |
|
|
|
12 |
20,160 |
UNIX for Advanced & Expert Users |
|
|
|
5 |
5,169 |
Solaris |
|
|
|
12 |
27,485 |
IP Networking |
|
|
|
3 |
21,920 |
Emergency UNIX and Linux Support |
|
|
|
4 |
4,659 |
IP Networking |
|
|
|
5 |
10,001 |
Linux |
|
|
|
3 |
4,338 |
IP Networking |
|
|
|
0 |
2,704 |
Red Hat |
|
|
|
8 |
6,541 |
SCO |
|
|
|
1 |
3,241 |
What is on Your Mind? |
|
|
|
1 |
3,910 |
Red Hat |
|
|
|
9 |
4,919 |
UNIX for Advanced & Expert Users |
|
|
|
4 |
3,983 |
UNIX for Dummies Questions & Answers |
|
|
|
8 |
5,349 |
IP Networking |
|
|
|
1 |
4,827 |
UNIX for Advanced & Expert Users |
|
|
|
1 |
4,027 |
Solaris |
|
|
|
0 |
2,318 |
Solaris |
|
|
|
3 |
6,507 |
Solaris |
|
|
|
4 |
6,551 |
Ubuntu |
|
|
|
8 |
4,239 |
Solaris |
|
|
|
1 |
2,882 |
IP Networking |
|
|
|
0 |
2,954 |
Solaris |
|
|
|
2 |
4,978 |
IP Networking |
|
|
|
4 |
3,204 |
Shell Programming and Scripting |
|
|
|
1 |
3,484 |
Solaris |
|
|
|
0 |
3,379 |
Red Hat |
|
|
|
7 |
6,690 |
IP Networking |
|
|
|
0 |
2,886 |
UNIX for Dummies Questions & Answers |
|
|
|
1 |
3,925 |
Homework & Coursework Questions |
|
|
|
1 |
4,829 |
Cybersecurity |
|
|
|
7 |
16,345 |
UNIX for Advanced & Expert Users |
|
|
|
6 |
3,936 |
Ubuntu |
|
|
|
6 |
125,079 |
Red Hat |
|
|
|
2 |
3,950 |
Solaris |
|
|
|
2 |
5,665 |
Red Hat |
|
|
|
1 |
6,104 |
IP Networking |
desproxy-dns(1) User Commands desproxy-dns(1)
NAME
desproxy-dns - DNS for dynamic connections
SYNOPSIS
desproxy-dns dns_server proxy_host proxy_port
OPTIONS
None
DESCRIPTION
If you have direct DNS access then you don't need to do anything else. You know you have direct DNS access if you can resolve host names
to IP addresses.
NOTE: as desproxy-dns listens in port 53 (which is less than 1024) you may need administrator privileges to exec desproxy-dns (in fact if
you are running UN*X, you actually have to run desproxy-dns as root).
OK, so you have a dns server accessible now. But your computer doesn't know anything about that. You must configure your network
accordingly (again, need to be root in UN*X).
Edit /etc/resolv.conf and add the line "nameserver 127.0.0.1". You don't have to restart anything. Just test ping and see if it works.
ENVIRONMENT
None.
FILES
None.
SEE ALSO
dnsproxy(1), ping(1)
AUTHORS
This manual page was written by Jari Aalto <jari.aalto@cante.net>, for the Debian GNU system (but may be used by others). Released under
license GPL v2 or any later version.
desproxy-dns 2012-03-26 desproxy-dns(1)